The official, production release of Bridgetown 1.0 will occur some time next week (i.e., before March). So if there are any last minute bugs or major DX enhancements you’d like to see slip in before then, please hop on over to our GitHub repo and let us know!
We’ll be officially ending our 1.0 fundraising effort at the end of this month. As of the time of this writing, we have reached $3,763, or nearly 80% of our goal of raising $5,000. Will we at least make it to $4,000 before the final tally? I sure hope so! 😄
I soon plan to write up a “debrief” of my thoughts on the fundraiser (which overall I’m very pleased with) and what we might do differently in the future. In the meantime, please consider contributing to help us shore up our documentation, fix last-minute bugs, and get a polished 1.0 release out the door.
I continue to be gratified hearing all the positive feedback from Rubyists young and ol…erm, vintage 😏 as they try out Bridgetown for the first time. Tweets like these are music to my ears. We’ll continue to strive earnestly to make Bridgetown the best website construction kit available! ✌️
Bridgetown represents an evolution of thinking from previous generations of tools in this space, especially within the Ruby ecosystem. The pace of progress on the web never stands still, and neither will Bridgetown.
We put a stake in the ground at the very beginning of the Bridgetown project that we’d embrace frontend developers via first-party Webpack integration. Now it’s time to move on and embrace the speed and flexibilty of esbuild.