@claude, Let's update the Mattermost Product Documentation to reflect the admin and end user product experience from Mattermost server v11.2 onward captured via engineering PR mattermost/mattermost#33960.
Before proposing any changes:
- First, make an assessment on whether or not a doc update is even necessary for this PR.
- If it is necessary: Identify the existing admin and end user documentation page(s) most closely related to the About menu.
- Analyze the writing style, tone, structure, headings, and formatting patterns used on those pages.
When drafting updates:
- Match the existing voice and writing patterns of the page as closely as possible.
- Follow the same heading hierarchy and formatting conventions already in use.
- Avoid introducing new sections unless absolutely necessary.
Focus the docs update on:
- What has changed from the relevant persona’s perspective
- Where this change is surfaced in the product or UI
- When or why the persona would need to be aware of this change
DO NOT suggest changes to the following docs pages:
- changelogs
- important upgrade notes
- version archive
- removed and deprecated features
- unsupported legacy releases