Skip to content

docs(home): point Kane CLI cards on the docs home page to the Mintlify site - #3298

Open
anubhavsinghmaar wants to merge 1 commit into
LambdaTest:stagefrom
anubhavsinghmaar:docs/kane-cli-index-to-mintlify-stage
Open

docs(home): point Kane CLI cards on the docs home page to the Mintlify site#3298
anubhavsinghmaar wants to merge 1 commit into
LambdaTest:stagefrom
anubhavsinghmaar:docs/kane-cli-index-to-mintlify-stage

Conversation

@anubhavsinghmaar

Copy link
Copy Markdown
Contributor

What

The product grid on the docs home page (src/pages/docs.js) linked all eight Kane CLI cards to /support/docs/kane-cli-*/ (Docusaurus). Kane CLI documentation is actually served by the Mintlify stack at /docs/, so clicking "Kane CLI" on the index took readers to the wrong stack.

This repoints only the Kane CLI card. All 18 other product cards are untouched and still point at /support/docs/.

Card link Before After
Getting Started /support/docs/kane-cli-introduction/ /docs/kane-cli-introduction
Installation /support/docs/kane-cli-installation/ /docs/kane-cli-installation
Quick Start /support/docs/kane-cli-quickstart/ /docs/kane-cli-quickstart
Writing Objectives /support/docs/kane-cli-writing-objectives/ /docs/kane-cli-writing-objectives
Generate Test Cases /support/docs/kane-cli-generate/ /docs/kane-cli-generate
Checkpoints /support/docs/kane-cli-checkpoints/ /docs/kane-cli-checkpoints
Agent Mode /support/docs/kane-cli-agent-mode/ /docs/kane-cli-agent-mode
CLI Reference /support/docs/kane-cli-cli-reference/ /docs/kane-cli-cli-reference

Notes

  • No trailing slash on the new targets. That is the canonical form on the Mintlify site: https://www.testmuai.com/docs/<slug>/ 308-redirects to /docs/<slug>, so the slash-less form avoids a redirect hop.
  • Getting Started targets /docs/kane-cli-introduction, the new home of the Kane CLI introduction page. That page currently serves the Mintlify site root and is being moved in the companion stage-mintlify PR — merge that one first, or this link 404s.
  • These are plain <a href> elements, so the paths are root-absolute and bypass the Docusaurus baseUrl (/support/) — which is what we want, since /docs/ is a different stack. Consequence: they do not resolve against a local docusaurus start server, only against the deployed site.

Verification

  • docusaurus start compiles clean (only the pre-existing all-apis.json prebuild error, unrelated).
  • Home page renders 19 cards / 113 links; 8 now resolve to /docs/*, the other 105 unchanged at /support/docs/*.
  • All 8 target slugs confirmed to exist on stage-mintlify.

🤖 Generated with Claude Code

…y site

The Kane CLI documentation is served by the Mintlify stack at /docs/, not by
Docusaurus at /support/docs/. The product grid on the docs home page still
linked to the Docusaurus copies, so clicking "Kane CLI" took readers to the
wrong stack.

Repoint all eight Kane CLI cards to /docs/<slug> (no trailing slash, which is
the canonical form on the Mintlify site - /docs/<slug>/ 308-redirects to it).
Every other product card is untouched and still points at /support/docs/.

"Getting Started" now targets /docs/kane-cli-introduction, the new home of the
Kane CLI introduction page (previously served at the Mintlify site root).

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
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