feat(theme-classic): MDXContent wrapper component

[slorber]

Motivation

See #5468 (comment)

That's a legitimate use case to have a global way to wrap/enhance any MDX content being rendered

Also helps reduce a bit boilerplate in page/blog/docs

Have you read the Contributing Guidelines on pull requests?

yes

Test Plan

preview

[netlify]

✔️ [V2]

🔨 Explore the source changes: fa5f707

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

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

[github-actions]

⚡️ Lighthouse report for the changes in this PR:

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

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

[github-actions]

Size Change: +70 B (0%)

Total Size: 791 kB

Filename	Size	Change
website/build/assets/css/styles.********.css	105 kB	+70 B (0%)

ℹ️ View Unchanged

Filename	Size
website/.docusaurus/globalData.json	49.9 kB
website/build/assets/js/main.********.js	597 kB
website/build/index.html	38.4 kB

_{compressed-size-action}

[slorber]

@Josh-Cena let me know if that also helps for your use-case reported here: #5468 (comment)

[antonk52]

The latest commit fixes location of MDXContent

The one nit I have is that the tree contains two different components named MDXContent which can be confusing for developers working on themes. As overriding MDXContent in a theme/preset only overrides the top one.

react devtools screenshot

[slorber]

The one nit I have is that the tree contains two different components named MDXContent which can be confusing for developers working on themes. As overriding MDXContent in a theme/preset only overrides the top one.

I also noticed that but I believe it's a devtools bug or something, we only render the component once in the tree.

[Josh-Cena]

This component doesn't have access to the front matter, so no. But maybe we can provide the current page's metadata in a wrapping context as well?

[Josh-Cena]

I also noticed that but I believe it's a devtools bug or something

The second MDXContent looks like it's from the underlying MDX loader return

[slorber]

@Josh-Cena see this issue: #6885

This issue + the proposal above should help simplify your setup, and this change looks like a good thing to do anyway, so I'm going to merge for now.