domma-cms 0.44.0 → 0.45.0

package/admin/js/templates/docs/usage-actions.html

@@ -14,14 +14,14 @@
                   <h3>Creating an Action</h3>
                   <ol>
                       <li>Navigate to <strong>Data → Actions</strong> and click <strong>New Action</strong>.</li>
-                      <li><strong>General tab</strong> — enter a title and select the target collection.</li>
-                      <li><strong>Trigger tab</strong> — configure the button label, icon, and optional confirmation
+                      <li><strong>General tab</strong> - enter a title and select the target collection.</li>
+                      <li><strong>Trigger tab</strong> - configure the button label, icon, and optional confirmation
                           message.
                       </li>
-                      <li><strong>Steps tab</strong> — add steps in order. Each step runs sequentially; if one fails the
+                      <li><strong>Steps tab</strong> - add steps in order. Each step runs sequentially; if one fails the
                           action stops.
                       </li>
-                      <li><strong>Access tab</strong> — select which roles can trigger this action.</li>
+                      <li><strong>Access tab</strong> - select which roles can trigger this action.</li>
                       <li>Click <strong>Save Action</strong>. The button will appear on the collection's entry list.
                       </li>
                   </ol>
@@ -100,7 +100,7 @@
                       </tr>
                       </tbody>
                   </table>
-                  <p><strong>Example</strong> — approve an application and notify by email:</p>
+                  <p><strong>Example</strong> - approve an application and notify by email:</p>
                   <pre class="code-block"><code>Step 1: updateField  field=status      value=approved
 Step 2: updateField  field=approvedAt  value={{now}}
 Step 3: email        to={{entry.data.email}}
@@ -110,7 +110,7 @@ Step 3: email        to={{entry.data.email}}
                   <h3>Partial Execution</h3>
                   <p>Actions are <strong>not transactional</strong>. If a step fails, the action stops and returns the
                       number of steps completed so far (<code>stepsCompleted</code>). Steps that already ran are
-                      <strong>not rolled back</strong>. Design step order with this in mind — put irreversible steps
+                      <strong>not rolled back</strong>. Design step order with this in mind - put irreversible steps
                       (delete, email) last.</p>
 
                   <h3>After a deleteEntry step</h3>

package/admin/js/templates/docs/usage-cta-shortcode.html

@@ -30,13 +30,13 @@
                       <tr>
                           <td><code>action</code></td>
                           <td>Yes</td>
-                          <td>—</td>
+                          <td>-</td>
                           <td>Action slug</td>
                       </tr>
                       <tr>
                           <td><code>entry</code></td>
                           <td>Yes</td>
-                          <td>—</td>
+                          <td>-</td>
                           <td>Entry UUID to act on</td>
                       </tr>
                       <tr>
@@ -54,19 +54,19 @@
                       <tr>
                           <td><code>icon</code></td>
                           <td>No</td>
-                          <td>—</td>
+                          <td>-</td>
                           <td>Domma icon name</td>
                       </tr>
                       <tr>
                           <td><code>size</code></td>
                           <td>No</td>
-                          <td>—</td>
+                          <td>-</td>
                           <td>sm · md · lg</td>
                       </tr>
                       <tr>
                           <td><code>confirm</code></td>
                           <td>No</td>
-                          <td>—</td>
+                          <td>-</td>
                           <td>Confirmation prompt before executing</td>
                       </tr>
                       </tbody>
@@ -91,8 +91,8 @@
                       <tbody>
                       <tr>
                           <td><code>cta</code></td>
-                          <td>—</td>
-                          <td>Action slug — enables per-entry buttons</td>
+                          <td>-</td>
+                          <td>Action slug - enables per-entry buttons</td>
                       </tr>
                       <tr>
                           <td><code>cta-label</code></td>
@@ -101,7 +101,7 @@
                       </tr>
                       <tr>
                           <td><code>cta-icon</code></td>
-                          <td>—</td>
+                          <td>-</td>
                           <td>Domma icon name</td>
                       </tr>
                       <tr>
@@ -111,7 +111,7 @@
                       </tr>
                       <tr>
                           <td><code>cta-confirm</code></td>
