Docs: Video coverage extended

[jonniebigodes]

What I did

Introduced some additional videos to complement the documentation further. Featured in this pull request are the following pages:

• Writing stories / AutoDocs (custom template section)
• Writing Docs / Doc Blocks
• Sharing / Embed
• Sharing / Publish
• API / Doc Blocks
  • ArgTypes
  • Canvas
  • Controls
  • Description
  • Primary
  • Source
  • Stories
  • Story
  • Subtitle
  • Title

How to test

1. Check out the test_timestamps branch on the frontpage repository.
2. Follow the steps in the contributing instructions for this branch, chore_docs_adds_videos.
3. Open the relevant documentation, and the videos should be available, including the timestamped ones.

@chantastic and @kylegach when you have a moment, can you take a look at this and let me know of any feedback? Thanks in advance.

Checklist

• Make sure your changes are tested (stories and/or unit, integration, or end-to-end tests)
• Make sure to add/update documentation regarding your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts
• Make sure this PR contains one of the labels below.

["cleanup", "BREAKING CHANGE", "feature request", "bug", "build", "documentation", "maintenance", "dependencies", "other"]

🦋 Canary release

This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

core team members can create a canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>

[kylegach]

When we include these at the page level, we place them immediately under the page title. The thinking there being that videos offer an alternative learning path, and we want to present that as early as possible.

I think we should apply the same pattern here, and place the YouTubeCallout immediately after the section heading.

[jonniebigodes]

I know, and I thought of it as well, but I'm aware that users might want to get into the video upfront, but when taking a second look at it, I placed it there to give users the code first, and after it the video and the text so that they follow along what's being presented. More than ok with moving it up and seeing how it fares. If need be we can shift it around later on.

Sounds good?

[kylegach]

This is nice! I left a suggestion, but I'll go ahead and approve.

[chantastic]

Thanks for taking this on João!
Cool to see that you were able to add the specific time stamps for the doc blocks!

[jonniebigodes]

Thank you both for the speedy review. Appreciate it 🙏 ! I've just addressed the suggestion, and let's see how it fares. Merging this in a bit after the frontpage one is merged in.