Update from code changes: queued markdown imports workflow#366
Open
mintlify[bot] wants to merge 1 commit into
Open
Update from code changes: queued markdown imports workflow#366mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
|
|
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
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
Expand the Import page to document the new queued Markdown import workflow and move the Export starting-point reference to the new Data settings page.
Changes
features/import.mdxto cover the Settings → Data entry point, supported uploads (single.md/.mdxfile or.ziparchive, with unsupported entries skipped), upload limits, the async job lifecycle (queued→discovering→processing→importing→completed/failed), the import history list, and the fact that URL-based imports are unsupported.features/export.mdxto point readers at Settings → Data (Export moved alongside Import in the new Data settings page).Context
Follows the source change that added queued Markdown imports and consolidated import/export under a new Settings → Data page (#365).