Skip to content

release-8.5: implement a new information architecture for TiDB and TiDB Cloud docs#22420

Merged
qiancai merged 49 commits intorelease-8.5from
feature/preview-top-navigation
Feb 11, 2026
Merged

release-8.5: implement a new information architecture for TiDB and TiDB Cloud docs#22420
qiancai merged 49 commits intorelease-8.5from
feature/preview-top-navigation

Conversation

@qiancai
Copy link
Collaborator

@qiancai qiancai commented Feb 6, 2026

What is changed, added or deleted? (Required)

This PR reorganizes the documentation structure and improves experiences of developers by making the following changes:

  • Introduces new top-level navigation categories for AI, API, Best Practices, Developer Guides, and TiDB Releases, providing a clearer and more intuitive information architecture.
  • Adds dedicated Table of Contents (TOC) files for these categories to streamline navigation and improve content discoverability.
  • Reorganizes AI documentation by consolidating all AI-related content into a new top-level ai/ directory (migrated from vector-search/), adding a new landing page (ai/_index.md), and updating internal links accordingly.
  • Restructures the Developer Guide with a new overview page (develop/_index.md), clearer sections for TiDB basics, language and ORM integrations, and MySQL client tools, while aligning existing documents with the new structure.
  • Centralizes API documentation under a new api/ directory, including dedicated overview pages for TiDB Cloud APIs (v1beta1 and v1beta) and TiDB Self-Managed APIs (TiProxy, Data Migration, Monitoring, TiCDC, and TiDB Operator).
  • Cleans up and simplifies documentation content by removing platform-specific CustomContent tags across multiple sections, creating a more unified and maintainable documentation base.
  • Updates numerous internal links throughout the documentation to reflect the new structure and ensure consistency.

Which TiDB version(s) do your changes apply to? (Required)

Tips for choosing the affected version(s):

By default, CHOOSE MASTER ONLY so your changes will be applied to the next TiDB major or minor releases. If your PR involves a product feature behavior change or a compatibility change, CHOOSE THE AFFECTED RELEASE BRANCH(ES) AND MASTER.

For details, see tips for choosing the affected versions.

  • master (the latest development version)
  • v9.0 (TiDB 9.0 versions)
  • v8.5 (TiDB 8.5 versions)
  • v8.1 (TiDB 8.1 versions)
  • v7.5 (TiDB 7.5 versions)
  • v7.1 (TiDB 7.1 versions)
  • v6.5 (TiDB 6.5 versions)
  • v6.1 (TiDB 6.1 versions)
  • v5.4 (TiDB 5.4 versions)

What is the related PR or file link(s)?

  • This PR is translated from:
  • Other reference link(s):

Do your changes match any of the following descriptions?

  • Delete files
  • Change aliases
  • Need modification after applied to another branch
  • Might cause conflicts after applied to another branch

qiancai and others added 30 commits January 12, 2026 08:52
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* *: create TOC and add index for TiDB releases

Moved the detailed release notes navigation from TOC.md to a new TOC-tidb-releases.md file. Renamed releases/release-notes.md to releases/_index.md and updated all references to the new path across documentation. This change improves maintainability and centralizes release notes navigation.

* Reformat and reorganize TiDB releases TOC

Updated TOC-tidb-releases.md to use markdown headings for sections and improved the structure for better readability. No content changes to the release list; only formatting and organization were modified.

* Improve formatting of TiDB Cloud releases TOC

Reorganized the table of contents in TOC-tidb-cloud-releases.md for better readability by adding section headers and updating list formatting.

* Add alias for TiDB v8.5 release notes

Added '/tidb/v8.5/release-notes/' to the list of aliases for the release notes page to improve accessibility for users seeking v8.5 documentation.
Standardized section headers and link labels for TiDB Cloud and Self-Managed APIs in the table of contents. Improved clarity by renaming links to include 'API' and removed the beta image from the TiDB Cloud section.
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
* new nav: categorize best practices TOC items

Organized the table of contents into sections: Overview, Schema Design, Deployment, Operations, Performance Tuning, and Application Scenarios. This improves readability and helps users find relevant best practices more easily.

* Refactor TOC to use nested list format

