docs: open v003 and Tools links in new tabs; remove toolchain demos + v003 later roadmap#109
Merged
Merged
Conversation
docs.pccx.ai is the v002 legacy site now and should serve its own Sphinx build instead of forwarding visitors to docs.altifigence.com. The _extra/_redirects file held nine 301 rules that rewrote every page — /, /*, /en/*, /ko/*, /docs/v002/*, /en/docs/v002/*, /ko/docs/v002/*, /robots.txt, /sitemap.xml — to corresponding paths under docs.altifigence.com. Drop the file entirely. The deploy.yml \"Create root redirect page\" step is gated on `if [ -f _extra/_redirects ]`, so it now no-ops, and the Sphinx build's own root index.html (with its same-domain meta refresh to /en/) keeps the site fully self-contained. Companion change: pccxai/pccx-vision-v001 was deleted on 2026-05-27 and v003 / vision-v001 / Lab were removed from this Sphinx tree in #107. docs.altifigence.com is now the canonical hub for everything beyond v002; docs.pccx.ai is a frozen v002 archive.
- _static/pccx_versions.json: v003 entry now points to https://docs.altifigence.com/v003/ - index.rst, ko/index.rst: dropped Toolchain Demos toctree block; Tools now uses /lab/, /launcher/, /ide/ on altifigence (labels kept English for parity) - docs/roadmap.md + ko/docs/roadmap.md: removed "## Later — v003.x" section and updated family tree caption - docs/samples/index.md + ko/docs/samples/index.md: added :orphan: so removal does not break strict build - conf_common.py, _templates/sidebar/brand.html: updated footer icons - docs/index.rst, README.md, docs/v002/gemma3n-e4b-integration.rst: refreshed stale tool URLs for link health - all changes maintain EN/KO structural parity per repo rules
…r samples pages - _static/pccx-version-switcher.js: v003 entry and all external sidebar links (Tools) now use target=_blank + rel=noopener (via buildEntry + upgradeExternalSidebarLinks) - docs/samples/index.md + ko/docs/samples/index.md: use proper "orphan: true" YAML frontmatter so removal of Toolchain Demos toctree does not trigger "document isn't included" or transition errors under strict -W -n build - All changes maintain EN/KO parity
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.
Changes
target="_blank"+rel="noopener noreferrer")._static/pccx-version-switcher.js(covers both the injected version links and all external links in.sidebar-tree).docs/samples/index.md(EN + KO) so the removal doesn't breakmake strict.docs.altifigence.comfor the external tools.Verification
make lint→ PASS (sphinx-lint + codespell)make strict(EN + KO, -W -n) → PASS, build succeededThis continues the altifigence.com cross-domain work on the same branch.