Skip to content

docs: expand the "this site has moved" note into a usable dead-end sign - #8

Merged
bryanfawcett merged 1 commit into
mainfrom
docs/readme
Sep 11, 2026
Merged

bryanfawcett merged 1 commit into
mainfrom
docs/readme

Conversation

@bryanfawcett

Copy link
Copy Markdown
Member

The existing five-line README already told the truth - the site moved to
nyuchi/nyuchi-docs - so this keeps that verdict and does not soften it.
What it adds is the evidence, and a reader's next step.

Confirmed superseded, not merely quiet:

  • Commit b84f6e6 (24 May 2026), "chore: redirect to nyuchi/nyuchi-docs
    (Starlight)", is the moment the redirect note was added.
  • PR feat(theme): rebrand the docs site as Nyuchi Docs #5, "feat(theme): rebrand the docs site as Nyuchi Docs", was closed
    unmerged - the rebrand was attempted and abandoned.
  • docs.json is still the mintlify/product-guide-starter template:
    "name": "Product Guide", "theme": "almond", and global anchors
    pointing at Mintlify's own changelog and support pages. AGENTS.md
    still opens with the template's "Customize this file" instruction.
  • The content did land in the successor. nyuchi/nyuchi-docs carries
    site/src/content/docs/platform/{support-chat,product-workspaces}.mdx,
    integrations/{authentication,quickstart}.mdx and the api/* set that
    PRs Document in-app support chat #1-Add /v1 API gateway, WorkOS auth, and security docs #4 wrote here.

The page count is stated as 36, counted, rather than estimated.

No aspirational docs-site README was written: there is no install, no
usage and no "run mint dev" section, because running this site is not
something anyone should now do.

Links curled: docs.nyuchi.com 200, docs.bundu.org 200,
github.com/nyuchi/nyuchi-docs 200, mintlify.com 200,
github.com/mintlify/product-guide-starter 200, all three badges 200.
docs.mzizi.dev is not linked - it does not resolve.

The repo has no LICENSE file, and the licence section says so rather
than asserting one.

Co-Authored-By: Claude Opus 5 (1M context) noreply@anthropic.com

@bryanfawcett
bryanfawcett enabled auto-merge (rebase) September 11, 2026 19:54
The existing five-line README already told the truth - the site moved to
nyuchi/nyuchi-docs - so this keeps that verdict and does not soften it.
What it adds is the evidence, and a reader's next step.

Confirmed superseded, not merely quiet:

- Commit b84f6e6 (24 May 2026), "chore: redirect to nyuchi/nyuchi-docs
  (Starlight)", is the moment the redirect note was added.
- PR #5, "feat(theme): rebrand the docs site as Nyuchi Docs", was closed
  unmerged - the rebrand was attempted and abandoned.
- docs.json is still the mintlify/product-guide-starter template:
  "name": "Product Guide", "theme": "almond", and global anchors
  pointing at Mintlify's own changelog and support pages. AGENTS.md
  still opens with the template's "Customize this file" instruction.
- The content did land in the successor. nyuchi/nyuchi-docs carries
  site/src/content/docs/platform/{support-chat,product-workspaces}.mdx,
  integrations/{authentication,quickstart}.mdx and the api/* set that
  PRs #1-#4 wrote here.

The page count is stated as 36, counted, rather than estimated.

No aspirational docs-site README was written: there is no install, no
usage and no "run mint dev" section, because running this site is not
something anyone should now do.

Links curled: docs.nyuchi.com 200, docs.bundu.org 200,
github.com/nyuchi/nyuchi-docs 200, mintlify.com 200,
github.com/mintlify/product-guide-starter 200, all three badges 200.
docs.mzizi.dev is not linked - it does not resolve.

The repo has no LICENSE file, and the licence section says so rather
than asserting one.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@bryanfawcett
bryanfawcett merged commit d22fa08 into main Sep 11, 2026
7 checks passed
@bryanfawcett
bryanfawcett deleted the docs/readme branch September 11, 2026 19:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant