Skip to content
Agon ĀtriumAgon Ātrium

Source code

Open source page

Agon Ātrium showcase site

Read the repository’s AGENTS.md, the matching agent guidance, and development setup. Resolve repository paths relative to this skill’s directory, two levels up. The site build and hosting guide owns the public demo artifact and environments.

Keep showcase ownership clear

The demonstration application is src/showcase/, published as @agon/atrium-showcase. Keep domain records, simulated sessions, adapters, and sample workflows there. Reusable components and styles belong in src/atrium/ and must remain usable by the independent starter. Use the theme skill when a demonstration requires shared component, theme, or template changes. Read architecture and component contracts for those boundaries.

  • Maintain route definitions in src/showcase/config/routes.js and the component catalogue in src/showcase/config/components.js. Keep example templates and controllers under pages/, shared demo partials under partials/, and translations under locales/. Synchronize changed examples with their component guides.
  • Preserve lazy route loading, CSP-compatible Alpine providers, capability checks, cancellation, focus, and controller teardown. Demo authentication and API simulations demonstrate behavior and do not provide production backend authorization. Use backend integration for real application contracts.
  • Keep branding and demo preferences in the consumer configuration and styles. Follow theming and preserve responsive layouts, RTL, and supported palette and navigation modes.
  • Follow asset provenance for media. Use the presentation video skill for narration, product-tour screenshots, video regeneration, and editable decks. Only final presentation WebM files belong in showcase assets. Authoring inputs and companion artifacts remain under docs/presentation/.

Verify the application and public artifact

Use yarn dev for the local showcase and yarn build followed by yarn preview for its production preview. Run the affected unit and production browser workflows from maintainer verification. Browser checks are required for markup, styling, routing, lifecycle, and layout changes. Preserve direct-route reloads, subdirectory assets, genuine missing-asset responses, and PDF worker behavior. Use the packed-package consumer checks when template layout, exports, or publication allowlists change.

For the public site, follow the guide’s build and preview procedure. yarn sites:prepare builds both applications and the documentation, then qualifies the showcase into .build/showcase/release/. src/scripts/documentation/prepare-showcase.js owns that preparation despite its directory name. Keep its source revision and per-file integrity inventory intact. Use yarn sites:images and yarn sites:test for actual NGINX container acceptance. Stop owned previews and report any local images or services retained.

For hosting or delivery changes, read CI guidance and the site’s CI artifact chain. The public showcase uses the demo environment and image identifiers. Keep its Docker and NGINX configuration in resources/infrastructure/.docker/ and its Coolify Compose definition in resources/infrastructure/.deploy/demo/. External publication and deployment require the user’s authorization, and hosted delivery jobs must never run locally. Preserve immutable image references and stable-release eligibility for production.

Author

Laurent Declercq l.declercq@agon-innovation.ch

Version

Version: 20260921