CMS Web Core Components

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

@using Osirion.Blazor.Cms.Web.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.
• 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.