Bridgetown

Ruby-based, Jekyll's ambitious successor with modern frontend integration.

VISIT BRIDGETOWN

Key takeaway: Ruby teams who have outgrown Jekyll are the entire audience, and for them this is an upgrade rather than a compromise. Everything Bridgetown adds is what Jekyll never grew: a real component model, modern asset bundling, and partial hydration. If your team is not already writing Ruby daily, Eleventy or Astro give you the same shape with a far larger ecosystem behind them.

Quick facts

  • LanguageRuby
  • CategoryMulti-framework
  • LicenseMIT
  • Created2020
  • GitHub stars1.4k
  • Statusactive

Templating: Liquid ERB Serbea Markdown

What it is

Bridgetown started as a Jekyll fork in 2020 to escape the maintenance freeze and has matured into a Ruby-based modern SSG with Vite-style frontend integration, dynamic islands, and a real component model. Smaller community than Astro or Eleventy but a coherent vision.

Best for

  • Ruby teams that want a modern Jekyll replacement
  • Sites with rich content and a need for ESBuild / Vite asset pipelines
  • Editorial-heavy projects with components and partial hydration

When not to pick it

Skip Bridgetown if your team is not already on Ruby, the ecosystem is smaller and hiring is harder than with the JavaScript-based options. The capability gap to Astro or Eleventy is real on plugin breadth.

My take

Bridgetown is the right answer for a specific niche: a Ruby team that wants a modern Jekyll. Outside that niche the JS-based options will serve you better.

What it adds on top of the Jekyll model

Bridgetown kept the parts of Jekyll that worked, front matter, Liquid, a content folder, and replaced the parts that aged badly. Templates can be ERB or Serbea as well as Liquid, which matters because Liquid's deliberate limitations are exactly what makes complex Jekyll sites painful to maintain. The frontend pipeline is a modern bundler rather than a bolted-on arrangement, so Tailwind and TypeScript behave the way a current Ruby developer expects. There is a component model built on Ruby classes, a resource system that provides taxonomies and pagination without plugin hunting, and a dynamic islands mechanism for the small amount of interactivity a content site actually needs. For a Rails shop this is the shortest distance between templating your team already knows and a site that does not feel a decade behind the rest of your stack.

Ecosystem size is the whole risk

Bridgetown is small. The plugin count is a fraction of Jekyll's, the number of people who can answer a question at 2am is low, and the project depends on a very small core team, which is a real bus-factor consideration for a site you expect to run for years. Weigh that honestly, because the alternative is not staying on Jekyll forever. Migration in is the easiest path available: Liquid templates and front matter largely carry over, and you can convert incrementally rather than rewriting. Migration out is harder, since ERB and Serbea templates and Ruby components translate to nothing in the JavaScript world, so an eventual move to Astro means rebuilding the view layer. Choose it knowing you are choosing the Ruby ecosystem for the life of the site, not just for this build.

Frequently asked questions

Is Bridgetown a drop-in Jekyll replacement?

Close, but not literal. Liquid templates, front matter, and Markdown content mostly move across, and the folder conventions are recognisable. What does not transfer is Jekyll plugins, which have no direct equivalent, and any theme gem you depend on. Budget a day or two for a straightforward blog, considerably longer if you lean on plugins.

Bridgetown or Astro?

Bridgetown if your team writes Ruby every day and wants to stay there, particularly alongside an existing Rails application. Astro for everything else: bigger ecosystem, more hiring options, better image handling, and multi-framework islands. The deciding question is which language your team wants to maintain for years, not which tool is more capable on paper.

Does Bridgetown support partial hydration?

Yes. It has a dynamic islands mechanism for hydrating individual interactive components rather than shipping a client framework across the whole site, alongside a modern bundler for assets. It is not as broad as Astro's multi-framework island support, but it covers the interactivity a typical editorial or marketing site genuinely needs.

Links

Similar tools you should also consider

Jekyll

The original SSG. Liquid templates, Ruby, Markdown. GitHub Pages' backbone.

Read the take →

Astro

Multi-framework, content-first, ships zero JS by default. The default for SEO-heavy sites.

Read the take →

Eleventy (11ty)

Zero-config JS-based SSG. Templates only, no client-side JS framework.

Read the take →

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