The problem
Content sites built with Blazor need pages that render completely on the server, work without JavaScript, and can be published as static files, with content kept in Git rather than in a database.
Role
Author and maintainer: the architecture, the components, the CMS, the releases, and the security hardening.
Key decisions
- Static SSR first. Every component renders correctly under static server-side rendering before any interactivity is layered on, so a site can be exported to plain files.
- Modules, not a monolith. Core components, the CMS, navigation, analytics and theming ship as separate packages that a site combines as it needs.
- Content from Git. A GitHub provider and a file-system provider read Markdown with front matter, and the same content feeds the pages, the sitemap and the RSS and Atom feeds, as this site shows.
- Secure by default. Rendered HTML is sanitized with an allow-list, unsigned webhooks are rejected, and admin pages require an authorization policy.
Where it stands
Version 4.0.0 is on NuGet, with more than 2,000 unit tests. It runs the Hexavera website and this site.