pingcap / pingcap/docs

Integrate TiDB Cloud API docs into TiDB Cloud docs

Open
#10,387 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

feature-request lifecycle/frozen
Dominant language
Python
Stars
617
Forks
724
Avg merge
2d 10h
Merged PRs (30d)
223

Description

This issue tracks the efforts that integrate TiDB Cloud API docs into TiDB Cloud docs.

Background

  1. Currently, the TiDB Cloud API docs is a page separate from TiDB Cloud docs. When a user visits the API docs, they feel they jump to a totally different site.

TiDB Cloud docs:
TiDB Cloud docs
API docs:
image

  1. The current API docs use the default Redoc theming, which is quite different from the style of our docs site.

Therefore, we need to integrate TiDB Cloud API docs into TiDB Cloud docs and provide consistent, seamless experience for API users.

Tasks

To achieve the goal, we need to do (at least) the following:

  1. Embed the API docs into the current Cloud docs.
    • Users will see the same navigation bar and panels on the top and the left side. They won't feel they are taken to another site when they visit the API docs.
    • Estimated workload:
      • 1 week (FE)
      • 1 week (doc)
  2. Tune the API docs theme to make it more consistent with the Cloud docs style.
    • Estimated workload:
      • 1 month (FE + UI)
      • 1 week (doc)
    • Note: some theming configuration might require subscription of Redocly basic or professional plans. We don't know yet.

Status

After consulting the FE engineer, we reach the following agreement: this feature is nice to have , but we don't have enough resources to invest in it right now. There are two major reasons:

  • The front end resources are tight. The FE engineer is working on other features with higher priority and cannot start developing this feature within the next few months.
  • We don't have budget for Redocly subscirption.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by comparing the TiDB Cloud docs and TiDB Cloud API docs linked in the issue, focusing on navigation, layout, and Redoc theming. Done means the API documentation is embedded in the Cloud docs with consistent navigation, panels, and styling, but the issue notes that frontend and Redocly resources are currently unavailable.

Written by the indexing model from the issue text.

Assessment

Domain
documentation, frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.