> Thinking about isolated UI components and features, I'm wondering if "youtube" for a component name would be too general and specific at the same time. We could have many components that involve youtube. Not only that, but maybe we start off using youtube, but end up using vimeo or some other streaming service. What do you think about something like "video_quiz" or something like that. It's specific enough that it tells what it does. It's also generic enough that if we want to change providers, we just change the internals. This also makes it more obvious when building out the CSS and HTML partials that go along with the component.

Yeah, I like this suggestion.  video_quiz seems good.