Reorganized the Table of Contents in TOC-best-practices.md to use a nested list format for improved readability and structure. This change groups related best practices under their respective categories using indentation.

* Update format

* Remove an extra line

* Update TOC-best-practices.md
* *: enrich best practices index and move one doc

* Expand TiDB best practices overview and schema design

Added detailed sections and tables for best practice topics, including an overview and schema design recommendations. Introduced links to specific best practice documents for DDL management, UUID primary keys, multi-column indexes, and index management. Added placeholders for deployment, operations, and performance tuning sections.

* Update best practices index and PD scheduling terms

Expanded the best practices index with detailed tables and descriptions for deployment, operations, and performance tuning topics. Updated 'scale-down' terminology to 'scale-in' in the PD scheduling best practices document for consistency and clarity.

* Add aliases to public cloud best practices doc

Added aliases to the TiDB best practices on public cloud documentation for improved URL compatibility and easier access.

* Update descriptions

* Update wording

* Apply suggestions from code review

Co-authored-by: Grace Cai <qqzczy@126.com>

* Update _index.md

---------

Co-authored-by: Grace Cai <qqzczy@126.com>
Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Co-authored-by: qiancai <qqzczy@126.com>
Co-authored-by: lilin90 <lilin@pingcap.com>
@qiancai qiancai added the type/refactor The issue belongs to a refactor work. label Feb 7, 2026
Yuiham and others added 10 commits February 9, 2026 16:18
* chore(package): update package.json and package-lock.json to add new devDependencies for linting and markdown checks

* chore(scripts): add script to verify internal links in TOC files and ensure all referenced pages exist

* chore(ci): restructure CI workflow to add jobs for verifying duplicated file names, internal links, and TOC membership

* chore(scripts): enhance internal link verification script with configurable verbosity and limits for missing pages and violations

* chore(scripts): extend internal link verification to include source TOC references in violation reports

* chore(scripts): improve output formatting in internal link verification script for better readability

* chore(scripts): refactor internal link verification script to improve target extraction and sorting logic

* chore(scripts): format code for improved readability in internal link verification script
@qiancai qiancai added translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. and removed translation/doing This PR's assignee is translating this PR. labels Feb 11, 2026
Copy link
Member

@lilin90 lilin90 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@ti-chi-bot ti-chi-bot bot added the needs-1-more-lgtm Indicates a PR needs 1 more LGTM. label Feb 11, 2026
@ti-chi-bot
Copy link

ti-chi-bot bot commented Feb 11, 2026

[LGTM Timeline notifier]

Timeline:

  • 2026-02-11 06:51:19.295641474 +0000 UTC m=+1232.375632169: ☑️ agreed by lilin90.

@qiancai qiancai added needs-cherry-pick-master Should cherry pick this PR to master branch. lgtm labels Feb 11, 2026
@qiancai
Copy link
Collaborator Author

qiancai commented Feb 11, 2026

/approve

@ti-chi-bot
Copy link

ti-chi-bot bot commented Feb 11, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: qiancai

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@ti-chi-bot ti-chi-bot bot added the approved label Feb 11, 2026
@qiancai qiancai self-assigned this Feb 11, 2026
@qiancai qiancai merged commit b746912 into release-8.5 Feb 11, 2026
9 of 11 checks passed
ti-chi-bot pushed a commit to ti-chi-bot/docs that referenced this pull request Feb 11, 2026
Signed-off-by: ti-chi-bot <ti-community-prow-bot@tidb.io>
@ti-chi-bot
Copy link
Member

In response to a cherrypick label: new pull request created to branch master: #22439.
But this PR has conflicts, please resolve them!

qiancai added a commit that referenced this pull request Feb 11, 2026
…oud docs (#22420) (#22439)

Co-authored-by: Grace Cai <qqzczy@126.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved area/develop This PR relates to the area of TiDB App development. lgtm needs-1-more-lgtm Indicates a PR needs 1 more LGTM. needs-cherry-pick-master Should cherry pick this PR to master branch. size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. translation/done This PR has been translated from English into Chinese and updated to pingcap/docs-cn in a PR. type/refactor The issue belongs to a refactor work.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants