@FediFollows thanks for the shoutout! 😊
A next-generation, progressive site generator & fullstack framework, powered by Ruby.
@FediFollows thanks for the shoutout! 😊
@mb21 Rewrites, yes.
The experience of working in a static-first architecture is very different than just aggressively caching a dynamic server. But YMMV depending on what your project needs are.
@mb21 You can use Render for both actually! Deploy a static site and a server using the same commits, via the render.yaml file—even "punch holes" through the CDN for certain SSR routes. We're polishing up docs for this currently.
@sleepyfox Wow, that's a blast from the past!
Happy Birthday Bridgetown! 🎉
Five years ago today, a project was born to create a new kind of web framework—certainly one unlike any previously seen in the #Ruby community.
(And yes, we're still working on getting v2.0 final out the door—soon, #WebDev friends, soon!)
https://www.bridgetownrb.com/news/bridgetown-turns-five-today/
I sometimes need to spin up new test projects for @bridgetown to verify a bugfix or some other issue…
…and I was **today years old** when it occured to me I could name the project folder starting with the issue number:
```
bridgetown new 987_test_something_out
```
Now when viewing a sea of test folders I know *exactly* what this one is all about! (And when I can safely delete it!)
🏆 Open source maintainer achievement unlocked. 😅
All the #RubyOnRails web apps requires #ruby to work. Fortunately, not all ruby web apps requires Rails to work.
@gregw Hanami is cool indeed!
Don't discount Roda either! (And @bridgetown, if you want more of a framework wrapping it)
I'm always sad when I hear folks talk about leaving Ruby because of not wanting to use the Big Framework 😟 (but I do get it)
The Bridgetown progressive #Ruby #WebDev framework is racing to the 2.0 finish line!
While we don’t have a specific process for offering “release candidates”, we consider this Beta 4 release to be essentially an RC. Feature development is now frozen, and the only additional updates we anticipate will be major bug fixes only.
Read the post for all the latest goodies in v2.0 Beta 4!
https://www.bridgetownrb.com/release/countdown-to-production-release/
Bridgetown 2024: Year in Review
This year has been a pivotal one for the Bridgetown #Ruby #WebDev framework. We started off 2024 on some conceptual shaky ground, uncertain about the direction Bridgetown should head in next, but over the spring and summer we really hit our stride and are finishing out the year in a strong position.
Some stats for Bridgetown in 2024:
6 releases, 3 in the 2.0 beta line
15 contributors across releases
Grew by roughly 200 stars on GitHub…
Bridgetown 2024: Year in Review
This year has been a pivotal one for the Bridgetown #Ruby #WebDev framework. We started off 2024 on some conceptual shaky ground, uncertain about the direction Bridgetown should head in next, but over the spring and summer we really hit our stride and are finishing out the year in a strong position.
Some stats for Bridgetown in 2024:
6 releases, 3 in the 2.0 beta line
15 contributors across releases
Grew by roughly 200 stars on GitHub…
I have rebuilt my tiny corner of the Internet, https://nerdd.dk, and it is finally online! 🎉
It is generated with @bridgetown v2.0.0.beta3.
It is nothing fancy. Nevertheless, I am very pleased with it.
The @bridgetown #Ruby web framework used to regenerate an entire static site on each change. Fine for smaller sites, but could take seconds on larger ones!
But now with Fast Refresh, only verifiably stale pages get rebuilt, and the browser reloads almost instantly—a huge quality of life improvement. DX at its finest.
What ✨ magic ✨ made this possible? Dependency-tracking via linked lists and closures—aka Signals. What the what? Let’s dive in.
Beta 3 of the Bridgetown 2.0 web framework has now been released, featuring a major performance boost for full builds, ESM support for all local configuration files of the frontend pipeline (no more CommonJS!), i18n support for fast refresh, and more.
And ICYMI, all of the amazing features of Bridgetown 2.0 such as new tech baselines, better defaults, greater dev performance, enhanced full-stack application support, and a whole lot more.
https://www.bridgetownrb.com/release/bridgetown-2.0-beta-3-with-better-performance/
Beta 3 of the Bridgetown 2.0 web framework has now been released, featuring a major performance boost for full builds, ESM support for all local configuration files of the frontend pipeline (no more CommonJS!), i18n support for fast refresh, and more.
And ICYMI, all of the amazing features of Bridgetown 2.0 such as new tech baselines, better defaults, greater dev performance, enhanced full-stack application support, and a whole lot more.
https://www.bridgetownrb.com/release/bridgetown-2.0-beta-3-with-better-performance/
It's been on my to-do list for a while, but I've finally removed all uses of "just", "simple", "simply", and "straightforward" from the @bridgetown docs ....
I spent part of my day today attempting to avoid undue stress by working on two things I love very much: Ruby & web components. To wit, a Ruby-based custom elements rendering layer. The project had taken a back seat earlier in the year, but I'm gung ho to get a public beta out before winter. 🤘
All right, so yesterday I spent quite a lot of time tending to my "digital garden" as it relates to open source.
I archived or deleted a number of old projects that had been abandoned for sometime, and clarified the status of some things. I also used my internal wiki to write up the current status of a bunch of plugins and features as we gear up for @bridgetown v2.0 (and the wiki is powered by Bridgetown!)
I now feel more confident & less overwhelmed to work on active projects for Q4. Yay!! 🎉
Today's issue of the Fullstack #Ruby #newsletter has just gone out!
Subscribe and don't miss another groovy issue all about #WebDev with this plucky language.
Contents:
* Top 10 Most Excellent Gems to Use in Any Ruby Web Application
* Podcast: Designing Your API for Their API (Yo Dawg!)
* Bridgetown 2.0 is in Beta!
* Support Fullstack Ruby with Intuitive+
https://buttondown.com/fullstackruby/archive/designing-your-api-for-their-api-top-gems/
Most people would be better off with a simple static site than Wordpress.
Static sites are faster, cheaper, and easier to edit. And because you own your content in plain text you can more easily switch site generator or host. You're can't be held hostage.