Skip to content

Fix link to importmap-rails README heading #3

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Dec 16, 2021
Merged

Fix link to importmap-rails README heading #3

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion _posts/2021-12-15-Rails-7-fulfilling-a-vision.markdown
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ date: 2021-12-15 15:17:00 -08:00

This version of Rails has been years in the conceptual making. It's the fulfillment of a vision to present a truly full-stack approach to web development that tackles both the front- and back-end challenges with equal vigor. An omakase menu that includes everything from the aperitif to the dessert.

This vision wasn't possible even just a few years ago. We simply didn't have the core technologies in place. But with advancements in browser support for ES6/ESM, widespread adoption of HTTP/2, and [the exciting new standard for import maps](https://github.com/rails/importmap-rails), it's finally possible. Rails 7 takes advantage of all of these advances to deliver [a no-Node default approach to the front end](https://world.hey.com/dhh/modern-web-apps-without-javascript-bundling-or-transpiling-a20f2755) – without sacrificing either access to [npm packages](https://github.com/rails/importmap-rails#using-node-modules-via-javascript-cdns) or modern JavaScript in the process.
This vision wasn't possible even just a few years ago. We simply didn't have the core technologies in place. But with advancements in browser support for ES6/ESM, widespread adoption of HTTP/2, and [the exciting new standard for import maps](https://github.com/rails/importmap-rails), it's finally possible. Rails 7 takes advantage of all of these advances to deliver [a no-Node default approach to the front end](https://world.hey.com/dhh/modern-web-apps-without-javascript-bundling-or-transpiling-a20f2755) – without sacrificing either access to [npm packages](https://github.com/rails/importmap-rails#using-npm-packages-via-javascript-cdns) or modern JavaScript in the process.

[Hotwire](https://hotwired.dev)'s combination of [Turbo](https://turbo.hotwired.dev) and [Stimulus](https://stimulus.hotwired.dev) deliver all the tools needed to produce fantastic user experiences that leave little to nothing on the table in contrast to single-page applications – at a fraction of the complexity. It's the default choice for new Rails apps, replacing the far more limited options of Turbolinks and Rails UJS.

Expand Down