You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Once Bridgetown 2.0's out the door, it will be full steam ahead for positioning Bridgetown as a fullstack framework for small to medium-size web application projects. We should document some of the basic steps for how to transition from Rails to Bridgetown.
User management via rodauth & Authtown plugin (coming soon)
Bridgetown view templates and components
Forms via Lifeform plugin (coming soon)
esbuild frontend asset management
Using libraries like swup, i-html, etc. instead of Turbo, and web components instead of Stimulus
And once Heartml is out the door, we'll have a full client-server web components rendering pipeline
We might even imagine what would be a traditional Rails backoffice business application, and implement an example application purely in Bridgetown/Roda.
The text was updated successfully, but these errors were encountered:
We already have a page about Jekyll here: https://www.bridgetownrb.com/docs/migrating-from
Once Bridgetown 2.0's out the door, it will be full steam ahead for positioning Bridgetown as a fullstack framework for small to medium-size web application projects. We should document some of the basic steps for how to transition from Rails to Bridgetown.
We might even imagine what would be a traditional Rails backoffice business application, and implement an example application purely in Bridgetown/Roda.
The text was updated successfully, but these errors were encountered: