Skip to content

Fix overly long SEO descriptions#16

Open
mintlify[bot] wants to merge 85 commits into
mainfrom
mintlify/seo-descriptions-1775434197
Open

Fix overly long SEO descriptions#16
mintlify[bot] wants to merge 85 commits into
mainfrom
mintlify/seo-descriptions-1775434197

Conversation

@mintlify

@mintlify mintlify Bot commented Apr 6, 2026

Copy link
Copy Markdown
Contributor

Summary

  • Shortened the description frontmatter on platform/colocation.mdx (464 → 133 chars) and platform/self-trade-prevention.mdx (209 → 117 chars) to stay within the recommended 50–160 character range for SEO.
  • Removed inline markdown links from the colocation description, which don't render in meta tags.
  • All other 177 MDX pages already have compliant descriptions (or are snippets without frontmatter, which is expected).

  Implements the AI System Improvement initiative (Phases A–D):

  Phase A — Governance:
  - Add ai/RULES.md: all binding rules (AI behavior, pipeline gates, commit
    protocol, validation, content rules, self-improvement policy)
  - Add ai/LESSONS.md: pattern-triggered accumulated lessons (empty scaffold)
  - Slim CLAUDE.md to 53 lines (was 23 rules inline); all rules migrated to
    ai/RULES.md; add Commands section, Skills table, Key Files table
  - Add AGENTS.md: agent-agnostic entry point for Kiro, Cursor, and others

  Phase B — Skills system:
  - Add ai/skills/ with 9 skill files (dev-ticket-pipeline, doc-review-pipeline,
    task-self-review, self-improvement, promote-learnings, generate-docs-from-spec,
    write-commit-message, create-initiative-spec, cleanup-after-pipeline)
  - Update ai/agent.md: section 3 adds ai/skills/, ai/specs/, governance files;
    section 5 replaces step-by-step pipelines with one-line skill references

  Phase C — Claude Code Skills (official format):
  - Add .claude/skills/ with 9 SKILL.md directories (official format, not
    legacy .claude/commands/); all use disable-model-invocation: true;
    write-commit-message uses dynamic git diff injection

  Phase D — Initiative spec:
  - Add ai/specs/ai-system-improvement/ and ai/specs/claude-skills-research/
    (spec-driven pipeline used throughout; all phases complete)
chore(ai): add skills layer, governance files, and Claude Code skills
fix(api): add missing mining pool rewards fields
fix(api): typo
api(docs): change payoutDestination example in mining rewards response
added missing-schemas or validation
…ages, add nav links

- Add GET /api/v1/public/kline (Market Data) — new MDX page and nav entry
- Fix collateral open positions endpoint path: /positions → /positions/open
  in openapi/private/http-trade-v4.yaml and open-positions.mdx
- Remove cancel-oco-order and cancel-oto-order pages, nav entries, and
  legacy redirects — endpoints no longer documented
- Add \"We are hiring\" and GitHub (type: github) links to navbar
- Add github social to footer socials
docs(api): add kline, fix positions endpoint, remove cancel OCO/OTO pages, add nav links
- Add guides/mcp-server.mdx — full setup guide for the whitebit-mcp
  trading server (115 tools); covers Claude Code, Cursor, Claude Desktop,
  Codex, and OpenClaw client configuration
- Add guides/cli.mdx — CLI reference with commands, authentication,
  examples, and coming-soon install notice (source only for now)
- Add guides/ai-faq.mdx — FAQ covering API key safety, supported clients,
  trading vs docs MCP disambiguation, automation, and safe account practices
- Revamp guides/use-with-ai.mdx — full hub page with 4-card grid,
  feature breakdown by category, and supported AI clients table
- Rename guides/ai-ide-setup.mdx → "Docs search via MCP"; add icon
- Rename guides/ai-context-menu.mdx → "Docs page AI menu"; add icon
- Update docs.json — rename group to "AI Hub", add 3 new pages to nav
docs(ai-hub): add AI Hub section with MCP server, CLI, and FAQ pages
…text

- Rename "WhiteBIT MCP server" to "WhiteBIT documentation MCP server" in
  the IDE quick connect table to distinguish from the trading MCP server
- Update frontmatter description to list actual supported tools (ChatGPT,
  Claude, Perplexity, Grok, Cursor, VS Code, Claude Desktop) instead of
  implying docs integrations exist for Claude Code / Codex / OpenClaw
- Remove duplicate "via MCP via MCP" link text in two places
fix(ai-context-menu): clarify MCP server name and fix duplicate link text
Stage to main
whitebit-robot and others added 27 commits April 1, 2026 15:13
…cs-cleanup

