And a last one:

• Deep dive: evilmartians.com/chronicles/the-future-of-full-stack-rails-turbo-view-transitions

Build a (progressively enhanced) drawer component with Hotwire You can get 90% of the way there with server-rendered templates and View Transitions.

Not that hard to use the View Transitions API with Hotwire and the result feels great 🤘

Cool reads if you’re curious:
• MDN: developer.mozilla.org/View_Transition_API
• Hotwire drawer: thoughtbot.com/blog/hotwire-drawer

I’m rebuilding the Maglev editor UI with Hotwire + ViewComponent.
Still work in progress but look at this animation test 👇
(VueJS on the left, Hotwire + View Transitions API on the right)

Same polish, no JS build chain.
Just Rails and a bit of CSS magic ✨

#RubyOnRails #Hotwire #MaglevCMS

I’m not doing this for the sake of chasing a trend.

The goal is to give Maglev users full control over the editor UI, including visual tweaks, custom workflows, and a future plugin system 🤩

I’m not migrating the Maglev editor UI to Vue 3 + Typescript.

No more Node/Yarn/NPM dependencies.
No more black-box transpilation to customize the editor.

Rebuilding everything with Hotwire + ViewComponent.
Same great UI/UX, fully Rails-native.

I’ll share the journey. Stick around 🤘

Thanks @adrianthedev.com, (again) perfect timing for my project! 🙏

Now I can say Sitepress.cc saved a company $1,080/year.

Just moved the Maglev docs off Gitbook (was paying $90/mo 😅).
Rebuilt the whole thing with @bradgessler.com 's Sitepress.cc — pure Markdown, Liquid & Ruby 💎 🙏
Like VuePress, but for Rails devs 🧱
→ docs.maglev.dev