feat: add Docusaurus redirect mapping for stable and placeholder URLs #177
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
This PR implements the Phoenix “App Links” redirect system using
@docusaurus/plugin-client-redirects(v3.7.0).It introduces a centralized
app-links.jsfile that defines stable, version-independent URLs used by both the Phoenix app and the documentation site.📘 Overview
The new system allows Phoenix desktop and browser apps to reference stable URLs such as:
These URLs can be redirected to any internal or external destination and can also serve as placeholder links before actual documentation pages are written.
This makes it safe to wire app-level links early and restructure documentation later without breaking links.
🧭 Use Case
⚙️ Behavior
npm run start: Dev server does not generate redirect pages.npm run build: Static redirect pages are generated.npm run serve: Serves the built site with working redirects.🧱 Schema
Each entry follows:
from→ must begin with/app-links/...to→ can be:💡 Example Entries
✅ Testing
npm run buildnpm run servehttps://localhost:3000/app-links/<any-entry>