Clarify multiple API specification files #2537
Merged
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.
Documentation changes
This PR clarifies the use of multiple API specification files.
Closes https://linear.app/mintlify/issue/DOC-226/editor-how-to-add-multiple-jsonyaml-files
For Reviewers
When reviewing documentation PRs, please consider:
✅ Technical accuracy
✅ Clarity and completeness
✅ User experience
Note
Enhances documentation for configuring API specs and auto-generated pages.
asyncapifiles innavigationand notes each file generates its own channel pagesopenapifiles with CodeGroup examples for single and multiple specifications; adds guidance on hosting/adding specsdocs.json): Fixes expander casing toapi/openapi/asyncapiand adds clear examples foropenapi/asyncapias single file, array of files, or directory objectsWritten by Cursor Bugbot for commit 22c8d43. This will update automatically on new commits. Configure here.