# Conflicts:
#	api-reference/market-data/symbols.mdx
#	private/http-trade-v1/cancel-order.mdx
#	private/http-trade-v1/create-limit-order.mdx
#	private/http-trade-v1/query-executed-order-deals.mdx
#	private/http-trade-v1/query-executed-order-history-by-all-markets.mdx
#	private/http-trade-v1/query-executed-order-history-by-single-market.mdx
#	private/http-trade-v1/query-order-history.mdx
#	private/http-trade-v1/query-unexecuted-active-orders.mdx
#	private/http-trade-v1/trading-balance-by-currency.mdx
#	private/http-trade-v1/trading-balances.mdx
#	public/http-v1/kline.mdx
#	public/http-v1/market-activity.mdx
#	public/http-v1/market-info.mdx
#	public/http-v1/order-depth.mdx
#	public/http-v1/single-market-activity.mdx
#	public/http-v1/trade-history.mdx
#	public/http-v2/asset-status-list.mdx
#	public/http-v2/fee.mdx
#	public/http-v2/market-activity.mdx
#	public/http-v2/market-info.mdx
#	public/http-v2/orderbook.mdx
#	public/http-v2/recent-trades.mdx
Stage to main
chore(api): deprecate V1 and V2 API documentation
Stage to main
… list

Add a Notes section explaining how to classify the three structurally
distinct asset types returned by GET /api/v4/public/assets — crypto
assets, fiat currencies, and fiat payment methods — using the
`confirmations` and `providers` fields as reliable discriminators.
docs(market-data): add asset type classification note to asset status list
Stage to main
…hannel pages

Create snippets/WsChannelOverview.jsx — a React operations table that surfaces
send/respond/push relationships above the fold, replacing Mintlify's default
AsyncAPI renderer which hides all content in collapsed accordions.

Apply the pattern to all 17 WebSocket channel pages:
- WsChannelOverview operations table on every channel
- Steps-based subscription flows with inline JSON examples
- Query sections before Subscribe sections per WS.1.3
- Bold update interval labels per WS.4.2
- Update model + Ordering guarantees sections in depth.mdx per WS.4
- Sentence case fixes across all headings
feat(websocket): add WsChannelOverview component and rebuild all WS channel pages
- POST /api/v4/sub-account/kyc-url added to main_api_v4.yaml with
  full request/response schema and four named 400 error examples
- New MDX page with precondition Note (activation, active state,
  shared KYC)
- Navigation entry added to Account Management group in docs.json
Partner escalation revealed two issues with the crypto lending
plans endpoints:

- "retrieves all active plans" was ambiguous — could be read as
  the user's personal running investments rather than platform-
  offered plan configurations; also omitted filter context
  (region, public/private visibility, API access gating)
- The id → planId workflow (get-plans → invest) was undocumented,
  leaving integrators without guidance on how to use the response

Fixes both endpoints (fixed and flex) in the OpenAPI spec and
adds workflow notes to the corresponding MDX pages.

docs(api): add sub-account unconfirmed withdrawals endpoint

- Add POST /api/v4/sub-account/withdraw/unconfirmed-list to
  main_api_v4.yaml with full request/response schema and
  401/404/422 error responses
- Create spec-driven MDX page
- Add Withdrawals nav group to docs.json and overview card
feat(docs): add workers info to miner info, add reject rate to miner
Documentation actualization
custom component fix
Stage to main
…uite

Replace AsyncAPI renderer with fully custom React components on all
remaining WebSocket channel pages. Every page now uses WsChannelOverview,
WsSchemaTable, WsMessageExample, and WsSubscribeSteps with explicit .jsx
import paths, tag: "WSS" frontmatter, and no native Steps/fenced-code blocks.

Includes:
- 4 new snippet components (WsChannelOverview, WsSchemaTable,
  WsMessageExample, WsSubscribeSteps) as .jsx with all helpers inside
  component function bodies (required by Mintlify RSC bundler)
- 18 auto-generated ws-data files from AsyncAPI YAML schemas
- generate-ws-data.mjs script to regenerate ws-data from spec
- validate.mjs extended with --ws-data and --consistency checks
- .mintlifyignore to exclude ai/ and scripts/ from Mintlify scanner
- Tabular content in JSX props converted to flex-div layout (no <table>)
- Mintlify built-in components confined to MDX top-level scope only

All validations pass: --mdx, --nav, --consistency, --ws-data.
New skills: ai-changelog, ai-improvement-tracker, create-change-request,
docker-local-rebuild, session-retrospective

Consolidation (41 → 9 lessons): promoted 6 rules to RULES.md covering
Mintlify HTML diagnostic, TCR multi-phase gate, commit scope authority,
SME behavioral pass, shared-schema filter inference, and $ref check.
Style guides updated: api-endpoints.md (passive voice, ambiguous qualifier,
SME subject, glossary linking, pronoun sweep) and websocket.md (React global
prohibition, arrow-function requirement). skill-creator extended with porting
checklist, convention drift audit, and skill-reviewer gate before registration.
…example

The import hint comment hardcoded `exOrdersPendingRequest` for every
generated file, regardless of what that file actually exports. Replace
with names extracted from the real generated exports — first schema
export and first example export — so the comment is accurate per file.
feat(websocket): migrate all 17 WS channel pages to custom component s…
template fixes
Stage to main
@mintlify

mintlify Bot commented Apr 6, 2026

Copy link
Copy Markdown
Contributor Author

Preview deployment for your docs. Learn more about Mintlify Previews.

Project Status Preview Updated (UTC)
whitebit 🟢 Ready View Preview Apr 6, 2026, 12:11 AM

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