Cobalt

Rust SSG, Liquid-compatible. Niche, well-engineered.

VISIT COBALT

Key takeaway: There is one reason to choose Cobalt over Hugo or Zola: you want Liquid templates and a Rust binary in the same tool. That is a narrow overlap, and outside it you are trading a large community and theme ecosystem for a preference in template syntax. Jekyll users who want single-binary builds without learning new templating are the natural fit.

Quick facts

  • LanguageRust
  • CategoryRust
  • LicenseMIT
  • Created2015
  • GitHub stars0.8k
  • Statusactive

Templating: Liquid Markdown

What it is

Cobalt is a Rust SSG with Jekyll-compatible Liquid templates. Single binary, fast builds, small community. Useful for Jekyll users who want to migrate to a Rust toolchain.

Best for

  • Jekyll users wanting a faster Rust-based equivalent
  • Rust-aligned teams wanting a Liquid-based SSG

When not to pick it

For most teams Hugo or Zola will give you a bigger community. Cobalt is a niche pick.

My take

Niche but well-built. Hugo or Zola will serve most teams better.

A single Rust binary that speaks Liquid

Cobalt is a compiled binary with no runtime to install, which puts it in the same operational category as Hugo and Zola: drop the executable into CI, run one command, get HTML. The differentiator is templating. Where Hugo makes you learn Go templates and Zola makes you learn Tera, Cobalt uses Liquid, so anyone who has written Jekyll or Shopify templates is productive immediately. Front matter, collections, and pagination behave roughly the way a Jekyll user expects them to. That combination is genuinely useful for a team that inherited Liquid templates and wants builds measured in seconds without a Ruby version manager in the pipeline. The templating is Jekyll-flavoured rather than a wholesale compatibility layer, though, so plugins and gem-based themes have no equivalent and anything they were quietly doing has to be rethought.

Why Hugo or Zola usually wins the argument

Community size is not a vanity metric for a build tool, it is how quickly you get unstuck at 6pm on a launch day. Hugo has thousands of themes, multilingual routing, taxonomies, and an image pipeline in the binary, plus over a decade of answered questions. Zola sits in the middle with a smaller but active following, Tera templates most people find readable, and search index generation built in. Cobalt has a very small maintainer group and a release cadence that reflects it, so treat it as a stable tool rather than one that will grow new capabilities to meet your next requirement. For a personal site or a docs build with fixed requirements, that is fine. For anything a client depends on, the safer answer is Hugo, and the reason is support surface rather than raw capability.

Frequently asked questions

Can Cobalt build my existing Jekyll site unchanged?

Not unchanged. The Liquid templating is Jekyll-flavoured so much of it carries over, but Jekyll plugins and theme gems have no equivalent and anything relying on them needs rebuilding. Simple blogs with stock templates port with modest editing; sites with custom plugins or unusual collections need real work. Test with a copy first.

Cobalt or Zola?

Zola for almost everyone: larger community, better documentation, Tera templating, built-in search index generation, and a faster development pace. Cobalt only if Liquid syntax specifically matters to you, usually because you are arriving from Jekyll and want to keep templates you already have. Both are single Rust binaries with broadly similar build performance.

Is Cobalt suitable for a client project?

For a small, fixed-scope site whose requirements will not change, it works and it is well built. For anything with a growth path or a support obligation, pick Hugo. The deciding factor is not code quality, it is how much community help exists when something unexpected breaks a build on a deadline.

Links

Similar tools you should also consider

If Cobalt 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 Cobalt is genuinely the right call for you, and what the build actually looks like.