nebula-workbench-pages

To enforce canonical Canvas Workbench pages, place active previews in the top-level pages/ directory. This repository policy prevents the accidental use of examples/pages/ reference material as canonical Workbench previews during local validation.

Workbench pages should live in pages/ to separate canonical visual verification targets from reference material. The examples/pages/ directory is reference-only, ensuring repository workflows and CI checks operate on the intended active Canvas pages.

To validate Canvas Workbench pages locally, create active previews in the pages/ directory and run nebula-component-validation. This performs repo-local static checks to ensure adherence to the canvas-page-definition contract.

Yes, Nebula workflows require a specific directory structure for Workbench page previews. Active Canvas pages must reside in the top-level pages/ directory, while examples/pages/ is kept strictly as reference material.

The canvas-page-definition contract defines the required structure for page previews. Authors must adhere to this contract when creating canonical Workbench pages in the pages/ directory to pass repo-local static validation checks.

No, examples/pages/ is reference-only and cannot be used for active Canvas Workbench previews. The repository policy mandates that canonical Workbench previews must live in the top-level pages/ directory to prevent validation errors.