docs: the docs repo is docs-mantis, not mantis-docs - #80
Merged
Conversation
Every documentation link in this repo — 17 across 9 files — pointed at github.com/privacykey/mantis-docs. That repo was renamed to docs-mantis, so the links only still work because GitHub redirects renames. That redirect is not a guarantee: it breaks the moment anyone creates a new repo under the old name. Four of these ship to users rather than sitting in a README: src/app/(app)/layout.tsx the dashboard's Docs link src/app/login/page.tsx the login screen src/app/(app)/keys/[id]/… the file-key download panel cli/src/commands/init.ts printed by `mantis init` Verified all ten linked pages exist in docs-mantis at main. Deliberately NOT switched to docs.mantis.privacykey.org. That is where these should eventually point, but the hostname has no DNS yet — moving shipping product links onto a dead domain would replace working links with broken ones. Worth a follow-up once the docs site is published.
# Conflicts: # README.md
The href rename left the link text naming the old repo, so the dashboard download panel and the CLI README displayed "mantis-docs" while pointing at docs-mantis. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Move all 17 documentation links off the GitHub Markdown source and onto the Mintlify site, mapping each path to its rendered slug (drop the .md, and deployment/README.md -> /deployment, which is the nav root). Also refresh the prose and link labels that described the old target: the README no longer says the site isn't live, and two link labels that read as repo filenames now read as docs pages. Note: docs.mantis.privacykey.org does not resolve yet (NXDOMAIN). These links will fail until DNS is pointed at the Mintlify deployment, which includes the dashboard Docs link, the login page, the file-key download panel, and `mantis init` output. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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
2 participants
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.
Found while checking every repo's README against this session's changes.
Every documentation link in this repo — 17 across 9 files — points at
github.com/privacykey/mantis-docs. That repo was renamed todocs-mantis. The links still work, but only because GitHub redirects renamed repositories, and that redirect stops the moment anyone creates a new repo under the old name.Four of these ship to users, not just to readers of the README:
src/app/(app)/layout.tsxsrc/app/login/page.tsxsrc/app/(app)/keys/[id]/download-formats.tsxcli/src/commands/init.tsmantis initThe rest are the README,
cli/README.md, and three deploy templates.I verified all ten distinct pages these link to exist in
docs-mantisatmain—api.md,getting-started.md,use-cases.md,file-keys.md,host-events.md,self-hosted-apps.md,updating.md,deployment/README.md,deployment/cloudflare.md,deployment/edge-limits.md.What I deliberately did not do
I did not repoint these at
docs.mantis.privacykey.org.That is where they should eventually go, and the marketing site already uses it. But the hostname has no DNS yet, and mantis is shipping (
cli-v0.1.6is on the Homebrew tap). Moving live product links onto a dead domain would trade working links for broken ones. Worth a one-line follow-up once the docs site is actually published — happy to prepare it now so it's ready to merge the day DNS lands.