domma-cms 1.6.5 → 1.6.6

package/README.md

@@ -264,7 +264,7 @@ Permissions per resource are defined in `config/auth.json`.
 
 The sidebar groups content by role:
 
-- **Overview** - Dashboard
+- **Dashboards** - Dashboard
 - **Structure** - Navigation, Layouts *(admin and manager only)*
 - **Content** - Pages, Media
 - **Configuration** - Users, Site Settings *(admin and manager only)*

package/config/menus/admin-sidebar.json

@@ -5,7 +5,7 @@
   "variant": "transparent",
   "items": [
     {
-      "text": "Overview",
+      "text": "Dashboards",
       "url": "",
       "icon": "home",
       "items": [

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "domma-cms",
-  "version": "1.6.5",
+  "version": "1.6.6",
   "description": "File-based CMS powered by Domma and Fastify. Run npx domma-cms my-site to create a new project.",
   "type": "module",
   "main": "server/server.js",

package/server/services/sidebar-migration.js

@@ -3,7 +3,7 @@
  *
  * Runs once on server boot. Idempotent - guarded by the existence of
  * config/menus/admin-sidebar.json. Seeds the admin sidebar menu with the
- * standard tree (Overview, Projects, Content, Data, Tools, System,
+ * standard tree (Dashboards, Projects, Content, Data, Tools, System,
  * Documentation) and patches config/menu-locations.json to map the
  * `admin-sidebar` slot.
  *
@@ -21,7 +21,7 @@ const DEFAULT_CONFIG_DIR = path.resolve(path.dirname(__filename), '..', '..', 'c
 
 const SEED_ITEMS = [
     {
-        text: 'Overview', key: 'overview', icon: 'home',
+        text: 'Dashboards', key: 'overview', icon: 'home',
         items: [
             {text: 'Dashboard', url: '#/', icon: 'home'}
         ]
@@ -319,13 +319,14 @@ export async function ensureDocumentationSubmenus(opts = {}) {
 
 /** Keys for the folders the seed has always created, matched by their original name. */
 const SEED_FOLDER_KEYS = {
-    overview: 'overview', projects: 'projects', content: 'content', data: 'data',
+    overview: 'overview', dashboards: 'overview', projects: 'projects', content: 'content', data: 'data',
     tools: 'tools', system: 'system', documentation: 'documentation'
 };
 
 /**
  * Give an existing install's top-level folders their stable `key`, and - once -
- * a persisted Tools folder for enabled Tools to be placed into.
+ * a persisted Tools folder for enabled Tools to be placed into, and - once -
+ * the name Dashboards for the folder that was Overview.
  *
  *  - A folder is keyed only if it has no key yet and still carries one of the
  *    seed's names; a folder the admin made, or renamed before keys existed, is
@@ -361,6 +362,16 @@ export async function ensureFolderKeys(opts = {}) {
         changed = true;
     }
 
+    // The first folder was "Overview" until 1.6.6. Renamed once (`meta.dashboardsFolder`)
+    // and only while it still says Overview, so a name an admin gave it - even
+    // Overview again, later - stays. Its key is still `overview`.
+    if (!menu.meta?.dashboardsFolder && items.length) {
+        const first = items.find(n => isFolder(n) && n.key === 'overview');
+        if (first && String(first.text || '').trim() === 'Overview') first.text = 'Dashboards';
+        menu.meta = {...(menu.meta || {}), dashboardsFolder: true};
+        changed = true;
+    }
+
     // An empty menu is left empty: the renderer's minimal fallback (Dashboard,
     // Menus) is what an admin needs to repair it, and a lone Tools folder would
     // stop that fallback from applying.