refactor(content-blog): clean up type definitions; in-code documentation

[Josh-Cena]

Motivation

This is part of a bigger effort to make our codebase more approachable, both for internal types and the types exposed to end-users. For example, since we have JSDoc in the config file, the user can now use intellisense to see the documentation for any option:

It also means we can achieve #6649 without actually writing much Markdown. We may investigate migrating our API documentation to Typedoc later, so we don't maintain two sets of documentation (JSDoc and Markdown)

Have you read the Contributing Guidelines on pull requests?

Yes

[netlify]

✔️ [V2]

🔨 Explore the source changes: 5c52eba

🔍 Inspect the deploy log: https://app.netlify.com/sites/docusaurus-2/deploys/6231c7e840d390000804bc6d

😎 Browse the preview: https://deploy-preview-6922--docusaurus-2.netlify.app

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

Category	Score
🟠 Performance	67
🟢 Accessibility	100
🟢 Best practices	92
🟢 SEO	100
🟢 PWA	90

Lighthouse ran on https://deploy-preview-6922--docusaurus-2.netlify.app/

[github-actions]

Size Change: 0 B

Total Size: 792 kB

ℹ️ View Unchanged

Filename	Size
website/.docusaurus/globalData.json	49.9 kB
website/build/assets/css/styles.********.css	105 kB
website/build/assets/js/main.********.js	599 kB
website/build/index.html	38.7 kB

_{compressed-size-action}

[slorber]

Yes that's nice 👍

That would be interested also if someday we'd be able to generate some API reference docs pages from those code types so that everything stays in sync

[Josh-Cena]

That would be interested also if someday we'd be able to generate some API reference docs pages from those code types so that everything stays in sync

Introducing Typedoc 😄 There's also a Docusaurus integration plugin which I can check out later