feat: Add community projects page

[Krzemien97]

• Add new community projects page
• Add license file
• Add guideline to add community project

[cloudflare-workers-and-pages]

Deploying fictionlab-docs with    Cloudflare Pages

Latest commit:	b56c1fd
Status:	✅  Deploy successful!
Preview URL:	https://8ecdfa39.fictionlab-docs.pages.dev
Branch Preview URL:	https://feat-community-projects.fictionlab-docs.pages.dev

View logs

[Copilot]

Pull request overview

Adds a new Docusaurus “Community Projects” section (implemented as a blog) with custom list/post rendering, plus contributor guidelines and CI checks for required front matter.

Changes:

• Configure a new blog instance at /community-projects and add a navbar entry.
• Add custom React components/hooks to render community project list cards and post pages.
• Add front matter validation scripts + contributor guideline doc + MIT license.

Reviewed changes

Copilot reviewed 18 out of 18 changed files in this pull request and generated 16 comments.

Show a summary per file

File	Description
src/hooks/useCommunityProject/index.tsx	Adds a hook to type-extend blog post metadata with company front matter.
src/components/communityProjects/BlogPostPage/index.tsx	Custom community-project blog post page layout (TOC, paginator, etc.).
src/components/communityProjects/BlogListPage/index.tsx	Custom community-project blog list page layout.
src/components/communityProjects/BlogPostItems/index.tsx	Renders community project posts in a grid of cards.
src/components/communityProjects/BlogPostItems/styles.module.css	Styling for the grid/card wrappers.
src/components/communityProjects/BlogPostItem/index.tsx	Custom blog post item wrapper for community projects.
src/components/communityProjects/BlogPostItem/Header/index.tsx	Adds company logo rendering to the post header.
src/components/communityProjects/BlogPostItem/Header/styles.module.css	Styles for header author/company area.
src/components/communityProjects/BlogPostCard/index.tsx	Implements the compact “project card” UI for list view.
src/components/communityProjects/BlogPostCard/styles.module.css	Styling for the compact card UI.
scripts/docs-frontmatter-check.js	Updates success message wording for docs front matter validation.
scripts/community-projects-frontmatter-check.js	Adds front matter validation for community project MDX files.
package.json	Runs both docs and community-project front matter checks in check:frontmatter.
docusaurus.config.ts	Registers the new blog instance and adds navbar link.
docs/guidelines/addCommunityProject.mdx	Adds contributor guidelines for submitting community projects.
communityProjects/tags.yml	Defines tag metadata for community projects.
communityProjects/autonomous-agriculture-robot.mdx	Adds a sample community project MDX file (currently marked as a test file).
LICENSE	Adds MIT license file.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[jasiex01]

I wouldn't merge this do development with a placeholder unless we can ensure that the placeholder never makes it to production. It could be merged into production only when an actual first community project is added.

Additionally I like the tagging idea, however currently the /community-projects/tags view can only be accessed after going into a community project and clicking the tag assosciated with the project and then clicking view all tags. I'd prefer if the tag list or selecting the community projects by tags was more accessible.

[Krzemien97]

@jasiex01, I implemented the requested changes and also added the list of the tags at the top of the page.

Also, it will not be merged to the production with the placeholder, we want to get this community projects section ready for our client to add first community project.
In this case, should we allow them to work on this branch or create new one (and merge these changes to it)?

[jasiex01]

In my opinion we can let them work on a separate branch and merge to this one or merge it to development and let them work on a separate branch that will be merged to development. The downside of the first approach is that the guide refers to branching from development and the downside of the second approach is that we would be blocked from merging to production up until a community project is added.