builder-ecosystem-page-author

To create an ecosystem package page, define the package repo boundary, add concise positioning notes, and link to relevant examples and upstream repositories for catalog alignment. The page enforces boundary clarity and feature documentation to maintain catalog consistency.

Updating ecosystem package pages requires refreshing positioning notes, boundary definitions, and companion links. You must ensure feature notes remain accurate and companion links to examples and upstream repositories align with current catalog standards.

Ecosystem package page boundaries explicitly separate the package repository scope from the workbench narrative. Defining these boundaries ensures catalog entries maintain clear positioning and prevent scope overlap between package features and workbench documentation.

Yes, ecosystem package pages support companion links to relevant examples, guides, and upstream repositories. Linking these resources provides necessary context for users browsing the workbench ecosystem catalog and ensures package documentation remains connected to source materials.

Workbench ecosystem catalog standards require explicit boundary definitions, concise feature notes, and valid companion links. Package pages must align with these standards by maintaining consistent positioning and ensuring all entries follow the established catalog formatting guidelines.

Refresh an existing ecosystem package page when boundary definitions or feature notes need updating, or companion links require reconnection. Create a new page only when adding a previously undocumented package to the workbench ecosystem catalog.