chore(plugin-docs): expose all lib files through exports

[JPeer264]

Pre-flight checklist

• I have read the Contributing Guidelines on pull requests.
• If this is a code change: I have written unit tests and/or added dogfooding pages to fully verify the new behavior.
• If this is a new API or substantial change: the PR has an accompanying issue (closes Making getSlug available from outside of the packages #7961) and the maintainers have approved on my working plan.

Related issues/PRs

I hope that is OK that I deleted half of the template, as it would mostly duplicate #7961.

---

@Josh-Cena This would be out of scope of this PR, but I noticed that there are exports in theme-common and theme-search-algolia as well, to make it consistent should we add this line there as well?

[Josh-Cena]

but I noticed that there are exports in theme-common and theme-search-algolia as well, to make it consistent should we add this line there as well?

Everything in theme-common is already exported—same as theme-search-algolia.

[netlify]

✅ [V2]

Built without sensitive environment variables

Name	Link
🔨 Latest commit	2468136
🔍 Latest deploy log	https://app.netlify.com/sites/docusaurus-2/deploys/62fca8898eda61000ab00342
😎 Deploy Preview	https://deploy-preview-7962--docusaurus-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 site settings.

[github-actions]

⚡️ Lighthouse report for the deploy preview of this PR

URL	Performance	Accessibility	Best Practices	SEO	PWA	Report
/	🟠 54	🟢 100	🟢 100	🟢 100	🟢 90	Report
/docs/installation	🟠 85	🟢 99	🟢 100	🟢 100	🟢 90	Report

[Josh-Cena]

Thanks!

[JPeer264]

@Josh-Cena general question. Is there some general release plan or roadmap when new releases are coming out? Or is this just based on specific new features?

[slorber]

We wrote about our release process here:

• https://docusaurus.io/community/release-process
• https://docusaurus.io/blog/2022/08/01/announcing-docusaurus-2.0

If you have any question after reading that, please submit and we'll improve our release process doc

[JPeer264]

@slorber thanks for these links they helped a lot. Also recently [email protected] has been deployed, but it seems that these changes were not part of the retro compatible commits. I was just wondering if there is a reason if this is not backwards compatible or not. Would it be possible by any chance to add this to some release? For now we use the nightly builds, which work fine, but still for me it feels a bit unsafe to use them in the long(er) run. Sorry for bringing this little thing up again.

[slorber]

@JPeer264 added the tag to backport for next stable release ;)