docs: align machine-facing copy with the brand book positioning

[vihar]

Summary

• Rewrites both sites' llms.txt openings from the retired "open-source, modern project management software" definition to the canonical brand-book language ("Plane is agentic work infrastructure: …"), while keeping each site's role explicit — product docs vs developer docs.
• Adds a "When to use" section to each llms.txt: fit conditions on docs.plane.so, concrete developer jobs (REST API, MCP server, webhooks, OAuth apps, self-hosting) on developers.plane.so. Cross-links each site's llms.txt to the other.
• Completes the shared Organization JSON-LD (packages/theme/src/seo.ts) with legalName, the canonical company description, and the registered PostalAddress from Plane's Terms of Service — contactPoint + address is what agent-readiness audits check for organization completeness.
• Replaces "Modern project management software" / "extend your project management platform" in site, og, and twitter meta descriptions with purpose copy that doesn't redefine the company. Search keywords metas are unchanged (search-entry terms stay allowed per the brand book).
• Updates introduction/home.md (the docs site's "What is Plane" page and the first ToC link in llms.txt) to the canonical definition.

This mirrors the positioning already shipped in plane.so's llms.txt (makeplane/plane.so-marketing#954), so all three sites now describe Plane identically to machines. Out of scope: a full copy sweep of individual content pages.

Test plan

• pnpm check and pnpm build pass (verified locally)
• Built llms.txt on both sites opens with the canonical definition and renders the "When to use" section (verified locally)
• Organization JSON-LD in built HTML includes legalName, description, address, contactPoint (verified locally)
• After deploy: curl https://docs.plane.so/llms.txt | head -20 and same for developers.plane.so

Made with Cursor

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
developer-docs	Ready	Preview	Aug 22, 2026 11:56am
docs	Ready	Preview	Aug 22, 2026 11:56am

[coderabbitai]

Warning

Review limit reached

@vihar, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 43 minutes

Limit details: You’ve used the included review currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

How can I continue?

Wait for the limit to reset, then comment @coderabbitai review or push new commits to the PR.

An organization admin can change what happens after included review limits in Billing.

How do review limits work?

CodeRabbit enforces per-developer PR review limits within each organization.

For paid Pro and Pro+ reviews, CodeRabbit uses a developer's included PR review attempts over the past 7 days to set the current hourly allowance. At typical activity levels, the full plan allowance applies. Higher sustained activity can lower the allowance until earlier attempts leave the 7-day window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: c26057cf-1903-4530-9f29-451dc303ab72

📥 Commits

Reviewing files that changed from the base of the PR and between 95e92fe and d7a92b0.

📒 Files selected for processing (4)

• apps/developer-docs/docs/.vitepress/config.mts
• apps/docs/docs/.vitepress/config.ts
• apps/docs/docs/introduction/home.md
• packages/theme/src/seo.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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