Skip to content

product name: use "Estuary" instead of "Estuary Flow" - #3463

Open
jwhartley wants to merge 1 commit into
masterfrom
james/product-name-estuary
Open

product name: use "Estuary" instead of "Estuary Flow"#3463
jwhartley wants to merge 1 commit into
masterfrom
james/product-name-estuary

Conversation

@jwhartley

@jwhartley jwhartley commented Sep 4, 2026

Copy link
Copy Markdown
Contributor

The product is "Estuary", not "Estuary Flow" (context).

Two of these print in --help, via clap's #[command(about, ...)] on the flowctl and dekaf Cli structs. The rest are READMEs and comments, which agents read and imitate when drafting documentation.

Left alone as identifiers, not the product name: LICENSE-BSL, pyproject.toml, the estuary-flow-poc bucket in fixtures and seed.sql, and the estuary-flow-web tarball in CI.

Nothing under site/ is touched, since that tree is deprecated and estuary/docs is the live source. #2964 edits site/docs/getting-started/getting-started.md for the same rename and may want redirecting there.

Companion PR: estuary/connectors#5191

The product is "Estuary". Two of these strings are user-visible: the doc
comments on the flowctl and dekaf Cli structs are pulled into --help by
clap's #[command(about, ...)], so they print whenever a customer runs
`flowctl --help` or `dekaf --help`.

The rest are READMEs and comments. Those still matter, because agents read
them and reproduce the old name when drafting new documentation.

Not changed, since they are identifiers rather than the product name:
LICENSE-BSL ("Estuary Flow v1"), pyproject.toml (name = "estuary-flow"),
the estuary-flow-poc bucket in fixtures and seed.sql, and the
estuary-flow-web tarball in CI.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant