docs: name Defang Deploy where the copy defines the product

[defang-sam]

Part of a naming audit across website, portal and docs. Companions: defang-mvp#3265, DefangLabs/portal#1062.

The docs site now documents two products, so copy that defines "Defang" as a deployment tool is no longer accurate about the company. Fixed where the sentence is definitional, and only there.

What changed

Where	Change
intro.mdx	Page description, the lede sentence, and the "Learn more" card now say Defang Deploy. The <h1> stays "Defang Documentation" — this page is the site root and the site covers both products
how-it-works.mdx	"How Defang Deploy Works", the opening sentence, and the page description
faq/questions.md	The three comparison questions that define what the product is and is not: against run-time platforms, against Vercel/fly.io/Railway/Render/Heroku, and against SST
docusaurus.config.js	The two top-level navbar tabs are now Defang Deploy and Defang Station

In each passage only the first, defining mention changes. The rest of the paragraph stays bare, because by then the context has named the product — which is what the style guide asks for. Same reasoning for the Deploy dropdown's children (Overview, Tutorials, Concepts, Providers, CLI): they sit inside a tab that has just named the product.

What was deliberately left alone

There are 879 bare "Defang" in docs/. Almost all of them are correct.

• The CLI is still called Defang. Every defang command, install instruction and CLI reference keeps the name — it is in customer scripts, CI files and muscle memory.
• Inside the deploy product's own documentation, under a tab labelled for it, bare "Defang" is the established voice. Replacing it wholesale would make the prose unreadable and would not make anything clearer.
• Use-case recommendations of the form "Defang is a great choice for stateless web services" are suitability statements, not definitions. Out of scope by design.
• Blog posts are a published record. Back-dating them rewrites history rather than fixing copy; tracked separately.
• "Defang Portal" in docs/concepts/portal.md, workspaces.md, recipe.md and others — the console is being standardized on "Defang Deploy Portal" (portal#1062), and the docs pages should follow in a second pass once that name is merged and settled. Listed in the audit.

Full audit: SAM idea 01M2AYNX4JQTMC9VDXRHRBQNDE.

Verification

• docusaurus.config.js parses (node -e "require('./docusaurus.config.js')")
• Frontmatter intact on all three markdown files
• test-deploy build green on this PR

A local docusaurus build fails here for 90 paths — but identically on clean main, same path count. The prebuild step shells into ../defang/src/cmd/gendocs and needs Go, which this environment lacks. CI is green on main and runs the full prebuild, so I am relying on this PR's build rather than the local one.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Advanced

Run ID: ceacb2f7-4a39-4a3b-a579-c346470cdcb5

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

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