Skip to content

FAQ

This page answers common questions about BlazorForge.

You need the .NET 9 SDK and a code editor. The .NET SDK is free and available from the official Microsoft download page. Any editor works, but Visual Studio 2022 Community, JetBrains Rider, and VS Code are the most common.

No, unless you want to run Decap CMS in local mode. If you only want to run the theme, you do not need Node.js. If you want to edit content through the CMS while developing, install Node.js from the official website.

Does BlazorForge work on Windows, macOS, and Linux?

Section titled “Does BlazorForge work on Windows, macOS, and Linux?”

Yes. The .NET SDK is available for all three platforms, and BlazorForge has no operating-system-specific code.

How much disk space does BlazorForge need?

Section titled “How much disk space does BlazorForge need?”

About fifty megabytes after extraction. After the first build, it grows to about two hundred megabytes because of compiled binaries and the NuGet cache. Plan for at least five hundred megabytes of free space.

Open a terminal in the project folder and run dotnet run. Wait for the terminal to print Now listening on: http://localhost:5052, then open that URL in your browser.

The first run restores NuGet packages, compiles the project, and downloads the .NET WebAssembly runtime. It takes one to three minutes. Subsequent runs take five to ten seconds.

Press Ctrl + C in the terminal where the server is running.

Edit Properties/launchSettings.json and change the number in the applicationUrl field. For example, change http://localhost:5052 to http://localhost:5053.

Why do I see “The ASP.NET Core developer certificate is not trusted”?

Section titled “Why do I see “The ASP.NET Core developer certificate is not trusted”?”

This is a warning, not an error. The site runs normally. To trust the certificate permanently, run dotnet dev-certs https --trust in a terminal and click Yes when prompted.

All content is stored as Markdown and JSON files. Journal articles, service pages, and static pages are Markdown files in wwwroot/content/. Site configuration, SEO defaults, navigation, footer, and widgets are JSON files in wwwroot/data/.

No. BlazorForge does not use a database. Content is stored in plain files.

You can edit content two ways. The first is to open the Markdown and JSON files directly with a text editor. The second is to use Decap CMS, a browser-based admin panel included with BlazorForge.

Do I need to restart the server after editing content?

Section titled “Do I need to restart the server after editing content?”

Yes. After editing a Markdown file, stop the server with Ctrl + C and run dotnet run again. The Markdown compiler regenerates the metadata, and the changes appear after you refresh the browser.

Yes. Decap CMS provides a browser-based editor for every piece of content. Non-developers can edit articles, service pages, site settings, and navigation without opening a single file.

Images uploaded through Decap CMS are stored in wwwroot/images/uploads/. The path is filled into the field automatically as /images/uploads/filename.jpg.

Decap CMS is a free, open-source admin panel. It provides a browser-based editor for content stored as Markdown and JSON files.

Do I need a GitHub account to use Decap CMS?

Section titled “Do I need a GitHub account to use Decap CMS?”

Not if you use Netlify Identity. With Netlify Identity and Git Gateway, editors log in with an email and password. No GitHub account is required.

What is the difference between local mode and online mode?

Section titled “What is the difference between local mode and online mode?”

In local mode, the CMS runs on your development machine and saves changes directly to your working directory. It requires the decap-server tool. In online mode, the CMS runs on the deployed site and saves changes to GitHub through Netlify Identity and Git Gateway.

How do I switch between local and online mode?

Section titled “How do I switch between local and online mode?”

The only change is one line in wwwroot/admin/config.yml. Set local_backend: true for local mode. Set local_backend: false for online mode.

The most common cause is a missing or incorrect Netlify Identity widget script in wwwroot/admin/index.html. Verify that the widget script is loaded in the head section and the redirect script is present before the closing body tag.

Verify that the URL ends with a trailing slash. For example, https://yoursite.com/admin/, not https://yoursite.com/admin.

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.

Netlify is recommended because it includes Netlify Identity and Git Gateway, which are needed for online Decap CMS. Cloudflare Pages is faster at serving static files but does not include an identity system.

Why does the Netlify build fail with “dotnet: command not found”?

Section titled “Why does the Netlify build fail with “dotnet: command not found”?”

Netlify may not have the correct .NET version. The project includes a build.sh file that installs .NET 9 before building. Verify that netlify.toml uses chmod +x build.sh && ./build.sh as the build command.

This is a routing issue. The netlify.toml file must include a redirect rule that sends all routes to index.html with status 200. Verify that the redirect is present.

The first build takes three to five minutes because the build agent downloads and installs the .NET SDK. Subsequent builds take two to three minutes.

Yes. All colors are CSS variables defined at the top of wwwroot/css/style.css. Change --color-primary to your brand color and the entire site updates.

Yes. Edit wwwroot/data/site.json. The name, tagline, and logo fields control the header and footer.

Yes. Create a Markdown file in wwwroot/content/ with the appropriate frontmatter, then create a Razor page in Pages/. The Developer Guide covers this in detail.

BlazorForge does not include dark mode out of the box. You can add it by extending the CSS variables and adding a theme toggle. The Developer Guide includes a starting point.

BlazorForge does not include multi-language support out of the box. You can add it by duplicating content into language-specific folders and updating the routing logic.

The license allows unlimited personal and commercial projects. You can use BlazorForge for client work, SaaS products, and internal enterprise applications. You can modify the source code for your projects.

You may not resell or redistribute BlazorForge as a theme, template, or boilerplate. You may not share the source code publicly. You may not claim authorship of the original design.

Can I use BlazorForge for multiple client projects?

Section titled “Can I use BlazorForge for multiple client projects?”

Yes. The license covers unlimited projects. There is no per-project fee.

Yes. BlazorForge comes with a fourteen-day money-back guarantee. If the theme does not meet your needs, email axcora@gmail.com within fourteen days of purchase for a full refund.

Updates are delivered through your Gumroad purchase. You receive an email whenever a new version is released, with a download link to the latest package. Updates are free for life.

Email support is included with every purchase. Response time is typically within one business day.

For custom .NET development, AI automation, or documentation sites, hire our team directly on Fiverr. Links are in the sidebar under Services.

Email axcora@gmail.com with a description of the bug, the steps to reproduce it, and the error message if any. Bug fixes are included in future updates.

BlazorForge uses Blazor WebAssembly, which requires the .NET WebAssembly runtime. It does not use any third-party JavaScript libraries. There is no React, Vue, or jQuery.

BlazorForge is tested and supported on .NET 8 LTS and .NET 9.

Yes. The Razor components work in Blazor Server, Blazor WebAssembly, and Interactive Auto render modes.

Does BlazorForge work with MAUI Blazor Hybrid?

Section titled “Does BlazorForge work with MAUI Blazor Hybrid?”

Yes. The Razor components work in .NET MAUI Blazor Hybrid applications for Windows, macOS, and mobile.

BlazorForge generates meta descriptions, keywords, canonical URLs, Open Graph tags, Twitter Card tags, and JSON-LD structured data automatically. The Markdown compiler also generates sitemap.xml, feed.xml, and robots.txt on every build.

BlazorForge works with static prerendering through the BlazorWasmPreRendering.Build package. See the Developer Guide for setup instructions.

If your question is not answered here, email axcora@gmail.com.

For developer-focused questions, see the Developer Guide starting at Architecture Overview.