Support publishing content for groups

On the previous CNCF community platform (Bevy), Merge Forward actively used content publishing to share key information with the community.

This included:
- Governance and roles
- Contribution opportunities
- Community guidelines and best practices
- Communication and marketing resources

Examples of previously published content:
- Merge Forward Messaging Guide
- Merge Forward Community Partnership
- Non-Code Opportunity: Digital Marketing Core Contributor
- Merge Forward Marketing Kit
- Collaboration Best Practices
- Merge Forward Roles & Responsibilities
- Merge Forward Community Manager
- Contributor Wanted: Mentorship Program
- KubeCon Onsite Activities Coordinator
- Contributors Wanted: Active Members
- KubeCon Amsterdam CfP Coordinator

References available from the previous platform:
https://community.cncf.io/v0/forum/merge-forward-working-group-1864/

**Current Situation on Open Community Groups**
There is currently no way to publish and organize this type of structured, persistent content within a group.

As a result:
- Important community resources cannot be shared in a centralized place
- Knowledge is fragmented across external tools (Google Docs, Slack, etc.)
- New contributors lack a single entry point to understand the initiative

**Why this matters**
For initiatives like Merge Forward, content publishing is essential to:
- Communicate governance
→ Roles, responsibilities, and how the group operates
- Enable onboarding at scale
→ Contributors can self-serve information without requiring synchronous support
- Promote contribution opportunities
→ Clear visibility on how to get involved (especially for non-code contributors)
- Ensure transparency and alignment
→ Shared understanding of goals, strategy, and ongoing initiatives
- Reduce dependency on synchronous tools (e.g., Slack)
→ Persistent, structured knowledge is critical for asynchronous collaboration

**Without this capability**
- Community growth slows down
- Contributor experience degrades
- Operational overhead increases for maintainers
- Important knowledge becomes hard to find or maintain

**Feature Request:**
Introduce a way for groups to publish and manage structured static content pages: knowledge base, documentation style.

**Key capabilities**
- Create and organize posts/pages within a group
- Categorize content (e.g., governance, opportunities, resources)
- Provide persistent URLs for sharing
- Allow updates and versioning over time

**Expected Outcome**
- Centralized and structured community knowledge
- Improved onboarding and contributor experience
- Better visibility of opportunities and governance
- Reduced reliance on external tools
- Stronger, more scalable community operations

Happy to share more concrete workflows or examples of how we used this in practice if helpful.