Repository navigation
fix(docs): publish current documentation at root - #873
Merged
Merged
Conversation
…"" This reverts commit c187fd7.
GitHub Pages caches HTML for ten minutes. The first root deploy replaced every page under latest/ and 3.x/ with a redirect stub and deleted the alias assets, so cached alias pages loaded 404 stylesheets and rendered unstyled. Mirror the full build into each alias before writing the stubs. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Co-Authored-By: lino@rapidata.ai <68745352+LinoGiger@users.noreply.github.com>
LinoGiger
marked this pull request as ready for review
September 15, 2026 12:16
LinoGiger
deleted the
fix(docs)/publish-current-documentation-at-root
branch
September 15, 2026 12:16
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.
What
Re-applies #871 (publish the current documentation at
https://docs.rapidata.ai/, no version prefix) with the fix for why the first attempt rendered unstyled.Why the first deploy looked broken
The build was fine. GitHub Pages serves HTML with
cache-control: max-age=600. The first root deploy replaced every page under/latest/and/3.x/with a redirect stub and deleted the assets under those prefixes. For up to ten minutes browsers and the CDN kept serving the cached full pages from/latest/..., whose stylesheets (/latest/assets/stylesheets/main.*.css) were now 404. Result: unstyled pages until the cache expired, which looked like a broken build and triggered the revert.Fix
prepare_docs_site.pynow mirrors the complete build (assets, media, search index, markdown, llms files) intolatest/and3.x/before overwriting their HTML pages with redirect stubs. A stale cached alias page therefore still finds its assets and renders normally, and a fresh request is redirected to the root URL.Verified locally by building main, running the script against the real
gh-pagestree, then rendering the pre-deploy/3.x/quickstart/HTML against the new tree in headless Chrome: fully styled.After merge
main(no inputs any more)./latest/...and/3.x/...redirect to the same path at the root; obsolete paths (/starting_page/,/improve_order_quality/, old*_orderexamples) redirect to their replacement or/migration/;/2.x/is kept as-is.Includes the #872 developer-portal fix implicitly: the copy step it patched no longer exists.
🔗 Session: https://poseidon.rapidata.internal/chat/session-41cd4687
🤖 Generated with Claude Code