Turbo Drive: Improve context and overview

[doronmi]

Checks

• This is not a duplicate of an existing issue (please have a look through our open issues list to make sure)
• I have thoroughly read and understand The Odin Project Contributing Guide
• Would you like to work on this issue?

Describe your suggestion

As someone who is new to Rails and Turbo, I am missing some more context.
Specifically, it would have helped me to understand what problems or new capabilities exactly are being served with Turbo, and how Turbo is actually implemented. Is it a JS library or a Rails proccess? is it running on the server side or the client side? Does the browser have a function in the proccess?

Path

Ruby / Rails

Lesson Url

https://www.theodinproject.com/lessons/ruby-on-rails-turbo-drive

(Optional) Discord Name

No response

(Optional) Additional Comments

No response

[rlmoser99]

Thank you for this feedback. You're right that the lesson could better explain what Turbo is before diving into implementation details.

We should add the following in the "Turbo drive" section (before explaining how it handles navigation):

• What Turbo is technically: A JavaScript library that ships with Rails by default
• Where it runs: Client-side in the browser
• What problem it solves: Traditional full page reloads are slow, lose JavaScript state, and require re-downloading assets
• How it works at a high level: Turbo intercepts browser link clicks and form submissions, makes the request via JavaScript, and swaps out page content without a full reload

Would adding this context address your concerns?

[ZackHoang]

I can take this up if needed

[rlmoser99]

Perfect! @ZackHoang I have assigned you to this issue.