Remove the capabilities entry from the Get Started sidebar

[claude]

Requested by Nicolas · Slack thread

Before: capabilities sat second in the Get Started group of the Documentation tab, directly under introduction. It was the first thing a reader saw in the sidebar. It was also the only entry in that group with an icon, because capabilities.mdx:7 sets icon: "list-check" while all eight sibling pages set no icon. The single icon broke the alignment of the group.

After: the Get Started group starts with introduction and then goes straight to the MCP group. No entry in the group has an icon, so the alignment is uniform again.

This removes one line from the navigation config and nothing else.

How: the change deletes "capabilities", from the en / v2 Get Started pages array in docs.json. That is the whole diff, one line.

The page is not deleted. capabilities.mdx stays in the repo, so docs.firecrawl.dev/capabilities keeps working, and the two inbound links from features/crawl.mdx:42 and api-reference/endpoint/scrape.mdx:8 keep resolving. This makes the change reversible: to put the page back in the sidebar, add the line again.

The icon needs no separate edit. It comes from the page frontmatter, not from the nav config, so it leaves the sidebar together with the entry. The icon: "list-check" line stays in capabilities.mdx, and it would apply again if the page ever returns to the nav.

The five locale nav entries (es/capabilities, fr/capabilities, ja/capabilities, pt-BR/capabilities, zh/capabilities) are left alone. The repo CLAUDE.md says not to edit localized content by hand, and locadex re-syncs those blocks. Tell me if you want them removed in this PR instead.

PR #1364 added the entry on 2026-09-08.

Verification: docs.json parses as valid JSON. Nav resolution after the edit: 1,781 entries, 1,439 unique, 0 missing files. capabilities no longer appears in the English nav.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CYSesehkKTc53tRrvKMn3x

---

Generated by Claude Code

[mintlify]

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

Project	Status	Preview	Updated
firecrawl	🟢 Ready	View Preview	Sep 9, 2026, 8:14 PM

💡 Tip: Enable Automations to automatically generate PRs for you.

[claude]

The failing check is not caused by this change. I am leaving the diff at one line.

Failing check: "Locale literals and extraction-hostile markdown", conclusion failure, on head fe2c38a.

What actually fails: the job runs three scripts. Two pass. The one that fails is scripts/check-locale-api-literals.sh, at the "Keep API literals untranslated" step. It reports 14 findings, all in localized .mdx content, where a translation turned an API identifier into the local language:

translated API literal: es/features/change-tracking.mdx uses `seguimientoDeCambios`, which no English page uses
translated API literal: es/webhooks/events.mdx uses `rastreo.iniciado`, which no English page uses
translated API literal: fr/features/monitoring.mdx uses `suiviDesModifications`, which no English page uses
translated API literal: pt-BR/v0/sdks/node.mdx uses `dadosRaspados`, which no English page uses

(plus 10 more of the same shape across es/, fr/ and pt-BR/)

Proof it is pre-existing: I ran the same script on main at the merge base a4abc26f, which is this branch's parent. It exits 1 there too, and the output is byte-identical to the run on this branch (diff -q reports no difference). Node 22.22.2 in both runs.

Why it cannot be this change: check-locale-api-literals.sh never reads docs.json. A grep of the script for docs.json, mint.json, nav and capabilit returns nothing. It compares code identifiers in localized .mdx files against the English pages. This PR touches one line of docs.json and no .mdx file at all.

On nav parity, since it came up: there is no parity check between the English nav and the locale navs. The five locale entries (es/capabilities and so on) still resolve to files that still exist, so nothing breaks. I left them for locadex, per the repo CLAUDE.md.

This PR's own verification: docs.json parses as valid JSON. Nav resolution gives 1,781 entries, 1,439 unique, 0 missing files. The other two scripts in the job, check-locale-api-literals-selftest.sh and check-extraction-hostile-markdown.sh, both pass on this branch.

The locale literal findings look worth fixing, but they belong in their own PR against the translation pipeline, not here.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CYSesehkKTc53tRrvKMn3x