chore(marketing): say Paradev in marketing, email, and agent docs copy

Merged
KI
2d ago
+135-135

Summary

Part of the Superset → Paradev rename sweep. Slice: marketing, API/email, agent docs.

Most of this slice was already renamed: marketing page copy, apps/api strings (Slack manifest and agent messages), and email templates already say Paradev. This PR fixes what was left.

Changed (72 files)

  • apps/marketing/content (compare, category, about; 47 files): docs.superset.sh → docs.paradev.com, superset.sh → paradev.com, github.com/superset-sh/superset → github.com/paradevai/paradev. All target hosts return 200.
  • apps/marketing/public/cli/install.sh: header says "Paradev CLI", and the usage line uses paradev.com/cli/install.sh.
  • Theme marketplace page SEO keywords use COMPANY.NAME.
  • Roadmap PR link now points to paradevai/paradev.
  • packages/email/README.md: prose and marketing links.
  • AGENTS.md, apps/docs/AGENTS.md, apps/mobile/AGENTS.md: product name and the docs host.
  • .agents/commands (create-plan, create-pr, pr/create-pr, refresh-compare-pages, task, task-run) and .agents/skills (cdp-verification, incident-triage, mobile-demo-film wordmark default + example, mobile-demo-record, mobile-sim-verification, superset-settings, ticket-format): product name in prose.
  • .github: the issue template docs link, the "Bundled Paradev CLI" CI error text, the Homebrew formula homepage, and the canary release title "Paradev Desktop Canary". The release is found by its tag, not by this title.

Left on purpose

  • status.superset.sh in incident-triage: status.paradev.com redirects to status.superset.sh, so the status page has not moved.
  • relay/realtime/api.superset.sh health URLs, app.superset.sh in the bug report template: these are client hosts.
  • security@superset.sh and "Superset Inc." in content/legal/*, and "© Superset Inc." in the footer: legal.
  • JSON-LD sameAs entries for the old GitHub, X, LinkedIn, and YouTube identities: they are listed on purpose so search engines link the old and new names.
  • Media page item "Superset Mobile launches on iPhone" (Sep 21): it is a dated press item, so the old name stays. Change it if you want the current name there.
  • /compare/superset-vs-* slugs, /blog/superset-mobile, and .superset/* config paths: these are URLs and paths.
  • Superset CLI commands in demos, MCP server name superset, superset-* skill names, Superset.app / Superset.xcworkspace / -scheme Superset, Superset-*.dmg release files, the Homebrew class Superset formula, and the Vale style names: these are identifiers.
  • Blog posts and changelog entries: history.
  • WallOfLove tweets that quote @superset_sh: they quote real posts.
  • Code comments that only describe internals.

Validation

  • bun run lint:fix: passes.
  • apps/marketing bun test: passes.
  • lint:prose: 0 errors.
  • turbo typecheck --filter=@superset/marketing --filter=@superset/email: fails with 21 better-auth type errors. They are all in packages/auth and packages/trpc, which this PR does not touch, and they persist after a fresh bun install. I did not run the same check on main to confirm they are pre-existing.
  • check:i18n: not run, because no Lingui strings changed. check:plugins: not needed, because plugins/ is not touched.

No plugin publish and no tags are needed.

Summary by cubic

Completes the remaining Superset → Paradev renames in marketing, email, and agent-facing copy, so the public and agent-facing surfaces consistently use the Paradev name and hosts.

Changed

  • Marketing compare/category pages and the CLI installer now link to paradev.com, docs.paradev.com, and github.com/paradevai/paradev; all target hosts return 200.
  • Theme SEO keywords use COMPANY.NAME, the roadmap PR link points to paradevai/paradev, and the email README, AGENTS.md files, .agents commands and skills, issue template docs link, and workflow/Homebrew display names say Paradev.

Left on purpose

  • Status, API/app hosts, legal text, JSON-LD sameAs entries, dated press items, URL slugs, CLI commands, and identifiers stay as Superset, as do blog posts, changelog entries, quoted tweets, and internal code comments.

Lint and marketing tests pass; typecheck fails only on pre-existing better-auth errors in packages/auth and packages/trpc, which this PR does not touch.