blazorstatic.net

What It Is

BlazorStatic is a static site generation library for the .NET Blazor ecosystem. Its core idea is to run a Blazor app, use HttpClient to fetch the HTML for each page, and then output those HTML files together with static assets from wwwroot/RLC and elsewhere into an output folder. The generated result is a set of ordinary static files, so it can be hosted on any standard HTTP server or static hosting platform.

Core Capabilities

It is best suited to developers who are already familiar with Blazor/Razor: you can keep using Blazor components, Razor pages, and your existing CSS setup. The documentation indicates support for Markdown content parsing, custom YAML front matter, automatic Razor page discovery, adding or removing pages, HotReload, and dotnet new templates. The content model can be customized by implementing IFrontMatter, while directory structure and output behavior can be configured through BlazorStaticOptions. It is not tied to any specific UI framework; the examples mention Tailwind, and the docs also provide entry points for integrating with FluentUI or other component libraries.

Pricing and Deployment

The documentation does not mention any paid plans. Usage options include installing the BlazorStatic.Templates template or adding the BlazorStatic NuGet package. Deployment is one of its strengths: the output directory can be deployed to GitHub Pages, Netlify, Vercel, Cloudflare Pages, Azure Static Web Apps, and similar platforms. More concrete CI/CD examples are provided for GitHub Pages and Netlify, while the Azure Static Web Apps section is marked as not yet tested.

Pros and Cons

The main advantages are low migration cost for Blazor users, simple and transparent generated output, and good suitability for blogs, documentation sites, personal websites, and showcase sites. The template includes sample content, GitHub Actions, and GitHub Pages configuration, making the onboarding path fairly clear. The downsides are that it requires .NET SDK 8+, is clearly positioned within the Blazor ecosystem, and may not be worth adopting for non-.NET users. Some documentation pages are still marked as under construction, and certain capabilities require reading blog posts or example source code to understand. Its maturity still needs to be proven compared with established tools such as Hugo, Astro, and Docusaurus.

Who It’s For and Access from China

It is a good fit for individual developers or small teams that want to use Blazor across the stack and deploy content sites as static files. If your team mainly uses React/Vue or wants a more mature content ecosystem, alternatives such as Astro, Docusaurus, Hugo, and Jekyll may be worth considering. The documentation does not provide information about access from China. Actual reachability of the domain and related GitHub/Netlify/Cloudflare services may vary depending on network conditions, so it is recommended to test access speed and CI/CD availability before deployment.