npm - @pagenary/publisher - Versions diffs - 2026.5.0 - Mend

@pagenary/publisher 2026.5.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (147) hide show

package/LICENSE +661 -0
package/README.md +337 -0
package/bin/pagenary.mjs +116 -0
package/build.config.json +5 -0
package/package.json +66 -0
package/scripts/build-site.js +87 -0
package/scripts/build-tenants.js +3569 -0
package/scripts/build.js +99 -0
package/scripts/generate-sections.js +41 -0
package/scripts/lib/seo-generator.js +558 -0
package/scripts/lint-content.js +62 -0
package/scripts/seo-smoke.js +94 -0
package/scripts/serve.js +142 -0
package/site/app.js +1 -0
package/site/index.html +57 -0
package/site/lib/categories.js +1 -0
package/site/lib/export.js +1 -0
package/site/lib/manifest-utils.js +1 -0
package/site/lib/router.js +1 -0
package/site/lib/search.js +1 -0
package/site/llms.txt +22 -0
package/site/manifest.js +132 -0
package/site/mermaid-init.js +1 -0
package/site/pages/api.html +339 -0
package/site/pages/architecture.html +303 -0
package/site/pages/deployment.html +282 -0
package/site/pages/developer-guide.html +157 -0
package/site/pages/extending.html +135 -0
package/site/pages/quickstart.html +318 -0
package/site/pages/seo-strategy.html +121 -0
package/site/pages/tenant-config.html +519 -0
package/site/pages/welcome.html +116 -0
package/site/robots.txt +10 -0
package/site/sections/api.js +3 -0
package/site/sections/architecture.js +3 -0
package/site/sections/deployment.js +3 -0
package/site/sections/developer-guide.js +3 -0
package/site/sections/extending.js +3 -0
package/site/sections/quickstart.js +3 -0
package/site/sections/section-templates.js +1 -0
package/site/sections/seo-strategy.js +3 -0
package/site/sections/tenant-config.js +3 -0
package/site/sections/welcome.js +3 -0
package/site/seo.js +1 -0
package/site/sitemap.xml +63 -0
package/site/styles.css +1982 -0
package/site/syntax-highlight.js +1 -0
package/src/app.js +988 -0
package/src/index.html +56 -0
package/src/lib/categories.js +55 -0
package/src/lib/export.js +195 -0
package/src/lib/manifest-utils.js +69 -0
package/src/lib/router.js +44 -0
package/src/lib/search.js +151 -0
package/src/manifest.js +246 -0
package/src/mermaid-init.js +207 -0
package/src/sections/archive-future-roadmap.js +7 -0
package/src/sections/archive-initiative-alpha.js +7 -0
package/src/sections/archive-milestone-records.js +7 -0
package/src/sections/archive-timeline-overview.js +7 -0
package/src/sections/core-technology-compliance-frameworks.js +7 -0
package/src/sections/core-technology-coordination-model.js +7 -0
package/src/sections/core-technology-data-definitions.js +7 -0
package/src/sections/core-technology-hardware-integration.js +7 -0
package/src/sections/core-technology-integrity-controls.js +7 -0
package/src/sections/core-technology-network-topology.js +7 -0
package/src/sections/core-technology-operator-requirements.js +7 -0
package/src/sections/core-technology-overview.js +7 -0
package/src/sections/core-technology-service-interfaces.js +7 -0
package/src/sections/core-technology-synchronization-strategy.js +7 -0
package/src/sections/core-technology-system-foundation.js +7 -0
package/src/sections/developers-api-credentials.js +7 -0
package/src/sections/developers-api-operations.js +7 -0
package/src/sections/developers-api-reference.js +7 -0
package/src/sections/developers-api-websocket.js +7 -0
package/src/sections/developers-automation-blueprints.js +7 -0
package/src/sections/developers-automation-modules.js +7 -0
package/src/sections/developers-automation-patterns.js +7 -0
package/src/sections/developers-deployment-playbook.js +7 -0
package/src/sections/developers-overview.js +7 -0
package/src/sections/developers-scheduling-patterns.js +7 -0
package/src/sections/developers-sdk-go.js +7 -0
package/src/sections/developers-sdk-javascript.js +7 -0
package/src/sections/developers-sdk-python.js +7 -0
package/src/sections/developers-sdk-rust.js +7 -0
package/src/sections/developers-sdks.js +7 -0
package/src/sections/developers-solution-examples.js +7 -0
package/src/sections/developers-testing-framework.js +7 -0
package/src/sections/getting-started-architecture-basics.js +7 -0
package/src/sections/getting-started-introduction.js +7 -0
package/src/sections/getting-started-performance-overview.js +7 -0
package/src/sections/governance-community-initiatives.js +7 -0
package/src/sections/governance-dao-overview.js +7 -0
package/src/sections/governance-multi-token.js +7 -0
package/src/sections/governance-overview.js +7 -0
package/src/sections/governance-proposal-process.js +7 -0
package/src/sections/governance-proposals.js +7 -0
package/src/sections/governance-structure.js +7 -0
package/src/sections/governance-token-distribution.js +7 -0
package/src/sections/governance-treasury.js +7 -0
package/src/sections/operations-environment-prep.js +7 -0
package/src/sections/operations-getting-started.js +7 -0
package/src/sections/operations-incentives-guide.js +7 -0
package/src/sections/operations-incentives-strategies.js +7 -0
package/src/sections/operations-incentives.js +7 -0
package/src/sections/operations-infrastructure.js +7 -0
package/src/sections/operations-monitoring.js +7 -0
package/src/sections/operations-overview.js +7 -0
package/src/sections/operations-performance.js +7 -0
package/src/sections/operations-power-infrastructure.js +7 -0
package/src/sections/operations-setup-guide.js +7 -0
package/src/sections/operations-sync-setup.js +7 -0
package/src/sections/products-flagship-solution.js +7 -0
package/src/sections/products-solution-library.js +7 -0
package/src/sections/resources-brand-assets.js +7 -0
package/src/sections/resources-faq.js +7 -0
package/src/sections/resources-glossary.js +7 -0
package/src/sections/resources-research-papers.js +7 -0
package/src/sections/section-templates.js +873 -0
package/src/sections/security-audits.js +7 -0
package/src/sections/security-best-practices.js +7 -0
package/src/sections/security-bug-bounty.js +7 -0
package/src/sections/security-incident-response.js +7 -0
package/src/sections/security-overview.js +7 -0
package/src/sections/technical-architecture.js +7 -0
package/src/sections/technical-whitepaper.js +7 -0
package/src/sections/tutorial-automation-bot.js +7 -0
package/src/sections/tutorial-build-first-integration.js +7 -0
package/src/sections/tutorial-deploy-automation.js +7 -0
package/src/sections/tutorial-event-driven-experience.js +7 -0
package/src/sections/tutorial-operations-onboarding.js +7 -0
package/src/sections/tutorial-systems-integration.js +7 -0
package/src/sections/tutorials-overview.js +7 -0
package/src/sections/use-case-connected-devices.js +7 -0
package/src/sections/use-case-digital-auctions.js +7 -0
package/src/sections/use-case-financial-automation.js +7 -0
package/src/sections/use-case-interactive-media.js +7 -0
package/src/sections/use-case-realtime-execution.js +7 -0
package/src/sections/use-case-research-analytics.js +7 -0
package/src/sections/use-case-supply-operations.js +7 -0
package/src/sections/use-cases-overview.js +7 -0
package/src/sections/welcome-overview.js +7 -0
package/src/seo.js +90 -0
package/src/styles.css +1982 -0
package/src/syntax-highlight.js +90 -0
package/tenants.json.example +68 -0
package/tenants.schema.json +231 -0

