Skip to content

fix: add CLI to Developer Tools overview, dedupe MCP Setup title#276

Merged
joalves merged 3 commits into
masterfrom
fix/dev-tools-overview-cli-mcp-title
Jul 9, 2026
Merged

fix: add CLI to Developer Tools overview, dedupe MCP Setup title#276
joalves merged 3 commits into
masterfrom
fix/dev-tools-overview-cli-mcp-title

Conversation

@joalves

@joalves joalves commented Jul 9, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • The Developer Tools overview page (docs/APIs-and-SDKs/overview.mdx) listed SDK Guide, SDK API, Platform API and MCP Server but never mentioned the CLI, even though it has its own sidebar category (CLI-Documentation). Added a "CLI" section and a row in the "Which one should I use?" table.
  • The MCP Server Setup page (docs/APIs-and-SDKs/MCP-Server/setup.mdx) rendered the "Setup" title twice. Root cause: the page has export const ... MDX declarations before its in-content # Setup H1. Docusaurus's parseMarkdownContentTitle only strips leading import statements, not export, so it never finds the H1 and falls back to rendering the frontmatter title: Setup as a synthetic heading — on top of the literal # Setup already in the content. Fixed by removing the redundant # Setup heading from the content itself (simpler than hide_title: true, per review feedback), so the frontmatter title renders as the only H1.
  • Removed the "Area / Status" stability table from the CLI overview page (CLI-Documentation/index.mdx) — it read like an internal engineering tracker rather than customer-facing docs.
  • Reworded the --profile staging examples across CLI-Documentation/index.mdx, authentication.mdx and configuration.mdx. Customers only ever have one ABsmartly instance, so an example profile pointed at a different endpoint (staging.absmartly.com) was misleading. Profiles are more realistically used to switch between credentials with different permissions (e.g. a read-only key), so all examples now use a readonly profile against the same instance.
  • Dropped the parenthetical (chmod 600) from the CLI Authentication page's intro paragraph — an implementation detail that read oddly out of context for docs.

Test plan

  • Ran yarn install + npx docusaurus start in an isolated worktree and confirmed the dev build compiles successfully
  • Verified via Playwright that /docs/APIs-and-SDKs/MCP-Server/setup now renders exactly one <h1>Setup</h1>
  • Verified /docs/APIs-and-SDKs/overview now shows a CLI section with working links to CLI-Documentation pages, and a CLI row in the comparison table
  • Verified /docs/APIs-and-SDKs/CLI-Documentation/ no longer shows the status table, and /docs/APIs-and-SDKs/CLI-Documentation/authentication no longer shows (chmod 600) and uses readonly profile examples
  • Screenshots confirmed visually (before/after match the reported bugs)

Summary by CodeRabbit

  • Documentation
    • Added a new CLI section to the APIs and SDKs overview, including links to common starting points.
    • Updated the “Which one should I use?” table with a row directing users to the CLI for experiment management from terminal or CI/CD workflows.
    • Updated CLI documentation examples to use readonly profiles (instead of staging) for authentication and configuration.
    • Cleaned up the MCP Server setup page by relying on the existing page title for heading display.
    • Removed the “Area / Status” stability table from the ABsmartly CLI overview section.

The Developer Tools overview page listed SDK Guide, SDK API, Platform
API and MCP Server but omitted the CLI, even though it has its own
sidebar category. Added a CLI section and table row.

The MCP Server Setup page rendered its H1 twice: `export const` MDX
declarations before the in-content `# Setup` heading stopped
Docusaurus's title parser from detecting it (it only strips leading
`import` statements), so it fell back to rendering the frontmatter
title as a synthetic H1 on top of the literal one. Added
`hide_title: true`, the same pattern already used elsewhere in this
repo for pages with pre-heading MDX exports.
@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown

Review Change Stack

Walkthrough

This change adds a CLI subsection and comparison-table entry to the APIs-and-SDKs overview. It updates CLI authentication and configuration examples to use a readonly profile, removes a credential-permissions note, removes the CLI stability table, revises the non-interactive setup example, and removes the standalone heading from the MCP Server setup page.

Estimated code review effort: 2 (Simple) | ~12 minutes

Possibly related PRs

  • absmartly/docs#275: Updates the same CLI documentation area with related example and overview changes, including readonly profile usage and CLI page content.

Suggested reviewers: marcio-absmartly, mario-silva, bmsilva

Poem

A bunny found the docs in bloom,
Hopped past CLI notes in the room.
Readonly profiles, neat and small,
Make the setup paths stand tall.
With a twitchy nose, I cheer this tune.

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed Clearly summarizes the two main documentation changes: adding the CLI to the overview and removing the duplicate MCP Setup heading.
✨ Finishing Touches
📝 Generate docstrings
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/dev-tools-overview-cli-mcp-title

Comment @coderabbitai help to get the list of available commands.

@netlify

netlify Bot commented Jul 9, 2026

Copy link
Copy Markdown

Deploy Preview for absmartly-docs ready!

Name Link
🔨 Latest commit f7399b0
🔍 Latest deploy log https://app.netlify.com/projects/absmartly-docs/deploys/6a4f83ae59fb6200089ff83e
😎 Deploy Preview https://deploy-preview-276--absmartly-docs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify project configuration.

Comment thread docs/APIs-and-SDKs/MCP-Server/setup.mdx Outdated
---
title: Setup
sidebar_position: 3
hide_title: true

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

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

Why not just remove the title from the markdown? 😅

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Good call, done — removed the redundant # Setup heading from the content instead.

Remove the status table from the CLI overview page — it read as an
internal engineering tracker rather than customer-facing docs.

Reword profile examples: customers only ever have one instance, so a
"staging" profile with a different endpoint was a misleading example.
Profiles are more realistically used to switch between credentials
with different permissions (e.g. a read-only key), so all examples
now use a "readonly" profile against the same endpoint.

Also drop the parenthetical "(chmod 600)" from the Authentication
page intro — an implementation detail that reads oddly out of context.
Per review feedback, dropping the duplicate `# Setup` heading from the
content is simpler than hiding the frontmatter title with
hide_title: true — same rendered result, one less frontmatter flag.
@joalves joalves merged commit 0ed48e7 into master Jul 9, 2026
6 checks passed
@joalves joalves deleted the fix/dev-tools-overview-cli-mcp-title branch July 9, 2026 11:25
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.

2 participants