Key takeaway: The only real argument here is toolchain consistency: a .NET shop that wants Razor templates and no Node in CI. Note that this project's active continuation is Statiq, so new work should start there rather than on Wyam itself. Teams without a .NET constraint get more from Hugo or Astro.
Quick facts
- LanguageC#
- Category.NET
- LicenseMIT
- Created2014
- GitHub stars1.7k
- Statusactive
Templating: Razor Markdown
What it is
Wyam (now Statiq) is a .NET-based SSG. Razor templates, Markdown, mature in the .NET community. Niche outside that audience.
Best for
- .NET teams wanting a Razor-based SSG
- Projects where the toolchain stays in .NET
When not to pick it
For non-.NET teams the toolchain cost is real. Pick Hugo, Astro, or Eleventy.
My take
Niche pick for .NET teams. Outside that audience, broader options will serve you.
Razor templating in a C# pipeline
For a .NET team the appeal is straightforward: Razor syntax you already write, C# for any custom logic, and a build that runs on the SDK your CI already installs. The engine is pipeline-based, so generation is a sequence of modules that read documents, transform them, and write output, which is closer to Metalsmith in spirit than to Jekyll. That composability earns its keep when content comes from somewhere unusual, a database, an internal API, or generated from source annotations, because you write a module in C# instead of fighting a plugin system in a language your team does not use daily. There is also a documentation-oriented variant that generates .NET API documentation, which is the standout feature for a library author who wants reference docs and marketing pages produced by one build rather than two.
Wyam, Statiq, and picking the right repository
Wyam was renamed and rebuilt as Statiq, so the Wyam repository is the historical version and ongoing work happens under the new name. If you are evaluating this today, evaluate Statiq: same origins, same pipeline idea, restructured into a framework plus ready-made site generators layered on top. Anyone maintaining an existing Wyam site should plan the move rather than assume the old packages keep receiving attention. The broader risk is community size. This is a small project serving a corner of the .NET world, which means few themes, few worked examples, and a maintainer concentration worth thinking about before a long commitment. Hugo is the pragmatic alternative when all you actually need is a fast binary and Markdown, with no requirement that the toolchain be .NET.
Frequently asked questions
Is Wyam the same as Statiq?
Effectively yes. Statiq is the renamed and rebuilt continuation of Wyam, from the same origins, restructured into a core framework with prebuilt generators layered on top. Wyam is the historical name and repository. New projects should start on Statiq, and existing Wyam sites should treat migration as planned work rather than assuming the older packages will keep pace.
Do I need .NET installed to use it?
Yes. It is a .NET application, so your development machines and your CI runners need the SDK. That is the entire point for a .NET shop, since it means no Node toolchain in the build and one runtime to keep patched. It is also the entire reason not to choose it if your team is not already on .NET.
Wyam or Hugo for a .NET team?
Hugo if all you need is Markdown in and fast HTML out, because it is a single binary with a much larger theme and tutorial base. The .NET option if you want C# extensibility, Razor templates, or API reference generated from your own code. The question is whether you will write custom pipeline code, since that is where staying in .NET pays off.
Links
Similar tools you should also consider
If Silverwind / Wyam is your pick, the next conversation is short
The 30-min call is where your project gets a real architecture, an SEO transport plan, and a price range you can take to your team. Describe your site, your timeline, your existing content. I tell you whether Silverwind / Wyam is genuinely the right call for you, and what the build actually looks like.