Skip to content

Features Overview

BlazorForge ships with everything you need to build a production-ready Blazor WebAssembly application. This page lists every feature and what it does.

BlazorForge is built on .NET 8 and .NET 9, using Blazor WebAssembly as the primary render mode. The components also work in Blazor Server and Interactive Auto mode.

The entire theme is written in pure C# Razor components. There is no JavaScript framework, no npm dependency, and no TypeScript compilation. When you run dotnet build, everything compiles.

The theme includes seven pages, each fully designed and ready to use.

The Home page contains a hero section with call-to-action buttons, a statistics strip, a features section, a flagship showcase, testimonials, a pricing section with multiple cards, a services banner, an FAQ accordion, and a bottom call-to-action.

The About page contains a hero section, a vision and mission section, a company timeline, a team section, and a closing call-to-action.

The Services page lists all services in a grid with pagination. Each service card links to its detail page.

The Service Detail page shows the full description of a service, its features, its specifications, and a call-to-action button.

The Journal page lists all journal articles in a grid with pagination. Each article card shows the cover image, category tag, author, date, and excerpt.

The Journal Detail page shows the full article with cover image, metadata bar, article content, tag list, author card, and previous/next navigation.

The Contact page contains a contact form with validation, an aside with contact information, and an FAQ accordion.

BlazorForge includes a complete component library covering the most common UI patterns. Components include navigation menus, mobile drawers, hero sections, feature cards, service cards, journal cards, testimonial cards, pricing cards, CTA banners, breadcrumbs, pagination, tag lists, author cards, previous/next navigation, FAQ accordions, forms with validation, contact info cards, stat strips, showcase banners, and more.

Every component follows the Microsoft Fluent 2 design system and passes WCAG 2.1 AA accessibility requirements.

The design system follows Microsoft Fluent 2 specification. Colors, typography, spacing, elevation, and focus states all match the specification used in Azure Portal and Microsoft 365 admin centers.

All design tokens are CSS variables defined at the top of wwwroot/css/style.css. Change a single variable and the entire site updates.

BlazorForge is built with accessibility in mind. Every page uses semantic HTML, includes ARIA labels on interactive elements, supports full keyboard navigation, manages focus correctly, and maintains sufficient color contrast.

The theme passes government and enterprise accessibility audits on the first try without any modifications.

Decap CMS is included as an optional admin panel. Content editors can log in through a browser, edit journal articles, update service pages, change the site name, modify the navigation menu, and publish changes without touching a single file.

Decap CMS works in two modes. In local mode, it runs on your development machine and saves changes directly to your working directory. In online mode, it connects to GitHub through Netlify Identity and Git Gateway, allowing your entire team to edit content from anywhere.

All content is stored as Markdown files with YAML frontmatter and JSON configuration files. There is no database.

Journal articles, service pages, and static pages are Markdown files. Site configuration, SEO defaults, navigation, footer, and widgets are JSON files.

This approach means content is version-controlled, portable, and easy to migrate. You can edit content with any text editor, and you can move it between environments without database migrations.

BlazorForge handles SEO automatically. Every page gets a title with a configurable template, a meta description, keywords, a canonical URL, Open Graph tags, Twitter Card tags, and JSON-LD structured data.

Structured data includes Organization, Article, FAQ, and Breadcrumb schemas. All values are configurable through site-wide defaults or per-page overrides.

The Markdown compiler generates three additional files on every build.

A sitemap.xml file lists every page on the site, with priority and last-modified date. Submit this to Google Search Console.

A feed.xml file provides an RSS feed of journal articles. RSS readers and aggregators discover it automatically.

A robots.txt file tells search engine crawlers how to index the site, and points them to the sitemap.

BlazorForge does not include any third-party JavaScript libraries. There is no React, no Vue, no jQuery, and no utility libraries.

The only JavaScript in the project is the Blazor WebAssembly runtime itself, plus a small main.js file that handles a few DOM interactions.

This means faster load times, fewer security vulnerabilities, and easier maintenance.

Every page and component is responsive, following a mobile-first approach. The theme uses breakpoints at 768 pixels and 1024 pixels, and every layout adapts to screen width.

Mobile navigation collapses into a drawer. Grids reduce their column count. Typography scales down. Every interaction works on touch devices.

BlazorForge deploys as static files. It works on Netlify, Cloudflare Pages, Vercel, Azure Static Web Apps, GitHub Pages, Firebase Hosting, and any static host that serves HTML, CSS, JavaScript, and WebAssembly files.

The documentation includes step-by-step guides for Netlify, Cloudflare, and Vercel.

Every purchase includes lifetime updates. When a new version of BlazorForge is released, you receive an email with a download link. Bug fixes, security patches, and new components are all included at no additional cost.

BlazorForge does not include a backend, database, or API. It is a frontend theme.

BlazorForge does not include authentication. You can add ASP.NET Core Identity, Microsoft Entra ID, or any other authentication provider.

BlazorForge does not include multi-language support out of the box. The structure supports adding it, but you need to implement the routing and content structure yourself.

BlazorForge does not include dark mode. The design uses a light theme. If you need dark mode, you can add it by extending the CSS variables.

If you are ready to install BlazorForge, see Requirements and Download and Install.

If you want to know what is not included, see the FAQ page.