From 6240c15b8548297433c94a9d60d56c8564fbfad6 Mon Sep 17 00:00:00 2001 From: Prakash Sundaresan Date: Sat, 12 Sep 2026 18:08:30 +0000 Subject: [PATCH] docs: name Defang Deploy where the copy defines the product Part of a naming audit across website, portal and docs. 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. Landing page: the h1 stays 'Defang Documentation', because this page is the site root and the site covers both products. The sentence under it described only the deploy product, so it and the page description now say Defang Deploy, as does the card that links to the overview. How it Works: the heading and the opening sentence. The rest of that paragraph stays bare, since by then the context has named the product. FAQ: the three comparison questions that define what the product is and is not, against run-time platforms, against Vercel and Heroku, and against SST. Navbar: the two top-level product tabs are now Defang Deploy and Defang Station. Their children (Overview, Tutorials, Concepts, Providers, CLI) stay as they are, since they sit inside a tab that has named the product. Left alone on purpose. There are 879 bare 'Defang' in docs and almost all are correct: the CLI is still called Defang and every 'defang' command, install instruction and CLI reference keeps the name. Inside the deploy product's own documentation, under a tab labelled for it, bare 'Defang' is the established voice, and replacing it wholesale would make the prose unreadable. Use-case recommendations of the form 'Defang is a great choice for X' are suitability statements rather than definitions and were not touched. Blog posts are a published record and are tracked separately. Local fails here for 90 paths, but identically on clean main with the same count, because the prebuild step shells into ../defang gendocs and needs Go, which this environment lacks. CI is green on main and runs the full prebuild. Co-Authored-By: Claude Opus 5 --- docs/intro/faq/questions.md | 12 ++++++------ docs/intro/how-it-works.mdx | 6 +++--- docs/intro/intro.mdx | 8 ++++---- docusaurus.config.js | 4 ++-- 4 files changed, 15 insertions(+), 15 deletions(-) diff --git a/docs/intro/faq/questions.md b/docs/intro/faq/questions.md index 4624733e7..5cc143d26 100644 --- a/docs/intro/faq/questions.md +++ b/docs/intro/faq/questions.md @@ -65,14 +65,14 @@ import {Button, ButtonGroup, FormGroup, FormLabel} from "@mui/material" ## Feature Comparisons -### Is Defang a run-time platform? -- No. Defang is not a run-time platform. Instead, it lets you host and run your application on a [cloud provider](/docs/providers) of your choice. You can think of it as a tool that makes it way easier to deploy to that cloud provider. +### Is Defang Deploy a run-time platform? +- No. Defang Deploy is not a run-time platform. Instead, it lets you host and run your application on a [cloud provider](/docs/providers) of your choice. You can think of it as a tool that makes it way easier to deploy to that cloud provider. -### What is the difference between Defang and platforms such as Vercel, fly.io, Railway, Render, or Heroku? -- Defang is a tool that helps you get your application deployed to a [cloud provider](/docs/providers) of your choice, and it is not a platform. Unlike platforms, Defang does not host your application. +### What is the difference between Defang Deploy and platforms such as Vercel, fly.io, Railway, Render, or Heroku? +- Defang Deploy is a tool that helps you get your application deployed to a [cloud provider](/docs/providers) of your choice, and it is not a platform. Unlike platforms, Defang does not host your application. -### What is the difference between Defang and tools such as SST? -- Defang is cloud-agnostic and language-agnostic, meaning that it is designed to work with different [cloud providers](/docs/providers), and programming languages. Since Defang is not tied to just one cloud or language, this allows for greater flexibility in a wide range of cases. Another difference is that Defang follows the [Compose specification](https://docs.docker.com/compose/compose-file/), allowing it to work smoothly with various container platforms such as Docker. +### What is the difference between Defang Deploy and tools such as SST? +- Defang Deploy is cloud-agnostic and language-agnostic, meaning that it is designed to work with different [cloud providers](/docs/providers), and programming languages. Since Defang is not tied to just one cloud or language, this allows for greater flexibility in a wide range of cases. Another difference is that Defang follows the [Compose specification](https://docs.docker.com/compose/compose-file/), allowing it to work smoothly with various container platforms such as Docker. ## Troubleshooting diff --git a/docs/intro/how-it-works.mdx b/docs/intro/how-it-works.mdx index 0f8415324..227ed74fe 100644 --- a/docs/intro/how-it-works.mdx +++ b/docs/intro/how-it-works.mdx @@ -1,12 +1,12 @@ --- sidebar_position: 250 title: How it Works -description: Overview of the Defang architecture and how it works in your cloud +description: Overview of the Defang Deploy architecture and how it works in your cloud --- -# How Defang Works +# How Defang Deploy Works -Defang is an AI-assisted tool that lets you take your app from Docker Compose to a secure and scalable deployment on your favorite cloud in minutes. Defang abstracts away the complexity of cloud infrastructure, providing you with a streamlined experience. Defang works by provisioning a "CD" task and a small set of resources in your cloud account. These enable Defang to orchestrate deployments for you in your cloud account from the `defang` CLI. Here's how it works. +Defang Deploy is an AI-assisted tool that lets you take your app from Docker Compose to a secure and scalable deployment on your favorite cloud in minutes. Defang abstracts away the complexity of cloud infrastructure, providing you with a streamlined experience. Defang works by provisioning a "CD" task and a small set of resources in your cloud account. These enable Defang to orchestrate deployments for you in your cloud account from the `defang` CLI. Here's how it works. ## Bootstrapping diff --git a/docs/intro/intro.mdx b/docs/intro/intro.mdx index de5f70bb2..a18a8e3a6 100644 --- a/docs/intro/intro.mdx +++ b/docs/intro/intro.mdx @@ -1,7 +1,7 @@ --- sidebar_position: 100 title: Overview -description: Overview of Defang, an AI-assisted tool that lets you take your app from Docker Compose to a secure and scalable deployment on your favorite cloud in minutes. +description: Overview of Defang Deploy, an AI-assisted tool that lets you take your app from Docker Compose to a secure and scalable deployment on your favorite cloud in minutes. --- import DocCardList from "@docusaurus/theme-classic/lib/theme/DocCardList"; @@ -12,7 +12,7 @@ import DocCardList from "@docusaurus/theme-classic/lib/theme/DocCardList"; Defang Logo

