docs: mention docusaurus.community site in resources

website/community/2-community-docs.mdx

@@ -0,0 +1,17 @@
+---
+title: Community Docs
+hide_title: true
+sidebar_label: Community Documentation
+---
+
+## Community Documentation
+
+(extends the [Official Docs](/docs))
+
+The **[Docusaurus.community](https://docusaurus.community)** site can be used for extending the official documentation with more complex examples and full articles on best practices that provide solutions to problems the community often faces.
+
+(It is also a full React application just like our main site. So customization and experimentation examples are perfectly suited to be hosted there.)
+
+:::info We might allow direct links to be added in our official documentation that point to the community documentation, on a case by case basis, and as the community requests that such links to articles are useful.
+
+We are also contemplating further integration into the official documentation at some point in the future. :::

website/community/4-canary.mdx → website/community/5-canary.mdx

@@ -16,7 +16,7 @@ import {
 
 Docusaurus has a canary releases system.
 
-It permits you to **test new unreleased features** as soon as the pull requests are merged on the [next version](./5-release-process.mdx#next-version) of Docusaurus.
+It permits you to **test new unreleased features** as soon as the pull requests are merged on the [next version](./6-release-process.mdx#next-version) of Docusaurus.
 
 It is a good way to **give feedback to maintainers**, ensuring the newly implemented feature works as intended.
 

website/community/5-release-process.mdx → website/community/6-release-process.mdx

@@ -113,7 +113,7 @@ There are 3 ways to use the next version:
 
 - with an `alpha`, `beta` or `rc` pre-release
 - with the `@next` npm dist tag for the latest pre-release
-- with a [canary release](./4-canary.mdx) for the very latest features
+- with a [canary release](./5-canary.mdx) for the very latest features
 
 :::tip