♻️[Refactor] Remove redundant tools URL namespace - #95
Merged
Merged
Conversation
Closed
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.
Closes #94.
The public site currently inherits
/tools/from its source directory because the Cloudflare deployment copies the repository tree directly. This change stages a manifest-drivendist/artifact so canonical tool URLs live at/<category>/<tool>/, while every former/tools/*URL returns a one-hop 308 redirect to its root-level destination.The existing
/privacy/policy and Privacy category would collide after removing the prefix, so/privacy/now preserves the policy and includes the metadata-tool links. Canonical and Open Graph URLs, internal navigation, sitemap entries, browser smoke coverage, and deployment validation use the new namespace. OCR worker, core/WASM, English and Korean traineddata, and all runtime dependencies remain same-origin with the existing CSP and privacy boundaries.Validation:
npm ci --ignore-scriptsnpm run prepare:ocrnpm testnpm run buildnode scripts/validate-build.mjsnode tests/ocr-smoke.test.mjsgit diff --check origin/v2.2...HEAD