mirror of
https://github.com/hanzoai/team.git
synced 2026-10-30 14:49:35 +00:00
b5f007d35e
* docs: resolve cross-file anchor mismatches from RST-to-MDX migration
The Sphinx-to-Docusaurus migration converted `:ref:`/`{ref}` links using
naive text-slugification, so anchors that pointed to headings in a
different file (e.g. release-summary tables linking into their
respective changelog pages) were emitted as same-page fragments and
silently resolved to nothing.
Built a label registry from the original Sphinx `.. _label:` / `(label)=`
targets to recover the true source file for each cross-reference, then
rewrote the affected links to point at the correct file + heading
anchor. Fixes 282 broken cross-file anchors, primarily in the mobile/
desktop/server release-summary pages, plus assorted same-page anchor
mismatches caught by re-auditing after the prior admonition/anchor fix.
* docs: manually resolve remaining anchor mismatches after cross-file audit
Hand-verified fixes for anchors that fuzzy-matching alone couldn't
safely resolve (confirmed against actual heading text/context, and in a
few cases against the original RST source, before applying):
- Typos and dropped words carried over from the original Sphinx docs
(e.g. "bot-acocunts", "auto-follow-all-new-channel-threads" ->
"follow-all-new-channel-threads").
- Sphinx auto-generated duplicate-heading IDs (#id1/#id3/#id4) resolved
to their real target headings.
- Numbered-step TOC links in enterprise-roll-out-checklist.mdx that
dropped the leading "N. " used in the actual heading slugs.
- Push-notification docs pointing at the wrong file entirely
(environment-configuration-settings instead of
push-notification-server-configuration-settings).
- SAML "saml-enterprise" label resolved to its true cross-file target
(authentication-configuration-settings#saml-2-0), recovered from the
original RST label definition that the automated registry missed
because it sat after an RST transition marker.
- sso-saml-technical references converted from broken same-page/
malformed-path anchors to correct page links.
* docs: fix SAML 2.0 anchor slug (saml-2-0 -> saml-20)
github-slugger strips periods rather than hyphenating them, so "SAML
2.0" slugifies to saml-20, not saml-2-0 as previously fixed.
* docs: fix broken path links found during docs/main migration cleanup
* docs: convert div.tab blocks to Docusaurus Tabs/TabItem components
* docs: restore missing Kubernetes deployment architecture diagrams
The RST-to-MDX migration never copied over the AWS/Azure/Oracle
architecture diagrams referenced by the deployment-architecture-at-scale
page, leaving broken images in each Tabs/TabItem.
* docs: fix 7 anchor mismatches from the fragment/heading audit
Covers three root causes from the anchor mismatch breakdown:
- Fragment repeated the target page's own title instead of a real
heading, so the link is simplified to point at the bare page.
- Heading exists verbatim but lives on a sibling settings page
(experimental-configuration-settings, push-notification-server-
configuration-settings) rather than environment-configuration-settings.
- A page path was mistakenly pasted into a same-page #fragment instead
of being used as a real cross-page link.
* docs: fix 8 anchor slugs that were close but didn't match the real heading
Repoints links whose fragment was a plausible guess (typo, reworded
heading, or wrong section) at the actual auto-generated slug of the
target heading, confirmed by inspecting each target page directly.
* docs: merge split Tabs blocks so tabs render horizontally
The div.tab conversion script split some sibling tab groups into
separate single-item Tabs blocks whenever a stray blockquote marker
sat between them, causing them to render stacked instead of as one
horizontal tab bar. Merges the MySQL/PostgreSQL and Team/Enterprise
Edition tab groups back into single Tabs blocks.
* docs: remove Azure tab and restore Kubernetes deploy content
The Mattermost Operator, Azure, and Oracle platform tabs on the
Kubernetes deployment guide were split across two separate Tabs
blocks (rendering stacked instead of as one tab bar) and all three
tab bodies were empty because the migration never flattened the
original RST include directives. Removes the unsupported Azure tab
and restores the Mattermost Operator and Oracle content from the
pre-migration RST sources as a single merged Tabs block.
* addresscoderabbitreview
* docs: unify Linux/Kubernetes/Containers deploy pages and fix FIPS/STIG placement
Kubernetes and Containers duplicated full install content across a top-level
page (Tabs) and orphaned sidebar subpages that nothing linked to. Reworked
both to follow the Linux page's pattern: shared content on the landing page,
platform-specific instructions live once in their own subpage.
Also removed configure-fips-at-install-time.mdx, which claimed FIPS is
available for native Linux installs — FIPS/STIG in Mattermost is a container
image property (Chainguard-based build), not available outside Docker/
Kubernetes. Consolidated all FIPS/STIG references onto
containers/fips-stig.mdx and pointed the Mattermost Operator subpage (not
Oracle OKE, which doesn't expose image selection) at it.
* docs: fix review findings — image alt text, Important callout markup, typo
- Replace generic alt="image" on scaling diagrams with descriptive text
identifying cloud provider and user scale.
- Convert raw div.important markup in deploy-containers.mdx to the
repo's <Important> component, matching usage elsewhere in the file.
- Fix "Matermost" typo in manage-your-display-options.mdx.
---------
Co-authored-by: Hanzo Dev <[email protected]>
97 lines
6.5 KiB
Plaintext
97 lines
6.5 KiB
Plaintext
---
|
||
title: "Work with boards"
|
||
---
|
||
import Tabs from '@theme/Tabs';
|
||
import TabItem from '@theme/TabItem';
|
||
|
||
<PlanAvailability slug="entry-ent" />
|
||
|
||
Start by selecting the type of board you want to use. A board contains cards, which typically track tasks or topics, and views, which define how to display the cards, or a subset of them. Views can display cards in a board, table, calendar, or gallery layout, optionally filtered and grouped by a property (e.g., priority, status, etc).
|
||
|
||
## Add new boards
|
||
|
||
To add a new board, select the plus icon <img src="/img/ui/plus_F0415.svg" alt="The Plus icon provides access to channel and direct message functionality." className="theme-icon" /> at the top of the sidebar, then select **Create New Board** to open the template picker and select a template or blank board.
|
||
|
||
### Board details
|
||
|
||
To name or rename a board, select the title area to edit it.
|
||
|
||
To display board description, hover above the board’s title and select **Show description** to activate the show/hide toggle. Once the description field is displayed, select **Add a description** right below the board title to add or edit the description.
|
||
|
||
Boards and cards are created with random icons by default. To change or remove icons, select the icon then choose the appropriate action.
|
||
|
||
All changes you make to boards and cards are saved immediately.
|
||
|
||
## Choose a board template
|
||
|
||
Templates provide you with a predefined structure so that you can get started quickly. Each template has a different function, but can be customized to suit your use case. When you create a new board from the template picker, select each template’s name to preview it and make sure it suits your requirements. Alternatively, you can create your own board templates.
|
||
|
||
### Board templates
|
||
|
||
Standard board templates include:
|
||
|
||
- **Content Calendar**: Plan and organize your content creation and publication schedule.
|
||
- **Company Goals & OKRs**: Plan your company goals and objectives more efficiently.
|
||
- **Competitive Analysis**: Track and stay ahead of the competition.
|
||
- **Meeting Agenda**: Use this template for recurring meetings. Queue up items, organize discussions, and plan what to revisit later.
|
||
- **Personal Goals**: Categorize and plan your personal goals.
|
||
- **Personal Tasks**: Organize your life and track your personal tasks.
|
||
- **Project Tasks**: Stay on top of your project tasks, track progress, and set priorities.
|
||
- **Roadmap**: Plan your roadmap and manage your releases more efficiently.
|
||
- **Sprint Planner**: Plan your sprints and releases more efficiently.
|
||
- **Team Retrospective**: Identify what worked well and what can be improved for the future.
|
||
- **User Research Sessions**: Manage and keep track of all your user research sessions.
|
||
- **Welcome to Boards!**: Onboarding template with guided tour points to help you quickly ramp up on Boards.
|
||
|
||
### Create a blank board
|
||
|
||
If none of the available templates suit your requirements, you can create a blank board using the **Create empty board** option from the template picker.
|
||
|
||
### Create a new template
|
||
|
||
To create a new board template select the plus icon <img src="/img/ui/plus_F0415.svg" alt="The Plus icon provides access to channel and direct message functionality." className="theme-icon" /> at the top of the sidebar to open the template picker, select **Create New Board** and then select **+ New template**.
|
||
|
||
To turn an existing board into a template, hover over the board title in the sidebar. Select the options menu <img src="/img/ui/dots-horizontal_F01D8.svg" alt="Use the More icon to access additional message options." className="theme-icon" />, then select **New template from board**.
|
||
|
||
### Share a custom board template
|
||
|
||
<Tabs>
|
||
<TabItem value="from-boards-v7-2-or-later" label="From Boards v7.2 or later">
|
||
|
||
Custom templates support permissions control, and are restricted to only the template creator by default. The template creator is an admin of the template. To make the template accessible to everyone on the team, select **Share** on the template editor, and then set the team role as **Viewer**. All members of the team will now be able to see and select the template from the template picker.
|
||
|
||
The admin of the template can also grant specific team members elevated permissions to the template and/or limit access to selected team members by setting the team role as **None** and adding individual members to the template. Individual team members can be assigned the following roles on a template:
|
||
|
||
- **Admin**: Can modify the template and its permissions, and delete the template.
|
||
- **Editor**: Can modify but not delete the template, nor change permissions.
|
||
- **Viewer**: Can view and select the template.
|
||
|
||
</TabItem>
|
||
<TabItem value="prior-to-boards-v7-2" label="Prior to Boards v7.2">
|
||
|
||
Boards and templates are channel-specific so whichever channel you create your board or template in, is where you’ll find it. If you’d like to re-use a board as a template on another channel workspace, you can export it and then import the archive file in the channel of your choosing.
|
||
|
||
To do this, select the options menu <img src="/img/ui/dots-horizontal_F01D8.svg" alt="Use the More icon to access additional message options." className="theme-icon" /> in the toolbar at the top of the board. Then select **Export** board archive. Download the archive file. Navigate to the channel where you’d like to add the exported board. Select the gear icon <img src="/img/ui/settings-outline_F08BB.svg" alt="Use the Settings icon to customize your Mattermost user experience." className="theme-icon" /> next to your profile picture, then choose **Import archive**. The board you created will be added to this channel.
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|
||
|
||
## Edit board templates
|
||
|
||
Custom templates are fully editable, but standard templates cannot be edited or deleted. To open the template editor for a specific template, go to the template picker then hover over the custom template and select the pencil icon. Any changes made on the template editor will be automatically saved and visible to team members who have access to the template.
|
||
|
||
<Tabs>
|
||
<TabItem value="from-boards-v7-2-or-later" label="From Boards v7.2 or later">
|
||
|
||
Only admins and editors of a custom template can edit the template. If you don't see the pencil icon when hovering over the template, then you don't have the appropriate permissions to edit the template.
|
||
|
||
</TabItem>
|
||
<TabItem value="prior-to-boards-v7-2" label="Prior to Boards v7.2">
|
||
|
||
Any member of the channel workspace can edit a custom template in the channel. To limit access to the template, create or export the template to a private channel.
|
||
|
||
</TabItem>
|
||
</Tabs>
|
||
|