Pages
Company-site starter routes, injected defaults, and the limits of YAML page flags.
The current shell does not use publier.config.yaml#pages flags to create or suppress routes. A flag does not remove a route from navigation, sitemap, search, or RSS.
docsShell() injects docs, blog, and changelog routes when their content directories contain entries, plus a default 404 route. Its existing routes integration option can disable all injected routes with routes: false, or select defaults with these keys:
Each key defaults to true; setting it to false disables that injected default.
docsShell({ routes: { ... } }) key | Default routes controlled |
|---|---|
docs | /docs/[...slug] |
blog | /blog, /blog/[slug], and the blog feed |
changelog | /changelog and the changelog feed |
notFound | Default /404 |
rss | Blog and changelog feeds; these also require site.url |
These switches control shell-injected defaults, not your files in src/pages/. The company-site template supplies its six company pages as Astro files. Status and knowledge-base routes must be authored separately; the shell does not supply them automatically. Keep navigation links consistent with the routes you actually publish.
Customizing a page
The company-site template scaffolds .astro files in src/pages/ for each of its six sub-pages — edit them in place to update copy, components, or layout.
For any page type, drop a file at the matching path in src/pages/ to add or customize the page:
src/pages/about.astro → adds or replaces /aboutsrc/pages/changelog.astro → adds or replaces /changelogsrc/pages/404.astro → adds or replaces the 404 handlerCompany-site sub-pages
Six pages for marketing and company information, pre-scaffolded by the company-site template. Pages like Landing, Team, Press, and Careers use @publier/shell components; About and Contact are plain HTML starters.
Standard pages
Changelog and 404 have shell-injected defaults. Status and knowledge base are examples of custom pages you can author with existing components.