Fill gaps from assistant conversations: static file 404 troubleshooting - #7051
Merged
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
ethanpalm
approved these changes
Aug 21, 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
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 walks through why a static file committed to a docs repo can return 404 at its expected URL.
Changes
help-center/static-file-not-served.mdxcovering URL/path mismatch, unsupported file types, size limit, authentication,.mintignoreand auto-ignored directories, and redeploy timing.Help centergroup indocs.json.Context
Assistant conversations in the last week included a strongly negatively-rated thread where a user's
.jsonfile at the repo root was not being served. Existing coverage in/create/filesonly lists the auth and 20 MB caveats; users hitting other causes (path mismatch, mintignore, auto-ignored directories, unsupported extension, pre-deploy) had no single troubleshooting entry point. The new page is indexed for search and the assistant but excluded from the sidebar per the help center convention.Note
Low Risk
Documentation-only addition with no product, auth, or data-handling changes.
Overview
Adds a searchable Help center article that walks users through why a committed static file (JSON, PDF, image, etc.) can return 404 at its expected URL.
The page covers path/case mismatches, unsupported or Enterprise-only extensions, the 20 MB limit, authentication blocking direct file URLs,
.mintignoreand auto-ignored directories, and needing a successful deploy after adding the file. It is registered in the hidden Help center nav for English, Spanish, French, and Chinese.Reviewed by Cursor Bugbot for commit 08a46c8. Bugbot is set up for automated code reviews on this repo. Configure here.