Defang Documentation

- Defang lets you take your app from Docker Compose to a secure and scalable deployment on your favorite cloud in minutes. Build cloud applications in any language and stack, deploy to your account on your favorite cloud with a single command, and iterate quickly with AI-assisted tooling. + Defang Deploy lets you take your app from Docker Compose to a secure and scalable deployment on your favorite cloud in minutes. Build cloud applications in any language and stack, deploy to your account on your favorite cloud with a single command, and iterate quickly with AI-assisted tooling.

Getting Started

@@ -21,8 +21,8 @@ import DocCardList from "@docusaurus/theme-classic/lib/theme/DocCardList"; { type: "link", href: "/docs/intro/what-is-defang", - label: "Learn more about Defang", - description: "What is Defang and how does it work?", + label: "Learn more about Defang Deploy", + description: "What is Defang Deploy and how does it work?", }, { type: "link", diff --git a/docusaurus.config.js b/docusaurus.config.js index 40b7fa6f6..36ee6a317 100644 --- a/docusaurus.config.js +++ b/docusaurus.config.js @@ -81,7 +81,7 @@ const config = { // sections that were previously top-level, so no redirects are needed. { type: "dropdown", - label: "Deploy", + label: "Defang Deploy", position: "left", items: [ { @@ -113,7 +113,7 @@ const config = { { type: "docSidebar", sidebarId: "stationSidebar", - label: "Station", + label: "Defang Station", position: "left", }, { to: "https://defang.io/blog", label: "Blog", position: "left" },