Update from support feedback: editor preview Tailwind and custom mode styling - #7257
Open
mintlify[bot] wants to merge 2 commits into
Open
Update from support feedback: editor preview Tailwind and custom mode styling#7257mintlify[bot] wants to merge 2 commits into
mintlify[bot] wants to merge 2 commits into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
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
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
Documents two undocumented custom page mode behaviors that surfaced in support: the web editor's live preview does not generate CSS for page-specific Tailwind classes (styles only render on deployments, preview deployments, or
mint dev), and custom mode applies no default typography to native HTML elements.Changes
help-center/tailwind-classes-not-applying-in-editor-previewexplaining why Tailwind-styled pages look unstyled in the live preview, how to see accurate rendering, and the no-default-typography behavior of custom mode.guides/custom-layoutsabout the live preview limitation and a paragraph on unstyled native elements in custom mode.docs.json,es.json,fr.json, andzh.json.Support context
Note
Low Risk
Documentation-only changes with no runtime, auth, or deployment logic affected.
Overview
Adds documentation for two custom page behaviors that often show up in support: Tailwind-styled pages looking broken in the web editor live preview, and custom mode pages with no Mintlify default typography on native HTML.
A new Help center article (
tailwind-classes-not-applying-in-editor-preview) explains that live preview skips the build step, so page-specific Tailwind CSS is not generated there (classes may appear asmint-*with no matching rules), and points readers tomint dev, preview deployments, or production to verify styling. It also documents that custom mode is a blank canvas—<h2>,<p>, etc. need explicit Tailwind classes everywhere, not just in the editor.guides/custom-layoutsgains a short paragraph on custom-mode typography, a Note about the live preview limitation with a link to the help article, and the same updates are mirrored in es, fr, and zh. Help center nav indocs.jsonand locale JSON files registers the new page in each language.Reviewed by Cursor Bugbot for commit 5dcdf69. Bugbot is set up for automated code reviews on this repo. Configure here.