The Awareness Team met on 5th of February 2026, to review several website-related topics, focusing on content responsibility, outdated information, and the future direction of key pages.

Posting Responsibilities and Content Guidelines

The team discussed clarity around responsibility—specifically, who is authorized to publish content and what type of content can be posted on different parts of the website.

To avoid ambiguity and ensure consistency, we agreed on the following actions:

• Add clear posting guidelines (“rules”) to the Blog and Events pages, similar to the structure already in place for the Forums.
• Include a more general clarification in the Terms of Use outlining responsibilities and expectations for published content.

These changes are intended to improve transparency, reduce confusion, and support consistent communication across the platform.

Outdated Content and Page Maintenance

We reviewed several pages that contain outdated or no longer relevant information.

Actions agreed:

• The MVP page will be taken offline, as there are currently no plans to hold an MVP election in the near future.
• The History page will be updated. This will require collecting and verifying historical information to ensure accuracy and completeness before publication.

Maintaining up-to-date information is an ongoing responsibility, and this review highlighted the importance of regularly revisiting older sections of the website.

Rethinking the “Future” Page

The team also discussed the direction and purpose of the Future page. At present, it focuses primarily on the MVC pipeline, which does not fully reflect broader forward-looking initiatives.

We agreed to:

• Refocus the Future page to cover the general direction and long-term vision of the project.
• Create separate, dedicated pages for specific initiatives such as the MVC pipeline and the Editor.
• Explore making the Future page more of a forward-looking landing page that provides a high-level overview and links to detailed topic pages.

An additional idea discussed was the creation of a dedicated Sponsor page. Potential elements of such a page could include:

• Recognition of previous sponsors.
• Clear calls for sponsorship for specific projects.
• Transparency around both monetary contributions and development contributions (e.g., contributed hours).
• Exploring platforms such as Open Collective as a possible framework for managing and presenting sponsorship.

Looking Ahead

This meeting continued the team’s focus on improving structure, clarity, and long-term sustainability across the website.