Fill gaps from assistant conversations: offline export Node.js requirement - #7410
Open
mintlify[bot] wants to merge 2 commits into
Open
mintlify[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.
|
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
Add a help-center article that explains why
mint exportarchives require a Node.js runtime and clarifies whether the export can be served on a plain static host.Changes
help-center/offline-export-requires-node.mdxcovering whyserve.jsis used, why plain static hosting is not supported, and what to do when Node.js is unavailable. Links back to/deploy/exportas the canonical page.docs.json.Context
An assistant conversation about offline exports received negative feedback because the existing Offline export page does not explain why Node.js is required or address the follow-up "shouldn't the export support static site hosting?". The help-center article fills that gap without duplicating setup content.
Note
Low Risk
Documentation and navigation-only changes with no product or runtime impact.
Overview
Adds a new help-center article
offline-export-requires-node(English plus es, fr, and zh translations) that answers whymint exportarchives ship withserve.js, why plain static hosting (S3, GitHub Pages,file://) is not supported, and what to do when recipients cannot install Node.js—including links back to Offline export and alternatives like Mintlify hosting, self-host, or feature requests.Registers the page in the Help center nav in
docs.jsonand the locale nav files (es.json,fr.json,zh.json).Reviewed by Cursor Bugbot for commit 73001bd. Bugbot is set up for automated code reviews on this repo. Configure here.