docs: point campaign API key steps at the Developer button

[brettstirlingbond]

The Campaigns App no longer has an Integration tab on a campaign, but two of our getting-started pages still send developers there for the campaign API key. This rewrites both lines to point at the Developer button in the campaign header and the Campaigns API section of the modal it opens, using the same name the merchant docs use for it. The generated text bundles for AI readers pick up the change on the next deploy, so nothing else needs editing. Merging it means the two pages match the app as it ships today.

···

What changed

Two lines, one on the docs landing page and one on the Campaigns quick start, now read:

select Developer in the campaign header to open the Developer workspace, then copy the key from the Campaigns API section

• content/docs/index.mdx (Get started, step 3)
• content/docs/campaigns/index.mdx (Quick Start prerequisites)

Why

Campaigns App removed the Integration tab in NextCommerceCo/campaigns-app#479 (closed 2026-05-11). Campaign pages now have Analytics, Packages and Settings tabs, and install details moved into a Developer button in the campaign header. The modal it opens shows the API key under a Campaigns API heading. The merchant docs call this the campaign's Developer workspace (https://docs.nextcommerce.com/docs/apps/campaigns-app), so the wording now matches across both doc sites.

Reviewer notes

• llms-full.txt and llms/campaigns.txt render page bodies at build time and carried the stale line. They regenerate from these MDX files on deploy. llms.txt lists titles and descriptions only and never had it.
• A repo-wide grep finds no other Integration tab references.
• Two related lines were left alone for a follow-up: the Page Kit init callout is vague but accurate, and the Netlify deploy note on the Campaigns page calls authorized domains per-campaign when they are store-wide.
• npm ci && npm run build && npm run check pass locally on Node 22.

🤖 Generated with Claude Code

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

Docs-only change: two prerequisite lines now point at the Developer button / Campaigns API section instead of the removed Integration tab. Wording is identical on both pages, no links or code paths changed, and a repo-wide search confirms no remaining Integration tab references in content/. The llms-full.txt and llms/campaigns.txt surfaces are generated at request time from these MDX files (app/llms-full.txt/route.ts, app/llms/campaigns.txt/route.ts), so the PR's claim that they pick the change up on deploy holds — there is no committed stale copy to update.

Assumption stated: the external merchant page (https://docs.nextcommerce.com/docs/apps/campaigns-app) could not be fetched in this sandbox, so the exact UI labels "Developer workspace" and "Campaigns API" were verified only against the PR description, not the live merchant docs. content/capabilities.yaml last_verified dates were intentionally left untouched; this change alters prose, not links.

Files Reviewed (2 files)

• content/docs/campaigns/index.mdx
• content/docs/index.mdx

---

_{Reviewed by minimax-m3 · Input: 0 · Output: 0 · Cached: 0}

[cloudflare-workers-and-pages]

Deploying with    Cloudflare Workers

The latest updates on your project. Learn more about integrating Git with Workers.

Status	Name	Latest Commit	Preview URL	Updated (UTC)
✅ Deployment successful! View logs	developer-docs	87edf9e	Commit Preview URL Branch Preview URL	Sep 11 2026, 05:18 AM