domma-cms 0.25.15 → 0.25.16

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

@@ -0,0 +1,31 @@
+<div class="view-header">
+  <h1><span data-icon="book"></span> Navigation</h1>
+  <a href="#/documentation" class="btn btn-ghost btn-sm"><span data-icon="arrow-left"></span> All usage topics</a>
+</div>
+
+<div class="row">
+  <div class="col-12">
+    <div class="docs-body">
+
+<p>The navigation tree is stored in <code>config/navigation.json</code> and injected into every public
+                      page as
+                      <code>window.__CMS_NAV__</code>.</p>
+
+                  <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>
+
+                  <h3>External links</h3>
+                  <p>Set the URL to a full <code>https://</code> address to link outside the site. Leave blank for
+                      section
+                      headings.</p>
+
+                  <h3>Icons</h3>
+                  <p>Set the <code>icon</code> field to any registered icon name. Icons appear in the navbar link
+                      alongside the
+                      label.</p>
+
+    </div>
+  </div>
+</div>

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

@@ -0,0 +1,68 @@
+<div class="view-header">
+  <h1><span data-icon="book"></span> Pages</h1>
+  <a href="#/documentation" class="btn btn-ghost btn-sm"><span data-icon="arrow-left"></span> All usage topics</a>
+</div>
+
+<div class="row">
+  <div class="col-12">
+    <div class="docs-body">
+
+<p>Pages are stored as Markdown files in <code>content/pages/</code>. Each file has a YAML frontmatter
+                      block at
+                      the top followed by the page body in Markdown.</p>
+
+                  <h3>URL mapping</h3>
+                  <table class="table table-sm">
+                      <thead>
+                      <tr>
+                          <th>File path</th>
+                          <th>Public URL</th>
+                      </tr>
+                      </thead>
+                      <tbody>
+                      <tr>
+                          <td><code>content/pages/index.md</code></td>
+                          <td><code>/</code></td>
+                      </tr>
+                      <tr>
+                          <td><code>content/pages/about.md</code></td>
+                          <td><code>/about</code></td>
+                      </tr>
+                      <tr>
+                          <td><code>content/pages/blog/index.md</code></td>
+                          <td><code>/blog</code></td>
+                      </tr>
+                      <tr>
+                          <td><code>content/pages/blog/hello-world.md</code></td>
+                          <td><code>/blog/hello-world</code></td>
+                      </tr>
+                      </tbody>
+                  </table>
+
+                  <h3>Frontmatter reference</h3>
+                  <pre class="code-block"><code>---
+title: My Page
+description: A short description for SEO meta tags.
+status: published        # published | draft  (draft pages return 404)
+layout: default          # layout name from config/presets.json
+tags: [one, two]         # optional taxonomy
+updatedAt: 2026-03-01    # auto-set on save
+---
+
+# Page heading
+
+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.
+                      Toggle status
+                      in the Page Editor to publish.</p>
+
+                  <h3>Layouts</h3>
+                  <p>Layouts are defined in <code>config/presets.json</code> and apply CSS class wrappers around page
+                      content.
+                      Select a layout per-page in the editor, or change the default in Site Settings.</p>
+
+    </div>
+  </div>
+</div>

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

@@ -0,0 +1,36 @@
+<div class="view-header">
+  <h1><span data-icon="book"></span> Plugins</h1>
+  <a href="#/documentation" class="btn btn-ghost btn-sm"><span data-icon="arrow-left"></span> All usage topics</a>
+</div>
+
+<div class="row">
+  <div class="col-12">
+    <div class="docs-body">
+
+<p>Plugins extend the CMS with new server routes, admin views, and public-site injection snippets.
+                      Each plugin
+                      is a directory under <code>plugins/</code>.</p>
+
+                  <h3>Enabling and disabling</h3>
+                  <p>Use the Plugins page in the admin to toggle plugins on or off. State is saved to
+                      <code>config/plugins.json</code>. <strong>A server restart is required for changes to take
+                          effect.</strong>
+                  </p>
+
+                  <h3>Plugin settings</h3>
+                  <p>Plugins that expose a settings page will appear as a link in the sidebar under the Plugins section.
+                      Settings
+                      are merged with the plugin's defaults from <code>config.js</code> and saved to
+                      <code>config/plugins.json</code>.</p>
+
+                  <h3>Security</h3>
+                  <p>Only files inside a plugin's <code>admin/</code> and <code>public/</code> subdirectories are served
+                      statically. Server files (<code>plugin.js</code>, <code>config.js</code>, <code>data/</code>) are
+                      blocked and
+                      return 404.</p>
+
+                  <p>See the <a href="#/tutorials">Tutorials</a> section for a guide to writing your own plugin.</p>
+
+    </div>
+  </div>
+</div>