markdown plugin changes

[gllrmzndm]

Description (required)

Added an example of how the plugin works.

• Confusing examples @ https://docs.astro.build/en/guides/markdown-content/#markdown-plugins
• Sarah asked me to do a PR.

English

Related issues & labels (optional)

• Closes #
• Suggested label:

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	Jul 4, 2024 11:19am

[astrobot-houston]

Hello! Thank you for opening your first PR to Astro’s Docs! 🎉

Here’s what will happen next:

1. Our GitHub bots will run to check your changes.
   If they spot any broken links you will see some error messages on this PR.
   Don’t hesitate to ask any questions if you’re not sure what these mean!

2. In a few minutes, you’ll be able to see a preview of your changes on Vercel 🥳

3. One or more of our maintainers will take a look and may ask you to make changes.
   We try to be responsive, but don’t worry if this takes a few days.

[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

Locale	File	Note
en	guides/markdown-content.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.

[sarah11918]

Thank you for contributing this addition to docs, @gllrmzndm ! All I was hoping for was to show a config setting in the example in place, so that if readers did try to copy it, they'd get something that worked out of the box.

I appreciate the full example, but I think we can achieve the same thing just by not showing a plugin that requires configuration without any config. I also think this makes it obvious that if they don't like the default behaviour this produces, they can go look up remarkToc in its own docs and adjust settings.

I'm happy to have a more complete example here, and also happy to welcome you to Team Docs! 🥳