Feat: Add links to "Open a PR" on resources pages (plugins.mdx & community-content.mdx)

[trueberryless]

Description

• add 2 new sections to the CONTRUBUTING.md file:
  • Plugins and Integrations
  • Community Content
    • Video Content (new example MUST be reviewed...)
• link to these sections from the Starlight website
  • plugins.mdx "Open a PR" links to Plugins and Integrations (to original repo and main branch logically...)
  • community-content.mdx "Open a PR" links to Community Content (to original repo and main branch logically...)

I'm not sure if the maintainers want these changes to exist, because it kinda feels intended that the "Call to action" sections have no links on both sites but on the showcase.mdx site it does.
Probably the reason is, that we want people to add their Showcases on their own, but Plugins and other Content is maybe to complex for the people, so they should just provide a link and we change the files on our own. But I don't know and therefore I through this PR in here...

[changeset-bot]

⚠️ No Changeset found

Latest commit: c144a0e

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[netlify]

✅ Deploy Preview for astro-starlight ready!

Name	Link
🔨 Latest commit	4d57395
🔍 Latest deploy log	https://app.netlify.com/sites/astro-starlight/deploys/67eeb6f77ee65400087b8de9
😎 Deploy Preview	https://deploy-preview-2580--astro-starlight.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (no change from production) Accessibility: 100 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify site 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

Locale	File	Note
en	resources/community-content.mdx	Source changed, localizations will be marked as outdated.
en	resources/plugins.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.

[trueberryless]

Also I'll move the misplaced import statement to another PR cause it doesn't have to do anything with this one...

[trueberryless]

Looking back at what I did here two years ago, I think such a detailed documentation of all resources pages is not actually that necessary. The Sites and Themes section already cover the most difficult additions I would say, and I guess we noticed that not many people encounter problems with adding new plugins or other community content.

Besides: Why did I include a Rick Roll as an example? Seems like a had a funny day back then 😅

I'm gonna close this for now, but keep the branch, if we ever decide that we need more detailed documentation for these sections, we can take this as a reference. 👍