Jekyll sites & documentation

A Jekyll site is a folder of HTML. That sentence is the entire security model, the entire scaling story and most of the maintenance plan.

We use it for the sites where uptime matters more than novelty: product and marketing sites, documentation portals, public-sector handbooks, conference sites, statutory disclosure pages. The kind of thing that has to survive a front-page traffic spike on a Tuesday and an unattended August.

What you get

Content lives in Markdown in your Git repository, reviewed in pull requests like everything else. Editors who do not use Git get a web interface that commits on their behalf. The build runs in your CI, produces a directory, and that directory is served by nginx or a CDN from Stockholm or Falkenstein.

There is no database to back up, no runtime to patch on a Sunday, no plugin marketplace to audit, and no admin login to brute-force. When we hand it over, the whole system is legible to any developer who knows HTML.

Where it is the wrong tool

If you need per-user state, a checkout flow, or content that changes minute by minute, we will tell you to use Rails instead — and then quote you for that. Static generation is a sharp tool with a clear edge, and pretending otherwise would cost you more than it costs us.