Translate custom heading ID h5/h6 update to es, fr, zh#4881
Merged
Conversation
Generated-By: mintlify-agent
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
ethanpalm
approved these changes
Mar 25, 2026
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.
Summary
Translates changes from #4875 (custom heading IDs now include h5 and h6 support) into all supported languages:
##### Deep detail {#detail}example to the code block ines/create/text.mdx,fr/create/text.mdx, andzh/create/text.mdx<Note>block stating that custom heading IDs only support levels 1–4 from all three translated filesNote
Low Risk
Low risk documentation-only updates that adjust translated MDX content to reflect expanded custom heading ID support (now including level 5).
Overview
Updates the Spanish, French, and Chinese
create/text.mdxdocs to reflect that custom heading IDs now work beyond H4. This adds an##### ... {#detail}example and removes the note claiming custom IDs are limited to heading levels 1–4.Written by Cursor Bugbot for commit a3c16b0. This will update automatically on new commits. Configure here.