From 06ddf5032375e40b0bb606ec8d204109f62265cf Mon Sep 17 00:00:00 2001 From: Eva Sarafianou Date: Thu, 23 Jul 2026 10:27:27 +0300 Subject: [PATCH] docs: mark scale partial pages as unlisted with proper titles (#37628) These MDX files are content partials imported into the scale-to-*-users pages, mirroring the :orphan:/:nosearch: Sphinx pages they were migrated from. Without frontmatter, Docusaurus rendered them as full standalone pages with an ugly slug-derived title, breadcrumbs, and pagination. unlisted: true keeps their routes alive (needed by the PDF book builder and legacy redirects) while hiding them from the sidebar, breadcrumbs, pagination, and search indexing. Co-authored-by: Cursor --- .../administration-guide/scale/additional-ha-considerations.mdx | 2 ++ .../scale/estimated-storage-per-user-per-month.mdx | 2 ++ docs/main/administration-guide/scale/lifetime-storage.mdx | 2 ++ 3 files changed, 6 insertions(+) diff --git a/docs/main/administration-guide/scale/additional-ha-considerations.mdx b/docs/main/administration-guide/scale/additional-ha-considerations.mdx index 241d71aa2273..f543a68c4910 100644 --- a/docs/main/administration-guide/scale/additional-ha-considerations.mdx +++ b/docs/main/administration-guide/scale/additional-ha-considerations.mdx @@ -1,4 +1,6 @@ --- +title: Additional HA considerations +unlisted: true --- [Elasticsearch](https://www.elastic.co) provides enterprise-scale deployments with optimized search performance and prevents performance degradation and timeouts. Elasticsearch allows you to search large volumes of data quickly, in near real-time, by creating and managing an index of post data. Mattermost’s implementation uses [Elasticsearch](https://www.elastic.co) as a distributed, RESTful search engine supporting highly efficient database searches in a [cluster environment](/administration-guide/scale/high-availability-cluster-based-deployment). Visit the [Mattermost Elasticsearch product documentation](/administration-guide/scale/elasticsearch-setup) for deployment and configuration details. diff --git a/docs/main/administration-guide/scale/estimated-storage-per-user-per-month.mdx b/docs/main/administration-guide/scale/estimated-storage-per-user-per-month.mdx index 4cb27309572f..62b982a27615 100644 --- a/docs/main/administration-guide/scale/estimated-storage-per-user-per-month.mdx +++ b/docs/main/administration-guide/scale/estimated-storage-per-user-per-month.mdx @@ -1,4 +1,6 @@ --- +title: Estimated storage per user, per month +unlisted: true --- File usage per user varies significantly across industries. The below benchmarks are recommended: diff --git a/docs/main/administration-guide/scale/lifetime-storage.mdx b/docs/main/administration-guide/scale/lifetime-storage.mdx index f889f3725704..30cd2ed1a5f6 100644 --- a/docs/main/administration-guide/scale/lifetime-storage.mdx +++ b/docs/main/administration-guide/scale/lifetime-storage.mdx @@ -1,4 +1,6 @@ --- +title: Lifetime storage +unlisted: true --- To forecast your own storage usage, begin with a Mattermost server approximately 600 MB to 800 MB in size including operating system and database, then add the multiplied product of: