Repository navigation
Conversation
The English and Chinese home-page Javadoc buttons pointed to /javadoc, which never existed as a page and returned 404. Use the live /api/ route and redirect both legacy bookmark paths to it. Co-Authored-By: Claude Code <noreply@anthropic.com>
Set target: _self on both hero Javadoc actions. Without a target attribute, VitePress's click handler treats /api/ as an internal page, tries to load api/index and shows its own 404; the request never reaches the /api/ Pages Function. The nav and sidebar API Reference links already use target: _self for the same reason. Also note in _redirects that the 14 frozen archive homepages still link to /javadoc and rely on this rule; those buttons land on the current version's Javadoc by design. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
fix(home): point the Javadoc button at /api/ and redirect /javadoc
Deploying ultitools-dev-doc with
|
| Latest commit: |
62b4873
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://b7012d7d.ultitools-dev-doc.pages.dev |
| Branch Preview URL: | https://alpha.ultitools-dev-doc.pages.dev |
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
Promotes the home-page Javadoc button fix (#148) from
alphatomaster(production, dev.ultikits.com).On production, the hero button "Javadoc" on
/and/zh/links tohttps://dev.ultikits.com/javadoc, which returns 404. It was found by the production dead-link acceptance re-run onmastera625ebc(#147, item 1).Changes (merge-base diff: 3 files)
docs/src/index.md,docs/src/zh/index.md: the hero Javadoc button links to/api/withtarget: _self. The target keeps VitePress's client router from intercepting the link, the same way the nav API Reference link already works.docs/public/_redirects:/javadocand/zh/javadocredirect (301) to/api/. The 14 archived homepages still use the old link and rely on this rule.master-only content (#83,/zh/api/*redirect comment andscripts/verify-api-proxy.sh) is untouched by this merge.Gates (on #148, head
c88918c)Author-family review, cross-family review (first run and confirmation run, 0 open P1/P2), real-browser UAT on a clean build served with the Pages Functions runtime (dead-link sample and hero-button click both pass), CI green. Details: #148.
After deployment, the dead-link acceptance row is re-run on production to close #147 item 1.
Issue closure
None
🤖 Generated with Claude Code