Turbo Drive: Add knowledge check questions

[Monatric]

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

Knowledge check is almost a staple for every lesson. However, the Turbo Drive lesson is oddly missing that important element.

I am proposing to add a knowledge check section in this lesson. Here are my few suggestions to include in knowledge check:

1. What is page navigation defined by Turbo Drive?
   • Link to the answer: https://www.theodinproject.com/lessons/ruby-on-rails-turbo-drive#page-navigation
2. What is the default visit action that adds a new entry to the browser history?
   • https://www.theodinproject.com/lessons/ruby-on-rails-turbo-drive#application-visit
3. How do you change the action of a Turbo Drive link?
   • Answer within the TOP lesson: <%= link_to "Edit Article", edit_article_path(@article), data: { turbo_action: "replace" } %>
4. How do you disable Turbo Drive?
   • https://www.theodinproject.com/lessons/ruby-on-rails-turbo-drive#disable-turbo-drive
5. What is the HTTP status code that Turbo cannot handle?
   • HTTP 200 OK
   • https://www.theodinproject.com/lessons/ruby-on-rails-turbo-drive#form-submissions
6. How do you require confirmation for a visit?
   • https://turbo.hotwired.dev/handbook/drive#requiring-confirmation-for-a-visit
7. How does Turbo speeds up perceived link navigation latency?
   • https://turbo.hotwired.dev/handbook/drive#prefetching-links-on-hover

My thought process with this selection is to further reinforce the understanding around link navigation, as forms are covered later in the course. This also aligns with the goal of the lesson's assignment.

Path

Ruby / Rails

Lesson Url

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

(Optional) Discord Name

Koko

(Optional) Additional Comments

No response

[wise-king-sullyman]

Thanks for taking the time to create this issue!

Seems like adding KCs for the lesson would be a great idea to me, though I would love to hear from someone on @TheOdinProject/rails-path to confirm that wasn't an intentional decision.

[JoshDevHub]

Thank you for making this issue @Monatric

I think this makes perfect sense, and I also like your suggestions for knowledge checks. Since you checked the box in the original post indicating you'd like to work on this, I'll assign you. Let me know if you have any questions.

[Monatric]

Thanks @JoshDevHub

I have completed the task just now and I am ready to submit a PR but I am not sure how since this involves an issue (first time doing it this way). In the contributing guide, there's this instruction:

• If the PR is meant to close an open issue, you must link that issue in Step 1 of the PR template. This can be done either by replacing the XXXXX with the issue number, e.g. Closes Update project_building_blocks.md #2013, or if the issue is in another TOP repo replacing the #XXXXX with the URL of the issue, e.g. Closes https://github.com/TheOdinProject/curriculum/issues/XXXXX. This streamlines the issue closing process, as an issue that is linked to a PR will be closed when that PR gets merged.

I want to know if that's exactly how to submit a PR, by just pushing the branch normally as before, and then adding the number of this issue to that PR.

Another concern is how will the Knowledge Check be added to the sidebar navigation of the lesson? I cannot view this in markdown preview tool if this is automatically added. Is this automatically added when the section title of the lesson contains triple hashtags ###?

[JoshDevHub]

@Monatric The sidebar will automatically update to accommodate your changes. That isn't something that's handled here in the curriculum Markdown, bur rather, by some frontend JavaScript code on the main site itself.

And yes, for the issue section, you want to write Closes #29803--so "Closes" followed by this issue number. Doing this will have a couple of effects:

• GitHub will add a link in this issue to your PR and will add a link to the PR in this issue. This just makes navigating between the two very convenient, which can be useful for people who are reviewing.
• Whenever the PR is approved and merged, GitHub will automatically close this issue as having been completed. This just saves a little manual maintenance work.

[Monatric]

Thank you @JoshDevHub

I opened a PR now: #29862