Rails Turbo Drive: Add knowledge check section with 7 questions

[Monatric]

Because

The Turbo Drive lesson is oddly missing knowledge checks, in contrast with other lessons that do contain them. This PR adds 7 knowledge check questions, with links to the answer, and added some span tags as necessary. This PR should allow users to reflect more towards link navigation with Turbo.

This PR

• Add 7 knowledge check questions
• Add 3 span tags for redirection to the answer

Issue

Closes #29803

Additional Information

Pull Request Requirements

• I have thoroughly read and understand The Odin Project curriculum contributing guide
• The title of this PR follows the location of change: brief description of change format, e.g. Intro to HTML and CSS lesson: Fix link text
• The Because section summarizes the reason for this PR
• The This PR section has a bullet point list describing the changes in this PR
• If this PR addresses an open issue, it is linked in the Issue section
• If any lesson files are included in this PR, they have been previewed with the Markdown preview tool to ensure it is formatted correctly
• If any lesson files are included in this PR, they follow the Layout Style Guide

[Monatric]

It seems that there are a lot of linting errors. May I fix these stuff too?

If so, how would I run linters locally instead of having to push everytime and get GitHub to run the checks?

[mao-sz]

It seems that there are a lot of linting errors. May I fix these stuff too?

If so, how would I run linters locally instead of having to push everytime and get GitHub to run the checks?

Not a maint so not saying you need to fix the lint errors now, but to do linting stuff locally, instructions are in this repo's CONTRIBUTING.md

[Monatric]

Not a maint so not saying you need to fix the lint errors now, but to do linting stuff locally, instructions are in this repo's CONTRIBUTING.md

Sorry, are you referencing to this link? I really can't find the instructions. https://github.com/TheOdinProject/.github/blob/main/CONTRIBUTING.md

[mao-sz]

Sorry, are you referencing to this link? I really can't find the instructions. https://github.com/TheOdinProject/.github/blob/main/CONTRIBUTING.md

No, that's the general contributing guide in the .github repo. I mean this repo's CONTRIBUTING.md.

[Monatric]

Ah I see, thank you. That's my first time seeing that 🤔.

[JoshDevHub]

Thank you for making this PR @Monatric

I have a couple recommended changes to the knowledge check links, and while we're here in this file, we should go ahead and fix the Markdown lint errors. Let me know if you have any questions about any of this.

[JoshDevHub]

Suggested change

	- [What is page navigation defined by Turbo Drive?](https://www.theodinproject.com/lessons/ruby-on-rails-turbo-drive#page-navigation)
	- [What is page navigation defined by Turbo Drive?](#page-navigation)

Section headings automatically have an id inserted for them, which means you can do internal page navigation through just the id.

This isn't just a keystroke saver either. If you were running this site in dev and serving on localhost:3000, you'd want the links to go to localhost:3000/lessons/ruby-on-rails-turbo-drive#page-navigation and not the actual production site. Just expressing that if you can, you want to avoid hardcoding the full production URL to a page (or section of a page).

[Monatric]

Got it! But what's the next thing to do from here? Do I make changes locally or click "Commit suggestion" and "Resolve Conversation"?

I will work on it now but for now I will make the changes locally since I think the results would be the same anyway (i hope)

[JoshDevHub]

Suggested change

	- [How do you disable Turbo Drive?](https://www.theodinproject.com/lessons/ruby-on-rails-turbo-drive#disable-turbo-drive)
	- [How do you disable Turbo Drive?](#disable-turbo-drive)

[Monatric]

Thank you for making this PR @Monatric

I have a couple recommended changes to the knowledge check links, and while we're here in this file, we should go ahead and fix the Markdown lint errors. Let me know if you have any questions about any of this.

I think I resolved all lint errors now, though I have this slightly annoying issue once I installed the markdownlint VSCode extension, where if I run the npm run lint:lesson -- "./path/to/lesson", my terminal tab goes to Output automatically. That's not the only time it happened, but I am still unsure how to replicate this behavior. I'm not sure what the errors tell me too.

[JoshDevHub]

Thank you for making these changes.

I'm not sure about the vscode extension because I don't use it, and I don't know that any maintainer effort has gone into making sure our setup works properly with it. Sorry for the unsatisfying answer on that.