Document passing components to MDX Content

[matthewp]

Description (required)

Documents passing components to MDX <Content /> component.

Related issues & labels (optional)

For withastro/astro#14591

[netlify]

✅ Deploy Preview for astro-docs-2 ready!

Name	Link
🔨 Latest commit	fbca07b
🔍 Latest deploy log	https://app.netlify.com/projects/astro-docs-2/deploys/68fa50848d77c10008a7a042
😎 Deploy Preview	https://deploy-preview-12597--astro-docs-2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[astrobot-houston]

Lunaria Status Overview

🌕 This pull request will trigger status changes.

Learn more

By default, every PR changing files present in the Lunaria configuration's files property will be considered and trigger status changes accordingly.

You can change this by adding one of the keywords present in the ignoreKeywords property in your Lunaria configuration file in the PR's title (ignoring all files) or by including a tracker directive in the merged commit's description.

Tracked Files

File	Note
en/guides/content-collections.mdx	Source changed, localizations will be marked as outdated.
en/guides/integrations-guide/mdx.mdx	Source changed, localizations will be marked as outdated.
en/reference/directives-reference.mdx	Source changed, localizations will be marked as outdated.

Warnings reference

Icon	Description
🔄️	The source for this localization has been updated since the creation of this pull request, make sure all changes in the source have been applied.

[delucis]

We do already document this here: https://docs.astro.build/en/guides/integrations-guide/mdx/#custom-components-with-imported-mdx

Maybe we can link there? Or tweak it if we need to clarify anything?

[sarah11918]

Thank you @matthewp , this is a helpful example! See my comments below, including a question making sure it's clear how including the default exports work!

[sarah11918]

Following up, now Chris's comment is appearing for me. I'm going to suggest we keep this content in the MDX page only and perhaps link to it from the content collections page.

Maybe it's the MDX page that needs beefing up so it's obvious that this works in content collections, too!

[sarah11918]

OK! So I updated both the text on the content collections and the MDX pages so that the main content is all on the MDX page and content collections links to it.

I made this intentionally as big as it could be, showing both a plain "import from MDX" and a content collections example. Would love help fixing up the MDX stuff to make sure it's helpful enough for both scenarios, but not too much! @delucis

[sarah11918]

(Noting two link issues we can address once we've decided on a section heading)

[ArmandPhilippot]

Looks great to me! I left a comment for the heading and another nit because I think "blog posts" might confuse some people?

[sarah11918]

OK, I addressed Yan's grammar nits, and @ArmandPhilippot , what do you think of this new order/flow? I honestly think this whole thing feels much better in this order!

[sarah11918]

Updating branch to hopefully get a deploy preview

[sarah11918]

I am happy with this! (Anyone else still welcome to find things wrong.)

[yanthomasdev]

Happy too!