[SK-2630] docs: surface migration steps 3.1/3.2 in TOC + fix anchors (new-docs port) - #251
Merged
Merged
Conversation
BrenKt
added
Web Cloud
[SK-2630] Surface migration steps 3.1/3.2 in the table of contents and fix anchor positioning in migration-control-panel across 7 locales. Original-URL: ovh/docs#9409 Original-author: @BrenKt
BrenKt
force-pushed
the
SK-2630-port-toc-anchors
branch
from
June 24, 2026 14:03
1ac69a6 to
1b867e5
Compare
BrenKt
marked this pull request as ready for review
June 24, 2026 14:29
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Port of legacy PR ovh/docs#9409 to new-docs.
Context
Support feedback (SK-2630) on the MX Plan → Exchange / Email Pro migration guide.
Two issues, same root cause: sub-parts 3.1 and 3.2 were level-4 headings (
####).###, so 3.1/3.2 never appeared and couldn't be anchored to send a customer the "3.2 Automatic migration" section (they landed on Step 3 and could miss the Roundcube alert callout).<a name>anchors sat inline at the end of the heading line, so internal links (#roundcube-mxplan) landed one line below the heading.Changes
####to###→ visible in the TOC and anchorable.<a name>anchors onto their own line, before the heading → links land on the heading.#####→####for hierarchy.Anchor names unchanged → existing internal links keep working. Purely structural; no images, no syntax conversion needed.
Scope
7 locales (en, fr, de, es, it, pl, pt) — all real files, no symlinks. New-docs content matched the legacy base exactly → clean port, no divergence.