[SK-2630] fix(migration_control_panel): surface steps 3.1/3.2 in TOC and fix an…#9409
Closed
BrenKt wants to merge 1 commit into
Closed
[SK-2630] fix(migration_control_panel): surface steps 3.1/3.2 in TOC and fix an…#9409BrenKt wants to merge 1 commit into
BrenKt wants to merge 1 commit into
Conversation
…chors Steps 3.1 (manual migration) and 3.2 (automatic Roundcube migration) were level-4 headings, so they never appeared in the table of contents and could not be linked to when sending the section to a customer. The in-guide anchors were also placed inline at the end of the heading line, making cross-links land one line below the heading. - Promote 3.1/3.2 from #### to ### so they show in the TOC. - Move <a name> anchors onto their own line above the heading so links land on the heading. - Demote the two "Migration from..." sub-headings from ##### to #### to keep the hierarchy consistent. Applied to all EU locales plus en-ca/fr-ca (US locales have a flat step 3).
BrenKt
added
FIX
BrenKt
changed the title
BrenKt
changed the title
BrenKt
added a commit
to ovh/ovhcloud-docs
that referenced
this pull request
Jun 24, 2026
[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
added a commit
to ovh/ovhcloud-docs
that referenced
this pull request
Jun 24, 2026
[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
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.
Context
Support feedback (SK-2630) on the MX Plan → Exchange / Email Pro migration guide (KB0053486).
Two issues, same root cause: sub-parts 3.1 and 3.2 were level-4 headings (
####).###, so 3.1 and 3.2 never showed up. The "3.2 Automatic migration…" section couldn't be anchored to send directly to a customer: 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###→ they now appear in the TOC and become anchorable.<a name>anchors onto their own line, just before the heading (already the majority convention in the repo) → links now land on the heading.#####to####to keep the hierarchy consistent.Anchor names are unchanged, so existing internal links keep working.
Scope
all-mxplan/roundcube-mxplan)LegacyMxplan/NewVersionMxplan), fr-ca (3.1 only)