Use Fission components where design matters and Markdown content routes where documentation, references, blogs, and changelogs need to scale.
Custom pages
Designed landing pages
Homepages and product pages are normal Fission widgets rendered to static HTML at build time.
Content routes
Markdown at scale
Documentation and reference pages come from content folders, front matter, explicit sidebars, generated headings, and templates.
SEO
Static output
The site shell emits ordinary HTML, CSS, metadata, search indexes, assets, favicon links, and structured data support.
Site architecture
Custom routes and content routes solve different jobs.
A production static site needs designed pages, navigable content, metadata, assets, search, generated CSS, and publishing output.
Custom pages
Marketing pages are widgets
Homepages and product pages are normal Fission component trees, so layout, theme, links, imagery, and footer structure stay in Rust instead of a separate template language.
Folders under `content/` become route trees with front matter, sidebars, tables, code blocks, in-page links, metadata, generated blog landing pages, and search data.