Skip to content

docs: redirect the old Instrument-your-application path - #131

Open
dankoverride wants to merge 1 commit into
mainfrom
lovelace/redirect-old-instrument-path
Open

dankoverride wants to merge 1 commit into
mainfrom
lovelace/redirect-old-instrument-path

Conversation

@dankoverride

Copy link
Copy Markdown
Collaborator

The DeepCube Web Home page and released builds link to /Setup/Custom-application/Instrument-your-application/, which returns 404 today. This adds the redirect to /Instrument/ in mkdocs.yml, the live redirect layer. src/redirects.conf already carries the same rule, so the two maps now agree.

  • mkdocs build --strict passes, and the generated page points to Instrument/.
  • check-redirect-parity.py: no conflicts.

Independent of the Web revamp docs; safe to merge and deploy on its own.

🤖 Generated with Claude Code

The app's Home page and released builds link to
/Setup/Custom-application/Instrument-your-application/, which 404s on
docs.deepcube.ai. The 301 exists only in the dormant src/redirects.conf;
mkdocs.yml is the live layer, so add it there.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@dankoverride
dankoverride requested a review from ETWOYA as a code owner November 8, 2026 21:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Development

Successfully merging this pull request may close these issues.

1 participant