4 Commits

Include renames

Author	SHA1	Message	Date
3 people	9c31300bff	docs: port P13/P14 content drift into monorepo (#37590) ... * docs(P13c): add missing manage-plugins.mdx to Administration Guide Configure source/administration-guide/configure/manage-plugins.rst existed in the Sphinx repo pre-fork but was never carried over during the initial P2 move or the P13c Configure reconciliation pass. Port it verbatim (RST -> MDX) with links/anchors verified against the current docs/main tree (mmctl-command-line-tool, plugins, plugins-configuration-settings, popular-integrations, environment-configuration-settings#maximum-file-size, air-gapped-deployment). #### Release Note ```release-note NONE ``` * docs(P13/P14): port remaining content drift into monorepo Ports outstanding content-only drift identified in docs-experimental phase-P13/P14: V11.9 docs major release content, Azure Blob Storage guide, ID-attribute case-sensitivity notes, ranked attribute types and attribute value masking for ABAC, plugin management guide linkage, and the P14 markdown action buttons reference page with its interactive-messages cross-reference. Excludes all automation/workflow files, which are handled separately. * docs(sidebar): link top-level category headers to their landing page buildCategory() only recognized a literal index.md(x) filename as a category's landing page, but Overview, Deployment Guide, Administration Guide, Security & Compliance, End User Guide, Integrations Guide, Get Help, and Use Case Guide all use a *-index.md(x) filename instead (to avoid collisions when flattening for URL stability). As a result, clicking most top-level sidebar categories only expanded/collapsed the list instead of navigating to their overview page. Recognize the *-index.md(x) convention as a fallback so these categories link correctly, matching the existing Deployment Guide/Overview behavior. * docs(P13/P14): fix blog link typo and restore dropped Open Source Components entry Audit against Sphinx source (docs/source/product-overview/) found two drops from the 7e915c99f8 content-drift port: - mattermost-v11-changelog.mdx: blog link slug had an erroneous "-0" (mattermost-v11-9-0-is-now-available -> mattermost-v11-9-is-now-available), likely copy-pasted from the v11.8.0 entry above it. - mobile-app-changelog.mdx: the 2.42.0 release entry's "Open Source Components" subsection (voximplant/react-native-foreground-service removal) was dropped entirely during the RST->MDX port. #### Release Note ```release-note NONE ``` * docs(fix): remove standalone SQL comment line breaking MDX parse A lone "--" comment line inside a <pre><code> SQL block was parsed by remark as a setext heading underline, splitting the surrounding paragraph and leaving the <code> tag unclosed. CI caught this in the docusaurus build. Merge the comment into the surrounding paragraph. * docs(fix): escape curly braces in JSONB path literal breaking SSG render '{options}' inside a SQL <pre><code> block was parsed by MDX as a JSX expression referencing an undefined "options" identifier, causing "ReferenceError: options is not defined" during static site generation. Escape the braces the same way already done for other JSONB path literals elsewhere in this file. Verified with a full local docusaurus build. * docs(sidebar): reuse the landing-file resolver for nested category sorting/labels The prior fix only applied the index.md(x) / *-index.md(x) fallback to a category's own link resolution. Nested category sort keys and the category label fallback still assumed a literal index.mdx, so a sub-directory using the *-index.md(x) naming convention would sort by its default position (9999) instead of its declared sidebar_position, and its category label would fall back to a humanized directory name instead of the landing page's title. Factor the resolver into a shared findIndexFile() helper and use it in both places. --------- Co-authored-by: Hanzo Dev <[email protected]>	2026-07-21 13:40:08 +03:00
Eva SarafianouandGitHub	eadce354df	Remove internal only pages from develop (#37436)	2026-07-10 14:10:10 +03:00
3 people	611f31f6c2	docs: fix broken images, cross-links, and layout overflow after docs-experimental migration (#37418) ... * docs: restore missing e2e/mobile push-notification images These developer-docs images existed in mattermost-developer-documentation's static assets but were never copied into the monorepo during the docs migration, leaving broken image links in e2e-cheatsheets.md and the mobile push-notification pages. Also fixes e2e-cheatsheets.md's image paths, which used Hugo-style relative paths that don't resolve under Docusaurus. * docs: fix broken outgoing webhooks screenshot path The image reference used an absolute path left over from the old Hugo site (/integrate/faq/images/...), which doesn't resolve under Docusaurus since no matching file exists under site/static. The image already lives co-located in docs/develop/integrate/faq/images/, so point to it with a relative path instead. * docs: delete Azure AKS deployment guide page The page's screenshots never made it into the monorepo during migration and don't exist under any known source (docs, docs-experimental, or mattermost-developer-documentation). Remove the page rather than ship broken images; drop it from the PDF book manifest and repoint its legacy redirect to the general Kubernetes deployment guide accordingly. * docs: fix heading levels on Kubernetes deploy guides deploy-k8s.mdx and deploy-k8s-oke.mdx used H1 (#) for their top-level in-page sections (Installation steps, Common Errors, etc.) instead of H2. Docusaurus' contentTitle extraction grabs the first H1 it finds anywhere in the doc, which stole the page title slot from the actual frontmatter title, so no title rendered at the top of the page. The flat H1/H2 mix also meant TOC entries for install steps rendered as a flat list at the page's TOC root instead of nested under their section, which made the TOC sidebar overflow/misrender on narrower/zoomed viewports. Bump every heading in both files one level (H1->H2->H3->H4) so the page title renders and the TOC nests correctly. * docs: fix TOC/layout horizontal overflow on wide code blocks The Kubernetes prerequisites page's TOC sidebar overflowed off-screen at higher browser zoom levels. Root cause: `.docMainContainer` has `max-width: none !important` (intentional, so OpenAPI's 2-column layout gets full width), but that removes the container's only width ceiling. Combined with the default flexbox `min-width: auto` on both the main container (in its outer flex row with the left sidebar) and the doc content column (in the inner content/TOC row), a sufficiently wide code block's intrinsic min-content size could drag the whole row wider than the viewport instead of scrolling within itself. Add `min-width: 0` at both flex levels so `overflow-x: auto` on code blocks and tables actually contains overflow locally, and make the responsive table-scroll CSS apply unconditionally instead of only under the 996px breakpoint (zoom shrinks effective layout width without re-triggering the media query). Also shorten the illustrative base64 example values in the AWS Aurora Postgres secret example, which were long enough on their own to be a secondary contributor to the same overflow. * docs: restore additional missing images found via full static-resolution scan Docusaurus's build-time image validator doesn't reliably warn on every broken absolute-path reference, so npm run build alone missed these. A direct scan of every image reference in docs/develop and docs/main against the filesystem turned up 38 more genuinely missing images (desktop architecture, VPN/Pritunl setup, docker dev environment, i18n-extract tooling, MVP program, onboarding, schema migration guide, plugin best-practices, and interactive-message screenshots) that were never copied over from mattermost-developer-documentation during migration. Two references (interactive-dialog-date.png and interactive-dialog-datetime.png) remain unresolved because no source image exists anywhere in the legacy repo. * docs: fix broken cross-links after .md to .mdx migration Several Calls admin guide pages and the air-gapped quick-start runbook were renamed from .md to .mdx during migration, but their internal cross-links still pointed at the old .md filenames (and, for setup-tls, the old flattened path), so Docusaurus couldn't resolve them. Found via a full scan of every relative markdown link under docs/main and docs/develop against the filesystem, since the build's own "couldn't be resolved" warnings don't reliably surface every broken link. * docs: remove broken date/datetime element screenshots These screenshots were never captured before migration (broken on the currently live docs.mattermost.com too), and no source image exists anywhere in the legacy repos to restore. Remove the broken references rather than leave a dead image link. * docs: move newly-restored desktop architecture images to static/ These 4 images were restored co-located next to their content files, matching an existing (if inconsistent) convention elsewhere in docs/develop. Since these are new additions rather than pre-existing working references, move them to docs/site/static/ instead of perpetuating the co-located pattern. Repo-wide normalization of the other ~70 existing co-located image references is left for a separate follow-up PR. * docs: remove deleted AKS page from sidebar generator's manual grouping master (#37402) fixed the sidebar generator's SRC path but this branch's deletion of deploy-k8s-aks.mdx still left a dangling reference in the Deployment Guide's manual Kubernetes grouping, which fails Docusaurus's sidebar-doc-id validation at build time. --------- Co-authored-by: Hanzo Dev <[email protected]>	2026-07-09 18:13:08 +03:00
3 people	bc56925599	feat(docs): move docs-experimental content into monorepo docs/ (#37330) ... * feat(docs): move docs-experimental content into monorepo docs/ * Remove plan related files and comments * Cleanup comments, remove generated files --------- Co-authored-by: Hanzo Dev <[email protected]>	2026-07-02 18:42:57 +03:00