-                          <td>—</td>
+                          <td>-</td>
                           <td>Confirmation prompt</td>
                       </tr>
                       </tbody>

package/admin/js/templates/docs/usage-dconfig.html

@@ -7,18 +7,18 @@
   <div class="col-12">
     <div class="docs-body">
 
-<p>DConfig lets you wire up declarative behaviour on any public page — no JavaScript required. Define
+<p>DConfig lets you wire up declarative behaviour on any public page - no JavaScript required. Define
                       event
                       handlers and class toggles in JSON; the page runtime applies them automatically on load.</p>
 
                   <p>DConfig can be set in two ways, and both are merged at runtime (inline shortcode wins on selector
                       conflict):</p>
                   <ul>
-                      <li><strong>Page editor</strong> — the <em>DConfig</em> collapsible section accepts a JSON blob
+                      <li><strong>Page editor</strong> - the <em>DConfig</em> collapsible section accepts a JSON blob
                           stored in page
                           frontmatter and injected as <code>window.__CMS_DCONFIG__</code>.
                       </li>
-                      <li><strong>Inline shortcode</strong> — place one or more <code>[dconfig]…[/dconfig]</code> blocks
+                      <li><strong>Inline shortcode</strong> - place one or more <code>[dconfig]…[/dconfig]</code> blocks
                           directly in
                           the page body Markdown.
                       </li>
@@ -116,7 +116,7 @@ Content goes here.
 
                   <h3>Multiple selectors</h3>
                   <p>Any number of selectors can appear in one block. Selectors are matched with
-                      <code>document.querySelector</code> — use IDs, classes, or attribute selectors.</p>
+                      <code>document.querySelector</code> - use IDs, classes, or attribute selectors.</p>
                   <pre class="code-block"><code>[dconfig]
 {
   "#show-btn": {

package/admin/js/templates/docs/usage-navigation.html

@@ -14,7 +14,7 @@
                   <h3>Dropdowns</h3>
                   <p>Nest items under a parent using the drag-and-drop tree in the Navigation editor. Child items are
                       stored under
-                      the <code>items</code> key — the public navbar renders them as a dropdown.</p>
+                      the <code>items</code> key - the public navbar renders them as a dropdown.</p>
 
                   <h3>External links</h3>
                   <p>Set the URL to a full <code>https://</code> address to link outside the site. Leave blank for

package/admin/js/templates/docs/usage-pages.html

@@ -54,7 +54,7 @@ updatedAt: 2026-03-01    # auto-set on save
 Your Markdown content goes here.</code></pre>
 
                   <h3>Drafts</h3>
-                  <p>Pages with <code>status: draft</code> are never served on the public site — they return a 404.
+                  <p>Pages with <code>status: draft</code> are never served on the public site - they return a 404.
                       Toggle status
                       in the Page Editor to publish.</p>
 

package/admin/js/templates/docs/usage-shortcodes.html

@@ -23,11 +23,11 @@
                       <tbody>
                       <tr>
                           <td><code>[grid cols="N" gap="N"]...[/grid]</code></td>
-                          <td>CSS Grid container — N columns (1–12), optional gap (1–6)</td>
+                          <td>CSS Grid container - N columns (1-12), optional gap (1-6)</td>
                       </tr>
                       <tr>
                           <td><code>[row gap="N"]...[/row]</code></td>
-                          <td>Flexbox row — columns share width equally</td>
+                          <td>Flexbox row - columns share width equally</td>
                       </tr>
                       <tr>
                           <td><code>[col span="N"]...[/col]</code></td>
@@ -47,7 +47,7 @@
                       <tbody>
                       <tr>
                           <td><code>[card title="..."]...[/card]</code></td>
-                          <td>Styled card. Supports 6 variants, ~44 gradients and 33 layouts — see the
+                          <td>Styled card. Supports 6 variants, ~44 gradients and 33 layouts - see the
                               <strong>Cards</strong> subsection below.
                           </td>
                       </tr>
@@ -88,11 +88,11 @@
                       </tbody>
                   </table>
 
-                  <h3>Cards &mdash; variants, gradients &amp; layouts</h3>
+                  <h3>Cards - variants, gradients &amp; layouts</h3>
                   <p>The <code>[card]</code> shortcode is the most configurable component in the system. It has three
                       layers you can mix freely: <strong>variant</strong> (the overall visual style), <strong>gradient</strong>
                       (colour palette, used with <code>variant="gradient"</code> or any layout that accepts a gradient),
-                      and <strong>layout</strong> (the internal structure — header/body/footer, image position, sub-tags,
+                      and <strong>layout</strong> (the internal structure - header/body/footer, image position, sub-tags,
                       etc.). Every layout accepts every variant, gradient and universal attribute listed below.</p>
                   <pre><code>[card variant="gradient" gradient="ocean" layout="icon-top" icon="star" title="Fast"]
 Body content in **Markdown** is supported.
@@ -109,7 +109,7 @@ Body content in **Markdown** is supported.
                       <tbody>
                       <tr>
                           <td><code>clean</code></td>
-                          <td>Flat, minimal chrome &mdash; no border, subtle background</td>
+                          <td>Flat, minimal chrome - no border, subtle background</td>
                       </tr>
                       <tr>
                           <td><code>gradient</code></td>
@@ -126,7 +126,7 @@ Body content in **Markdown** is supported.
                       </tr>
                       <tr>
                           <td><code>dark</code></td>
-                          <td>Dark background with inverted text &mdash; good on light pages</td>
+                          <td>Dark background with inverted text - good on light pages</td>
                       </tr>
                       <tr>
                           <td><code>glow</code></td>
@@ -134,13 +134,13 @@ Body content in **Markdown** is supported.
                       </tr>
                       <tr>
                           <td><code>primary</code></td>
-                          <td>Legacy alias &mdash; adds <code>card-primary</code> class for backwards compatibility</td>
+                          <td>Legacy alias - adds <code>card-primary</code> class for backwards compatibility</td>
                       </tr>
                       </tbody>
                   </table>
 
                   <h4>Built-in gradients</h4>
-                  <p>Shipped in <code>public/css/</code> &mdash; available on every install. Default when
+                  <p>Shipped in <code>public/css/</code> - available on every install. Default when
                       <code>gradient</code> is omitted: <code>indigo</code>.</p>
                   <p><code>arctic</code>, <code>aurora</code>, <code>dusk</code>, <code>fire</code>, <code>forest</code>,
                       <code>gold</code>, <code>indigo</code>, <code>lagoon</code>, <code>lime</code>,
@@ -148,7 +148,7 @@ Body content in **Markdown** is supported.
                       <code>sunset</code></p>
 
                   <h4>Project-specific gradients</h4>
-                  <p>Defined in <code>content/custom.css</code> on this site only &mdash; fresh installs will not have
+                  <p>Defined in <code>content/custom.css</code> on this site only - fresh installs will not have
                       these unless the CSS is copied over.</p>
                   <p><strong>Single-tone:</strong> <code>purple</code>, <code>blue</code>, <code>green</code>,
                       <code>night</code></p>
@@ -162,7 +162,7 @@ Body content in **Markdown** is supported.
                       <code>silver-dark</code>, <code>charcoal-dark</code>, <code>christmas-dark</code>,
                       <code>unicorn-dark</code>, <code>dreamy-dark</code>, <code>grayve-dark</code>,
                       <code>mint-dark</code>, <code>wedding-dark</code></p>
-                  <p class="text-muted"><small>Gradient names are not validated &mdash; a typo falls through to the
+                  <p class="text-muted"><small>Gradient names are not validated - a typo falls through to the
                       default background with no warning. Use <code>/test-card-gradients</code> to preview every
                       palette.</small></p>
 
@@ -311,7 +311,7 @@ Body content in **Markdown** is supported.
                       <tr>
                           <td><code>icon-top</code></td>
                           <td><code>icon</code>, <code>title</code>, <code>subtitle</code></td>
-                          <td>Large centred icon above title &mdash; good for feature grids</td>
+                          <td>Large centred icon above title - good for feature grids</td>
                       </tr>
                       <tr>
                           <td><code>icon-inline</code></td>
@@ -387,7 +387,7 @@ Body content in **Markdown** is supported.
                       <tr>
                           <td><code>location-map</code></td>
                           <td><code>address</code>, <code>title</code></td>
-                          <td>Placeholder map panel + address block (static &mdash; no live map)</td>
+                          <td>Placeholder map panel + address block (static - no live map)</td>
                       </tr>
                       </tbody>
                   </table>
@@ -407,7 +407,7 @@ Body content in **Markdown** is supported.
                           <td><code>icon</code>, <code>title</code>, <code>subtitle</code>,
                               <code>tags</code> (comma-separated)
                           </td>
-                          <td>Circular avatar + name + role + pill tags &mdash; team / author cards</td>
+                          <td>Circular avatar + name + role + pill tags - team / author cards</td>
                       </tr>
                       <tr>
                           <td><code>quote-testimonial</code></td>
@@ -416,7 +416,7 @@ Body content in **Markdown** is supported.
                       </tr>
                       <tr>
                           <td><code>rating-review</code></td>
-                          <td><code>rating</code> (0&ndash;5), <code>title</code>, <code>subtitle</code>,
+                          <td><code>rating</code> (0-5), <code>title</code>, <code>subtitle</code>,
                               <code>verified</code> (flag)
                           </td>
                           <td>Star rating + review body + reviewer attribution</td>
@@ -437,7 +437,7 @@ Body content in **Markdown** is supported.
                       <tr>
                           <td><code>stat-metric</code></td>
                           <td><code>title</code> (label), <code>value</code>, <code>delta</code>,
-                              <code>progress</code> (0&ndash;100)
+                              <code>progress</code> (0-100)
                           </td>
                           <td>Big-number KPI tile with delta arrow and optional progress bar</td>
                       </tr>
@@ -493,12 +493,12 @@ Body content in **Markdown** is supported.
                       <tr>
                           <td><code>tag-cloud</code></td>
                           <td><code>title</code>, <code>tags</code> (comma-separated)</td>
-                          <td>Coloured pill list &mdash; topic tags, skills, categories</td>
+                          <td>Coloured pill list - topic tags, skills, categories</td>
                       </tr>
                       <tr>
                           <td><code>timeline-entry</code></td>
                           <td><code>title</code>, <code>subtitle</code> (date), <code>badge</code> (tag)</td>
-                          <td>Single dot-on-line timeline entry &mdash; stack several for a history list</td>
+                          <td>Single dot-on-line timeline entry - stack several for a history list</td>
                       </tr>
                       </tbody>
                   </table>
@@ -572,7 +572,7 @@ Body content in **Markdown** is supported.
                   </table>
 
                   <h4>Sub-tag reference</h4>
-                  <p>These are child tags accepted by specific layouts &mdash; they are not shortcodes in their own right
+                  <p>These are child tags accepted by specific layouts - they are not shortcodes in their own right
                       and only render inside a matching parent card.</p>
                   <table class="table table-sm">
                       <thead>
@@ -586,7 +586,7 @@ Body content in **Markdown** is supported.
                       <tr>
                           <td><code>[feature]text[/feature]</code></td>
                           <td><code>pricing</code>, <code>feature-comparison</code></td>
-                          <td><code>excluded</code> (flag, comparison only) &mdash; renders as a cross instead of a tick
+                          <td><code>excluded</code> (flag, comparison only) - renders as a cross instead of a tick
                           </td>
                       </tr>
                       <tr>
@@ -607,7 +607,7 @@ Body content in **Markdown** is supported.
                       <tr>
                           <td><code>[milestone done]text[/milestone]</code></td>
                           <td><code>progress-goal</code></td>
-                          <td><code>done</code> (flag) &mdash; filled dot if present, hollow otherwise</td>
+                          <td><code>done</code> (flag) - filled dot if present, hollow otherwise</td>
                       </tr>
                       </tbody>
                   </table>
@@ -681,7 +681,7 @@ Body content in **Markdown** is supported.
                           <td><code>field=value</code> or<br><code>f1=v1,f2=v2</code></td>
                           <td>Row filter (simple equality only, AND'd across comma-separated predicates). Example:
                               <code>where="tab=developers"</code> or
-                              <code>where="tier=free,featured=true"</code>. No OR, no comparison operators &mdash;
+                              <code>where="tier=free,featured=true"</code>. No OR, no comparison operators -
                               use a saved View for anything more complex.
                           </td>
                       </tr>
@@ -703,7 +703,7 @@ Body content in **Markdown** is supported.
                       <tr>
                           <td><code>fields</code></td>
                           <td>comma-separated field names</td>
-                          <td>Column filter &mdash; only these fields are shown (table/cards/list displays only).
+                          <td>Column filter - only these fields are shown (table/cards/list displays only).
                           </td>
                       </tr>
                       <tr>
@@ -776,7 +776,7 @@ Body content in **Markdown** is supported.
                       </tr>
                       <tr>
                           <td><code>[dconfig]{...}[/dconfig]</code></td>
-                          <td>Declarative click handlers and class toggles — no JavaScript needed</td>
+                          <td>Declarative click handlers and class toggles - no JavaScript needed</td>
                       </tr>
                       </tbody>
                   </table>

package/admin/js/templates/docs/usage-users-roles.html

@@ -22,7 +22,7 @@
                       <tbody>
                       <tr>
                           <td><strong>Admin</strong></td>
-                          <td>Full access — users, plugins, settings, all content.</td>
+                          <td>Full access - users, plugins, settings, all content.</td>
                       </tr>
                       <tr>
                           <td><strong>Manager</strong></td>
@@ -42,11 +42,11 @@
                   <h3>Authentication</h3>
                   <p>The admin panel uses JWT Bearer tokens. Tokens are stored in the browser and automatically
                       refreshed.
-                      Sessions expire according to <code>config/auth.json</code> — default is 24 hours.</p>
+                      Sessions expire according to <code>config/auth.json</code> - default is 24 hours.</p>
 
                   <h3>Views &amp; Actions</h3>
                   <p>Views and Actions are pro-only features that require a MongoDB connection.
-                      Both roles — Admin and Manager — can create, edit, and run Views and Actions.</p>
+                      Both roles - Admin and Manager - can create, edit, and run Views and Actions.</p>
                   <table class="table table-sm">
                       <thead>
                       <tr>

package/admin/js/templates/docs/usage-views.html

@@ -14,16 +14,16 @@
                   <h3>Creating a View</h3>
                   <ol>
                       <li>Navigate to <strong>Data → Views</strong> and click <strong>New View</strong>.</li>
-                      <li><strong>Source tab</strong> — enter a title, choose the primary source collection, and select
+                      <li><strong>Source tab</strong> - enter a title, choose the primary source collection, and select
                           the MongoDB connection.
                       </li>
-                      <li><strong>Pipeline tab</strong> — add aggregation stages in order. Each stage has a type and a
+                      <li><strong>Pipeline tab</strong> - add aggregation stages in order. Each stage has a type and a
                           JSON config object.
                       </li>
-                      <li><strong>Display tab</strong> — choose table or list mode, set page size, and optionally define
+                      <li><strong>Display tab</strong> - choose table or list mode, set page size, and optionally define
                           column definitions.
                       </li>
-                      <li><strong>Access tab</strong> — select which roles can access this view and whether it is
+                      <li><strong>Access tab</strong> - select which roles can access this view and whether it is
                           publicly accessible.
                       </li>
                       <li>Click <strong>Save View</strong>, then use <strong>Preview</strong> to execute and inspect the

package/admin/js/templates/documentation.html

@@ -7,7 +7,7 @@
     <div class="docs-body">
 
       <p class="lead">
-        Task-by-task reference for running a Domma CMS site. Pick a topic below — each opens as its own
+        Task-by-task reference for running a Domma CMS site. Pick a topic below - each opens as its own
         page, and every topic is also listed under <strong>Documentation → Usage</strong> in the sidebar.
       </p>