package/site/pages/deployment.html ADDED Viewed

@@ -0,0 +1,282 @@
+<!doctype html>
+<html lang="en">
+<head>
+  <meta charset="utf-8" />
+  <meta name="viewport" content="width=device-width, initial-scale=1" />
+  <title>Deployment | Pagenary Docs</title>
+  <meta name="description" content="Hosting the static output and multi-tenant domain routing." />
+  <link rel="canonical" href="/#deployment" />
+  <!-- Open Graph -->
+  <meta property="og:title" content="Deployment" />
+  <meta property="og:description" content="Hosting the static output and multi-tenant domain routing." />
+  <meta property="og:type" content="article" />
+  <meta property="og:url" content="/#deployment" />
+  <!-- Twitter Card -->
+  <meta name="twitter:card" content="summary" />
+  <meta name="twitter:title" content="Deployment" />
+  <meta name="twitter:description" content="Hosting the static output and multi-tenant domain routing." />
+  <!-- Structured Data -->
+  <script type="application/ld+json">
+[
+  {
+    "@context": "https://schema.org",
+    "@type": "TechArticle",
+    "headline": "Deployment",
+    "description": "Hosting the static output and multi-tenant domain routing.",
+    "url": "/#deployment",
+    "dateModified": "2026-05-26",
+    "mainEntityOfPage": {
+      "@type": "WebPage",
+      "@id": "/#deployment"
+    },
+    "isPartOf": {
+      "@type": "WebSite",
+      "name": "Pagenary Docs",
+      "url": "/"
+    }
+  },
+  {
+    "@context": "https://schema.org",
+    "@type": "BreadcrumbList",
+    "itemListElement": [
+      {
+        "@type": "ListItem",
+        "position": 1,
+        "name": "Home",
+        "item": "/"
+      },
+      {
+        "@type": "ListItem",
+        "position": 2,
+        "name": "Reference",
+        "item": "/#reference"
+      },
+      {
+        "@type": "ListItem",
+        "position": 3,
+        "name": "Deployment",
+        "item": "/#deployment"
+      }
+    ]
+  }
+]
+  </script>
+  <!-- Redirect to SPA for JavaScript-enabled browsers -->
+  <script>
+    if (typeof window !== 'undefined') {
+      window.location.replace('/#deployment');
+    }
+  </script>
+  <noscript>
+    <meta http-equiv="refresh" content="0; url=/#deployment" />
+  </noscript>
+  <link rel="stylesheet" href="../styles.css" />
+  <style>
+    .static-content { max-width: 800px; margin: 0 auto; padding: 2rem; }
+    .static-footer { margin-top: 3rem; padding-top: 1rem; border-top: 1px solid #eee; font-size: 0.9rem; color: #666; }
+  </style>
+</head>
+<body>
+  <main class="static-content">
+    <article>
+      <h1>Deployment</h1>
+      <p class="lead">Hosting the static output and multi-tenant domain routing.</p>
+      <div class="section-body">
+<section class="section doc markdown">
+  <div class="doc-content">
+<h1 id="deployment-guide">Deployment Guide</h1>
+<p>Pagenary produces static files that can be served by any web server, CDN, or object storage.</p>
+<h2 id="quick-deploy">Quick Deploy</h2>
+<pre><code class="language-bash"># Build a tenant to a specific directory
+node scripts/build-tenants.js my-tenant --target /var/www/docs
+# The output is ready to serve - no server setup required</code></pre>
+<h2 id="build-options">Build Options</h2>
+<h3 id="custom-output-directory">Custom Output Directory</h3>
+<pre><code class="language-bash"># Override target for all tenants
+node scripts/build-tenants.js --target /var/www/html
+# Build specific tenant to custom location
+node scripts/build-tenants.js my-docs --target /opt/docs/my-docs</code></pre>
+<h3 id="build-from-git-repository">Build from Git Repository</h3>
+<p>Configure a git source in your registry:</p>
+<pre><code class="language-json">{
+  &quot;tenants&quot;: [
+    {
+      &quot;id&quot;: &quot;my-docs&quot;,
+      &quot;source&quot;: {
+        &quot;type&quot;: &quot;git&quot;,
+        &quot;url&quot;: &quot;https://github.com/org/my-docs.git&quot;,
+        &quot;ref&quot;: &quot;main&quot;,
+        &quot;path&quot;: &quot;docs/&quot;
+      },
+      &quot;target&quot;: {
+        &quot;type&quot;: &quot;local&quot;,
+        &quot;path&quot;: &quot;/var/www/my-docs&quot;
+      }
+    }
+  ]
+}</code></pre>
+<p>Then build:</p>
+<pre><code class="language-bash">node scripts/build-tenants.js my-docs</code></pre>
+<h3 id="external-registry">External Registry</h3>
+<p>Use a registry file from any location:</p>
+<pre><code class="language-bash">node scripts/build-tenants.js --registry /etc/pagenary/tenants.json</code></pre>
+<p>Or via environment variable:</p>
+<pre><code class="language-bash">TENANT_REGISTRY=/etc/pagenary/tenants.json node scripts/build-tenants.js</code></pre>
+<h3 id="git-authentication">Git Authentication</h3>
+<p>For private repositories:</p>
+<pre><code class="language-bash"># SSH key
+GIT_SSH_COMMAND=&quot;ssh -i ~/.ssh/deploy_key&quot; node scripts/build-tenants.js
+# HTTPS token
+GIT_CREDENTIALS=&quot;username:token&quot; node scripts/build-tenants.js
+# Disable interactive prompts (recommended for CI)
+GIT_TERMINAL_PROMPT=0 node scripts/build-tenants.js</code></pre>
+<h2 id="cicd-integration">CI/CD Integration</h2>
+<h3 id="github-actions">GitHub Actions</h3>
+<pre><code class="language-yaml">name: Build Docs
+on:
+  push:
+    branches: [main]
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: &#39;20&#39;
+      - run: npm ci
+      - name: Build documentation
+        run: node scripts/build-tenants.js my-docs --target ./output
+      - name: Upload artifact
+        uses: actions/upload-artifact@v4
+        with:
+          name: docs
+          path: output/</code></pre>
+<h3 id="gitlab-ci">GitLab CI</h3>
+<pre><code class="language-yaml">build-docs:
+  image: node:20
+  script:
+    - npm ci
+    - node scripts/build-tenants.js my-docs --target ./public
+  artifacts:
+    paths:
+      - public/</code></pre>
+<h3 id="incremental-builds">Incremental Builds</h3>
+<p>For faster CI builds with git-based sources:</p>
+<pre><code class="language-bash"># Only rebuild changed content
+node scripts/build-tenants.js my-docs --incremental --keep-cache
+# Show what changed without building
+node scripts/build-tenants.js my-docs --diff-only</code></pre>
+<h2 id="hosting-patterns">Hosting Patterns</h2>
+<h3 id="static-file-servers">Static File Servers</h3>
+<p>The build output is self-contained. Serve with any static server:</p>
+<pre><code class="language-bash"># Python
+python -m http.server 8080 -d /var/www/my-docs
+# Node.js (npx)
+npx serve /var/www/my-docs
+# Caddy
+caddy file-server --root /var/www/my-docs --listen :8080</code></pre>
+<h3 id="nginx">Nginx</h3>
+<pre><code class="language-nginx">server {
+    listen 80;
+    server_name docs.example.com;
+    root /var/www/my-docs;
+    location / {
+        try_files $uri $uri/ /index.html;
+    }
+    # Cache static assets
+    location ~* \.(js|css|png|jpg|ico)$ {
+        expires 1y;
+        add_header Cache-Control &quot;public, immutable&quot;;
+    }
+}</code></pre>
+<h3 id="caddy">Caddy</h3>
+<pre><code class="language-caddyfile">docs.example.com {
+    root * /var/www/my-docs
+    file_server
+    try_files {path} /index.html
+    @static path *.js *.css *.png *.jpg *.ico
+    header @static Cache-Control &quot;public, max-age=31536000, immutable&quot;
+}</code></pre>
+<h3 id="s3-cloudfront">S3 + CloudFront</h3>
+<p>1. Create S3 bucket with static website hosting</p>
+<p>2. Upload build output:</p>
+<pre><code class="language-bash">   aws s3 sync /var/www/my-docs s3://my-docs-bucket/</code></pre>
+<p>3. Create CloudFront distribution pointing to S3</p>
+<p>4. Set default root object to `index.html`</p>
+<p>5. Configure error pages to return `index.html` for 404s (for hash routing)</p>
+<h3 id="netlify-vercel">Netlify / Vercel</h3>
+<p>1. Point to your repository</p>
+<p>2. Build command: `node scripts/build-tenants.js my-docs --target ./dist`</p>
+<p>3. Publish directory: `dist/`</p>
+<h2 id="multi-tenant-deployment">Multi-Tenant Deployment</h2>
+<h3 id="single-server-multiple-tenants">Single Server, Multiple Tenants</h3>
+<p>Build all tenants to subdirectories:</p>
+<pre><code class="language-bash">node scripts/build-tenants.js --target /var/www/docs
+# Creates /var/www/docs/tenant-a/, /var/www/docs/tenant-b/, etc.</code></pre>
+<p>Nginx config:</p>
+<pre><code class="language-nginx">server {
+    listen 80;
+    root /var/www/docs;
+    location ~ ^/([^/]+)/ {
+        try_files $uri $uri/ /$1/index.html;
+    }
+}</code></pre>
+<h3 id="domain-based-routing">Domain-Based Routing</h3>
+<p>Each tenant gets its own domain:</p>
+<pre><code class="language-caddyfile">tenant-a.example.com {
+    root * /var/www/docs/tenant-a
+    file_server
+    try_files {path} /index.html
+}
+tenant-b.example.com {
+    root * /var/www/docs/tenant-b
+    file_server
+    try_files {path} /index.html
+}</code></pre>
+<h2 id="cache-strategy">Cache Strategy</h2>
+<table><thead><tr><th style="text-align: left">Asset</th><th style="text-align: left">Cache Policy</th></tr></thead><tbody><tr><td style="text-align: left">`index.html`</td><td style="text-align: left">`no-cache` or short TTL (1 minute)</td></tr><tr><td style="text-align: left">`<em>.js`, `</em>.css`</td><td style="text-align: left">Long TTL with immutable (`max-age=31536000, immutable`)</td></tr><tr><td style="text-align: left">`sections/*.js`</td><td style="text-align: left">Long TTL (content-addressed)</td></tr></tbody></table>
+<p>The hash-based router means all navigation works client-side, so `index.html` is the only file that needs frequent updates.</p>
+<h2 id="monitoring">Monitoring</h2>
+<h3 id="health-check">Health Check</h3>
+<p>Create a simple health endpoint by checking for `index.html`:</p>
+<pre><code class="language-bash">curl -f https://docs.example.com/ || exit 1</code></pre>
+<h3 id="build-verification">Build Verification</h3>
+<p>After deployment, verify the build:</p>
+<pre><code class="language-bash"># Check response
+curl -I https://docs.example.com/
+# Verify content
+curl -s https://docs.example.com/ | grep -q &quot;manifest.js&quot;</code></pre>
+  </div>
+</section>
+      </div>
+    </article>
+    <footer class="static-footer">
+      <p>View interactive version: <a href="/#deployment">Deployment</a></p>
+    </footer>
+  </main>
+</body>
+</html>

package/site/pages/developer-guide.html ADDED Viewed

@@ -0,0 +1,157 @@
+<!doctype html>
+<html lang="en">
+<head>
+  <meta charset="utf-8" />
+  <meta name="viewport" content="width=device-width, initial-scale=1" />
+  <title>Developer Guide | Pagenary Docs</title>
+  <meta name="description" content="Project layout, scripts, and the content authoring workflow." />
+  <link rel="canonical" href="/#developer-guide" />
+  <!-- Open Graph -->
+  <meta property="og:title" content="Developer Guide" />
+  <meta property="og:description" content="Project layout, scripts, and the content authoring workflow." />
+  <meta property="og:type" content="article" />
+  <meta property="og:url" content="/#developer-guide" />
+  <!-- Twitter Card -->
+  <meta name="twitter:card" content="summary" />
+  <meta name="twitter:title" content="Developer Guide" />
+  <meta name="twitter:description" content="Project layout, scripts, and the content authoring workflow." />
+  <!-- Structured Data -->
+  <script type="application/ld+json">
+[
+  {
+    "@context": "https://schema.org",
+    "@type": "TechArticle",
+    "headline": "Developer Guide",
+    "description": "Project layout, scripts, and the content authoring workflow.",
+    "url": "/#developer-guide",
+    "dateModified": "2026-05-26",
+    "mainEntityOfPage": {
+      "@type": "WebPage",
+      "@id": "/#developer-guide"
+    },
+    "isPartOf": {
+      "@type": "WebSite",
+      "name": "Pagenary Docs",
+      "url": "/"
+    }
+  },
+  {
+    "@context": "https://schema.org",
+    "@type": "BreadcrumbList",
+    "itemListElement": [
+      {
+        "@type": "ListItem",
+        "position": 1,
+        "name": "Home",
+        "item": "/"
+      },
+      {
+        "@type": "ListItem",
+        "position": 2,
+        "name": "Guides",
+        "item": "/#guides"
+      },
+      {
+        "@type": "ListItem",
+        "position": 3,
+        "name": "Developer Guide",
+        "item": "/#developer-guide"
+      }
+    ]
+  }
+]
+  </script>
+  <!-- Redirect to SPA for JavaScript-enabled browsers -->
+  <script>
+    if (typeof window !== 'undefined') {
+      window.location.replace('/#developer-guide');
+    }
+  </script>
+  <noscript>
+    <meta http-equiv="refresh" content="0; url=/#developer-guide" />
+  </noscript>
+  <link rel="stylesheet" href="../styles.css" />
+  <style>
+    .static-content { max-width: 800px; margin: 0 auto; padding: 2rem; }
+    .static-footer { margin-top: 3rem; padding-top: 1rem; border-top: 1px solid #eee; font-size: 0.9rem; color: #666; }
+  </style>
+</head>
+<body>
+  <main class="static-content">
+    <article>
+      <h1>Developer Guide</h1>
+      <p class="lead">Project layout, scripts, and the content authoring workflow.</p>
+      <div class="section-body">
+<section class="section doc markdown">
+  <div class="doc-content">
+<h1 id="developer-guide">Developer Guide</h1>
+<p>Welcome to Pagenary Publisher. This workspace lives at `apps/publisher/` inside the Pagenary platform monorepo. Use the repo-level commands (e.g. `npm run publisher:*`) when you prefer not to `cd` into the workspace. This guide keeps onboarding fast so you can focus on tailoring tenant-specific copy rather than plumbing.</p>
+<h2 id="prerequisites">Prerequisites</h2>
+<ul>
+<li>Node.js 16+</li>
+<li>npm (ships with Node)</li>
+<li>Optional: a modern browser for local testing, and a static host account for deployment</li>
+</ul>
+<h2 id="install-run">Install &amp; Run</h2>
+<pre><code class="language-bash">npm install
+npm run dev</code></pre>
+<p>The dev command builds to `dist/` and serves the bundle with live reload. Open the printed URL and start exploring.</p>
+<h2 id="project-tour">Project Tour</h2>
+<ul>
+<li>`src/index.html` – HTML entry point with top-level shell structure</li>
+<li>`src/app.js` – navigation, routing, command palette, export logic</li>
+<li>`src/sections/section-templates.js` – template catalogue for every page type</li>
+<li>`src/manifest.js` – default navigation structure (overridden per tenant via `tenants/&lt;id&gt;/manifest.json`)</li>
+<li>`scripts/` – small Node utilities for building, serving, syncing sections, linting content, and checking SEO metadata</li>
+</ul>
+<h2 id="key-features">Key Features</h2>
+<p>1. <strong>Mermaid Diagrams</strong> - Use fenced code blocks with `mermaid` language. Renders with zoom/pan controls and pan-on-drag functionality.</p>
+<p>2. <strong>External Links</strong> - Links to external URLs (http/https) automatically open in new tab with security attributes. Use `url` property in manifest for external nav links.</p>
+<p>3. <strong>Internal Linking</strong> - Link between sections with `#section-id` syntax. Build validates that all internal links reference existing sections.</p>
+<p>4. <strong>Bottom Navigation</strong> - Configurable via `bottomNav` in root manifest. Options: &quot;mobile&quot; (default), &quot;always&quot;, or &quot;never&quot;.</p>
+<p>5. <strong>Command Palette</strong> - Press Ctrl+K (or Cmd+K) to search and navigate sections. Supports fuzzy search across section titles and summaries.</p>
+<p>See TENANT-CONFIG.md for full configuration details and examples.</p>
+<h2 id="common-tasks">Common Tasks</h2>
+<ul>
+<li><strong>Add a Section</strong> – create `src/sections/my-section.js`, set the `SECTION_ID`, update `manifest.js`.</li>
+<li><strong>Regenerate Templates</strong> – run `npm run sync:docs` to reset section boilerplate if you need a clean slate.</li>
+<li><strong>Branding</strong> – tweak the logo text and footer copy in `src/index.html`; adjust colors in `src/styles.css`.</li>
+<li><strong>Export Testing</strong> – open the app locally and use the Export button to confirm the combined PDF-ready document looks correct.</li>
+</ul>
+<h2 id="tenant-content-bundles">Tenant Content Bundles</h2>
+<ul>
+<li>Each tenant folder supports a `manifest.json` describing nav groupings, titles, and the content file backing each section. Use nested `sections` arrays to create expandable groups.</li>
+<li>Supported content types live in `tenants/&lt;id&gt;/content/`:</li>
+<li>`.md` → converted to structured HTML (headings, lists, blockquotes supported by the lightweight parser).</li>
+<li>`.html` → shipped as-is, wrapped in a loader module.</li>
+<li>`.js` → copied unchanged; export a `load()` function that returns `{ html, afterRender? }` to drive rich experiences.</li>
+<li>Run `npm run build:tenants` after editing content. The script regenerates `dist/&lt;id&gt;/manifest.js` plus section modules so the navigation immediately reflects the manifest.</li>
+<li>Provide per-tenant overrides (styles, assets, app shell tweaks) inside `tenants/&lt;id&gt;/overrides/`; they copy into the tenant bundle after content generation, so you can replace generated files if needed.</li>
+</ul>
+<h2 id="tooling-philosophy">Tooling Philosophy</h2>
+<ul>
+<li>Zero framework lock-in; replace `app.js` with your own router if you outgrow it.</li>
+<li>Scripts avoid third-party dependencies so they run in restricted environments.</li>
+<li>Everything is ASCII-only by default to ease diffs and downstream localization.</li>
+</ul>
+<h2 id="support-checklist">Support Checklist</h2>
+<p>Before shipping to a tenant:</p>
+<p>1. Replace placeholder copy with real content.</p>
+<p>2. Verify navigation order and summaries in `manifest.js`.</p>
+<p>3. Run `npm run check` to ensure lint and SEO checks pass.</p>
+<p>4. Test export output and section highlighting.</p>
+  </div>
+</section>
+      </div>
+    </article>
+    <footer class="static-footer">
+      <p>View interactive version: <a href="/#developer-guide">Developer Guide</a></p>
+    </footer>
+  </main>
+</body>
+</html>

package/site/pages/extending.html ADDED Viewed

@@ -0,0 +1,135 @@
+<!doctype html>
+<html lang="en">
+<head>
+  <meta charset="utf-8" />
+  <meta name="viewport" content="width=device-width, initial-scale=1" />
+  <title>Extending | Pagenary Docs</title>
+  <meta name="description" content="Add section templates, content types, and build behaviors." />
+  <link rel="canonical" href="/#extending" />
+  <!-- Open Graph -->
+  <meta property="og:title" content="Extending" />
+  <meta property="og:description" content="Add section templates, content types, and build behaviors." />
+  <meta property="og:type" content="article" />
+  <meta property="og:url" content="/#extending" />
+  <!-- Twitter Card -->
+  <meta name="twitter:card" content="summary" />
+  <meta name="twitter:title" content="Extending" />
+  <meta name="twitter:description" content="Add section templates, content types, and build behaviors." />
+  <!-- Structured Data -->
+  <script type="application/ld+json">
+[
+  {
+    "@context": "https://schema.org",
+    "@type": "TechArticle",
+    "headline": "Extending",
+    "description": "Add section templates, content types, and build behaviors.",
+    "url": "/#extending",
+    "dateModified": "2026-05-26",
+    "mainEntityOfPage": {
+      "@type": "WebPage",
+      "@id": "/#extending"
+    },
+    "isPartOf": {
+      "@type": "WebSite",
+      "name": "Pagenary Docs",
+      "url": "/"
+    }
+  },
+  {
+    "@context": "https://schema.org",
+    "@type": "BreadcrumbList",
+    "itemListElement": [
+      {
+        "@type": "ListItem",
+        "position": 1,
+        "name": "Home",
+        "item": "/"
+      },
+      {
+        "@type": "ListItem",
+        "position": 2,
+        "name": "Guides",
+        "item": "/#guides"
+      },
+      {
+        "@type": "ListItem",
+        "position": 3,
+        "name": "Extending",
+        "item": "/#extending"
+      }
+    ]
+  }
+]
+  </script>
+  <!-- Redirect to SPA for JavaScript-enabled browsers -->
+  <script>
+    if (typeof window !== 'undefined') {
+      window.location.replace('/#extending');
+    }
+  </script>
+  <noscript>
+    <meta http-equiv="refresh" content="0; url=/#extending" />
+  </noscript>
+  <link rel="stylesheet" href="../styles.css" />
+  <style>
+    .static-content { max-width: 800px; margin: 0 auto; padding: 2rem; }
+    .static-footer { margin-top: 3rem; padding-top: 1rem; border-top: 1px solid #eee; font-size: 0.9rem; color: #666; }
+  </style>
+</head>
+<body>
+  <main class="static-content">
+    <article>
+      <h1>Extending</h1>
+      <p class="lead">Add section templates, content types, and build behaviors.</p>
+      <div class="section-body">
+<section class="section doc markdown">
+  <div class="doc-content">
+<h1 id="extending-docs-toolkit">Extending Docs Toolkit</h1>
+<p>This project is meant to be forked or templated per reseller. Everything lives in vanilla modules, so extending it is a matter of editing a handful of files.</p>
+<h2 id="add-a-new-page-type">Add a New Page Type</h2>
+<p>1. Update `section-templates.js` with a new category configuration (summary + render function).</p>
+<p>2. Create a section file in `src/sections/` that imports `renderSectionTemplate` and sets `SECTION_ID` to match the slug you want.</p>
+<p>3. Register the slug inside `src/manifest.js` under the appropriate group (or create a new group entry).</p>
+<p>Run `npm run sync:docs` to regenerate the boilerplate module if you want to reapply the standard wrapper.</p>
+<h2 id="override-styling">Override Styling</h2>
+<ul>
+<li>Adjust global tokens and typographic scale in `src/styles.css`.</li>
+<li>Use existing utility classes (`doc-content`, `doc-grid`, etc.) when adding new markup blocks.</li>
+<li>Keep the high-contrast palette for accessibility unless brand guidelines state otherwise; test color contrast if you change it.</li>
+</ul>
+<h2 id="inject-dynamic-data">Inject Dynamic Data</h2>
+<p>While the bundle is static, section modules can directly fetch remote JSON or call APIs. Recommended approach:</p>
+<pre><code class="language-js">export async function load() {
+  const res = await fetch(&#39;https://api.example.com/tenant/metrics.json&#39;);
+  const metrics = await res.json();
+  return {
+    html: renderCustomTemplate(metrics)
+  };
+}</code></pre>
+<p>Keep requests idempotent and cache-friendly—most hosts allow short-lived fetches if end users need fresh stats.</p>
+<h2 id="internationalisation">Internationalisation</h2>
+<ul>
+<li>Duplicate `manifest.js` with translated summaries or hydrate labels at runtime via a locale switcher.</li>
+<li>Wrap static strings in template helpers so copy updates stay centralized.</li>
+</ul>
+<h2 id="automation-ideas">Automation Ideas</h2>
+<ul>
+<li>Add a content pipeline that transforms Markdown into HTML and swaps it into templates.</li>
+<li>Integrate accessibility scans (axe, pa11y) into CI alongside the provided lint/SEO scripts.</li>
+</ul>
+  </div>
+</section>
+      </div>
+    </article>
+    <footer class="static-footer">
+      <p>View interactive version: <a href="/#extending">Extending</a></p>
+    </footer>
+  </main>
+</body>
+</html>