Bridgetown Web Framework

(Re)Introducing the only #Ruby #WebDev framework which bridges the gap between static Markdown sites and fullstack database-driven application deployments.

Bridgetown 2.0 “River City” has been released! 🎉

This version has long been in the hopper, and it’s chock full of major quality-of-life improvements. It marks the arrival of a mature and stable foundation on which to build the next generation of content sites and “vanilla” web applications.

🤓 Read all the deets!
https://www.bridgetownrb.com/release/bridgetown-v2-river-city-released/

Good Times in River City: Bridgetown 2.0 is Here!

Introducing the only Ruby web framework which bridges the gap between static Markdown sites and fullstack database-driven application deployments.

Bridgetown
Sep 16, 2025 at 6:35pmWeb
Show threadmb21Sep 16, 2025

Congrats! 👏

I’m curious about the fast refresh: is this about the development server, or incremental regeneration across production builds?

Show threadBridgetown Web FrameworkSep 16, 2025
@mb21 It's just during the runtime of the dev server.
Show threadmb21Sep 17, 2025

Ah, but why do you need a (re-)build of the entire site in dev mode? Just to make sure there are no errors in other routes? Because otherwise you could just render the one route that was requested from the dev server? Or what tradeoff am I missing?

btw. I’ve done a bit of thinking around that an hybrid static/server sites and arrived at https://mastrojs.github.io/guide/bundling-assets-caching/#transforming-images

Bundling, pregenerating assets and caching | Mastro

Show threadRasmus Grouleff (he/him)Sep 16, 2025
@bridgetown Congrats! 🥳
Show threadBridgetown Web FrameworkSep 16, 2025
@nerdd thank you!
Show threadZach LeathermanSep 22
@bridgetown Congratulations on the release!!
Show threadBridgetown Web FrameworkSep 23
@zachleat Thank you! Bridgetown 🤝 Eleventy 😊