CMS pages

These components turn the items of a content provider into pages: lists, single articles, whole page layouts and the metadata search engines read. They are in the Osirion.Blazor.Cms.Web package and read from the default provider through IContentProviderManager, so register a content provider first (see CMS Web components).

Most live in the Osirion.Blazor.Cms.Web.Components namespace. DocumentPage, HomePage and LandingPage live in Osirion.Blazor.Cms.Components, next to the section components.

@using Osirion.Blazor.Cms.Web.Components
@using Osirion.Blazor.Cms.Components

Components

Choosing one

• Need a list? Use ContentList; it also writes the list page's head metadata.
• Need an article page with little code? ArticlePage (used by the example site) loads an item by slug or URL and renders the hero, breadcrumbs, table of contents and head metadata. ContentPage is the older, simpler layout and writes no head metadata.
• Need a documentation page? Use DocumentPage. For the home, about, contact, landing and not found pages there are HomePage, AboutPage, ContactPage, LandingPage and NotFoundPage.
• Building your own layout? Combine ContentView or ContentRenderer with a SeoMetadataRenderer in <HeadContent>.

Shared behavior

• Everything renders under static SSR. Links are ordinary links, and no component here needs script; only code highlighting in ContentRenderer loads Prism when the content has code blocks.
• Content HTML is sanitized before it is written: the providers sanitize Markdown output when they load it, and ContentView, LocalizedContentView and ContentRenderer sanitize again, which covers custom providers and items you create in code. Widen the allow-list with AddOsirionHtmlSanitizer when your content needs a custom element.
• Category and tag links default to /category/{slug} and /tag/{slug}; LocalizedContentView, and therefore ContentPage, puts the locale in front (/en/category/{slug}). Each component takes formatter parameters when your routes differ.
• A page or view that renders a not-found state also answers HTTP 404 (NavigationManager.NotFound() on .NET 10, the status code of the request on .NET 9): ArticlePage, AboutPage, HomePage, DocumentPage, ContentPage, ContentView, LocalizedContentView and LandingPage with a ContentPath. The page components also take their NotFound* and BackLink* parameters for that state and pass their SEO parameters on to SeoMetadataRenderer.
• ContentView and LocalizedContentView write the title as an h1; set HeadingLevel when you embed one in a page that has its own. Their images take the alt text from the featured_image_alt entry of custom_fields in the front matter, and are decorative (empty alt) without it.