Documentation

AWCMS-Micro docs and operating notes

This plugin surfaces the workspace guidance that keeps AWCMS-Micro aligned with EmDash while preserving the approved downstream boundaries.

README.md

Root entry point for the workspace and sync model.

AGENTS.md

Agent execution rules for the parent workspace.

docs/implementation-instructions.md

How to work inside the maintenance layer.

docs/synchronization-workflow.md

How upstream refreshes flow into the dev workspace.

docs/awcms-micro-implementation-boundaries.md

The rebuild-safe path allowlist and preservation rules.

docs/operator-workflow.md

Continuation vs fresh-clone guidance for operators.

awcmsmicro-dev/docs/awcms-micro/public-landing-page-standard.md

Standard components and patterns for public landing pages derived from reference repos.

Reference PRD

The SIKESRA reference PRD frames the example standard without turning it into production SIKESRA code.

In scope: the docs boundary, the SIKESRA plugin, both templates, and E2E coverage.
Reference goals: plugin/runtime shape, public-safe aggregate, registry and verification screens, masked fixtures, and validation guidance.
Execution order: document the standard, build the reference plugin and fixtures, align admin UI, align both templates, then harden E2E validation.

Published pages are editable from the standard Pages collection and can be surfaced from the docs hub.

About AWCMS-Micro

/about

The parent repo is a maintenance layer, not a runtime host.

`emdash-latest/` stays as the upstream reference tree.
`awcmsmicro-dev/` is rebuilt from upstream and then receives approved AWCMS-Micro overlays.
`scripts/` owns the sync and validation workflow for both trees.

Rebuilds must stay deterministic and reversible.

Check runtime prerequisites before any sync or validation step.
Rebuild `awcmsmicro-dev/` from `emdash-latest/` with the protected-path allowlist.
Restore only approved downstream paths and patch overlays after the rebuild.

AWCMS-Micro-owned work lives in explicit plugin, template, docs, demo, and release paths.

Plugins: `packages/plugins/awcms-micro-sikesra`, `packages/plugins/awcms-micro-gallery`, `packages/plugins/awcms-micro-docs`, and `packages/plugins/awcms-micro-website-social`.
Templates: `templates/awcms-micro-default` and `templates/awcms-micro-default-cloudflare`.
Docs and release metadata stay inside the approved downstream boundaries listed in the implementation-boundaries document.

Both templates include standard landing page sections driven by D1 configuration.

PromoPopup — sticky trigger and overlay with WhatsApp CTA, auto-shows after 2s, dismissed state in sessionStorage.
FAQ accordion — details/summary pattern with animated chevron, copy managed in messages.ts.
Footer location section — Google Maps iframe embed, business address, opening hours, and directions link from website_social D1 fields.
Floating WhatsApp CTA — locale-aware, driven by website_social collection.
Gallery — managed by awcms-micro-gallery plugin at /gallery.