Content Sections and Routes

Overview

• section components (Hero, CallToAction, InfoCards, FeatureGrid, Testimonials)
• route templates for pages, articles, and docs
• docs-index filtering/search/pagination with URL-state sync
• fragment utility integration via getFragment()

Who this is for

• Implementors composing pages from section components or modifying route templates
• Developers working on route contracts, docs-index behavior, or fragment integration

Route Contracts

Pages

• src/pages/[...slug].astro is generated only from non-draft pages collection entries.
• Reserved top-level prefixes are excluded from generated paths to avoid route shadowing.
• Unknown slugs return Astro default 404 behavior.

Articles

• Canonical listing route: /articles/
• Paginated listing route: /articles/page/{n}/
• Detail route: /articles/{slug}/

Article detail optionally renders TOC when toc: true and H2/H3 headings are present.

Docs

• Docs index route: /theme-docs/
• Docs detail route: /theme-docs/{slug}/
• Showcase routes remain under /theme-docs/showcase/* and are included in docs-index discoverability.

Docs detail supports frontmatter-driven TOC visibility and a fallback heading scan path when server heading data is unavailable.

Section Component Notes

• Hero is the unified heading-band component, rendered in PageGridLayout subheader. Without actions or image it renders as a compact page-title band; with actions or image it renders as a full hero.
• InfoCards, FeatureGrid, and Testimonials do not render their own headings. Callers compose headings as siblings using the Heading primitive or use LayoutSection label for screen-reader-only naming.
• InfoCards and FeatureGrid share clickable-card behavior:
  • full-card click defaults on when one link exists
  • full-card click auto-disables when multiple links exist
  • item-level fullCardClick can override section default behavior

Fragment Utility

getFragment(fragmentId) resolves a published fragments entry and returns Astro render output for composition.

• valid IDs resolve a { Content, headings, remarkPluginFrontmatter } payload
• invalid IDs throw immediately (fail-fast behavior)

Use showcase route /theme-docs/showcase/showcase-page-content/ for manual verification.