From 96ba45b96627a37205c7bf67d8a629009bb2f0c5 Mon Sep 17 00:00:00 2001 From: Doxa Maps Date: Mon, 28 Sep 2026 07:44:27 +0000 Subject: [PATCH] Name the two unlabelled Cities with Internet profiles MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit connectivity-list and data-tables had no profile meta at all, so the Studio and the gallery fell back to a humanised profile id: a reader picking a view saw "connectivity list" and "data tables" rather than what the pane actually is. The sibling connectivity-map already carried a label; these two are now in step, so the three read as one family in the picker instead of sorting apart. The wording is not invented. Each pane renders its own heading from i18n — connectivity.list.title is "Cities with Internet" and connectivity.tables.title is "Cities Data" — so the labels lead with the product name the reader already sees, then name the view, matching the shape connectivity-map established. Both metas declare stage experimental explicitly. That is the existing default for a profile with no meta, so nothing is promoted and the manifest is byte-for -byte unchanged; it is stated because bundleStage turns a whole bundle production as soon as one profile claims it, and a stage left implicit is one default change away from moving on its own. Source only, no bundle rebuild: the label is read from the meta by the gallery's discovery, and never travels into manifest.json. --- plugin-designs/cities-internet/connectivity-list.meta.json | 5 +++++ plugin-designs/cities-internet/data-tables.meta.json | 5 +++++ 2 files changed, 10 insertions(+) create mode 100644 plugin-designs/cities-internet/connectivity-list.meta.json create mode 100644 plugin-designs/cities-internet/data-tables.meta.json diff --git a/plugin-designs/cities-internet/connectivity-list.meta.json b/plugin-designs/cities-internet/connectivity-list.meta.json new file mode 100644 index 000000000..404b780ed --- /dev/null +++ b/plugin-designs/cities-internet/connectivity-list.meta.json @@ -0,0 +1,5 @@ +{ + "stage": "experimental", + "label": "Cities with Internet — connectivity list", + "note": "The Studio and gallery read this label from here (internal/plugin-gallery/discover.mjs: `meta.label || profile`); with no meta file at all they fell back to the humanised profile id. The wording tracks the pane's own heading, t('connectivity.list.title') = \"Cities with Internet\", plus the view name — the same shape as the sibling connectivity-map.meta.json, so the three profiles read as one family in the picker. stage is declared EXPLICITLY rather than left to the default: the default is already experimental (internal/profile-meta.mjs), so this changes nothing today, but a meta that states its stage cannot be silently promoted if that default ever moves, and bundleStage() turns the whole bundle production as soon as ONE profile claims it." +} diff --git a/plugin-designs/cities-internet/data-tables.meta.json b/plugin-designs/cities-internet/data-tables.meta.json new file mode 100644 index 000000000..3a55f9241 --- /dev/null +++ b/plugin-designs/cities-internet/data-tables.meta.json @@ -0,0 +1,5 @@ +{ + "stage": "experimental", + "label": "Cities with Internet — data tables", + "note": "Label read by internal/plugin-gallery/discover.mjs (`meta.label || profile`); without a meta file this profile showed as the humanised id 'data tables'. The pane's own heading is t('connectivity.tables.title') = \"Cities Data\"; the label leads with the bundle's product name so the picker groups it with connectivity-map and connectivity-list rather than sorting it away under a different first word. stage declared explicitly for the reason given in connectivity-list.meta.json." +}