domma-cms 0.42.0 → 0.44.0

package/CLAUDE.md

@@ -112,8 +112,9 @@ Collection entry I/O is delegated to a storage adapter. Schema management is alw
 Roles are **dynamic** — stored as entries in `content/collections/user-types/` (a preset collection).
 Seeded on first run with: `admin`, `manager`, `editor`, `subscriber`.
 
-- `server/services/userTypes.js` — `seed()`, `load()`, `invalidate()`, `getRoleLevel(role)`, `getPermissionsFor(resource)`, `getRoleHierarchy()`
-- `server/services/roles.js` — role helper utilities
+- `server/services/roles.js` — `seed()`, `load()`, `invalidate()`, `getRoleLevel(role)`,
+  `getPermissionsFor(resource)`, `getRoleHierarchy()` (returns role names sorted most-privileged
+  first, level 0 = admin, so the least-privileged role is `.at(-1)`)
 - `server/services/permissionRegistry.js` — central permission map; route guards read the cache at request time
 - `server/services/rowAccess.js` — row-level access control for collections
 - Route guards use `requirePermission('resource')`, **not** hardcoded role names
@@ -159,6 +160,39 @@ Menus live in `config/menus/<slug>.json`. The slot → menu map lives in `config
 
 The admin sidebar is now menu-data-driven — no more hardcoded `sidebar-config.js`. The menu lives at `config/menus/admin-sidebar.json` and is auto-seeded on first boot (idempotent, file-existence guarded) with the standard tree: Overview, Projects, Content, Data, System, Documentation. Renderer is at `admin/js/lib/sidebar-renderer.js`; it reads the menu, merges in plugin-registered items (via `hooks.registerSidebarItem({parent, item})`), filters by each item's optional `permission` field, then mounts. The **Menus** admin can edit the sidebar visually like any other menu — the item editor exposes the new `permission` field on each row (resource key from `permissionRegistry`). Plugin-injected items are render-time only and not shown in the Menus editor; admins hide them by adding a same-`text` item with `hidden: true` to the persisted menu.
 
+## Collection displays & public filtering
+
+`[collection]` and `[view]` render in any of table, cards, list, block, accordion, timeline,
+carousel or listgroup (`display="…"`). Rendering is server-side in `markdown.js`; the browser
+modules below add behaviour on top.
+
+**Right-click menu** (`public/js/collection-context.js`, loaded as `type="module"` from
+`server/templates/page.html`) works on the public site, not just the admin. Every
+collection-rendered display carries a `data-ctx` payload (tables instead hydrate via `site.js`);
+right-clicking inside one opens a menu of filters derived from the clicked entry's fields, plus
+free-text search, sort, group-by, export, copy (CSV/JSON/Markdown to clipboard), print and
+"copy link to this view". Active filters appear as removable chips above the display. Sort,
+filters and grouping all persist in the URL hash (`dmf=`), so a filtered/sorted/grouped view can
+be bookmarked or shared. Each display type filters differently — timeline via the Progression
+instance's `.setItems()`, carousel by rebuilding the track from pristine slide copies and
+re-initialising, table by re-creating the Domma table with the row subset, everything else by
+toggling a hidden class on `[data-entry-id]`. Grouping needs entries rendered as direct DOM
+siblings, so it's only offered on the five toggle-based displays (cards, list, listgroup,
+accordion, block) — table/timeline/carousel manage their own rendering and hide the "Group by…"
+row. See `docs/markdown-shortcodes.md` for the full capability table per display type.
+
+**Export permission** lives in the collection schema's `export` block (`enabled`, `access`,
+`formats`) — see `docs/configuration.md`. It is a convenience gate, not an access boundary: entry
+data is already in the page's `data-ctx` attribute, so it never stops a determined reader of page
+source, only the download button shown to everyone else.
+
+**Shared modules**: `public/js/collection-export.mjs` (CSV/JSON/Markdown serialisation dialect —
+CSV formula-injection sanitising, BOM handling) is imported by BOTH the browser
+(`collection-context.js`) and the server (`server/services/collections.js`), so admin exports and
+public right-click exports are byte-identical for the same values. `public/js/collection-sort.mjs`
+holds `compareValues`/`sortEntries` — the same comparison ladder backs both the sort menu and the
+`gt`/`lt` right-click filters.
+
 ## Key Gotchas
 
 1. **Menu item sub-items**: use `items` key, NOT `children` — Domma navbar and the `[menu]` shortcode both read `items`.

package/admin/js/templates/collection-editor.html

@@ -14,7 +14,7 @@
     <div class="tab-list">
         <button class="tab-item active">Settings</button>
         <button class="tab-item">Fields</button>
-        <button class="tab-item">API Access</button>
+        <button class="tab-item">API &amp; Export</button>
       <button class="tab-item" id="storage-tab-btn" style="display:none;">Storage</button>
     </div>
     <div class="tab-content">