diff --git a/.vale.ini b/.vale.ini index 8efd643b..fa97736f 100644 --- a/.vale.ini +++ b/.vale.ini @@ -30,3 +30,18 @@ Spacefast.Hype = NO Spacefast.Wordiness = NO Spacefast.Condescension = NO Spacefast.ApiKey = NO +Spacefast.Hosting = NO + +; Generated error pages are a verified snapshot synced from the monorepo, and +; the OpenAPI prose extraction reads generated/openapi. Both stay exempt from +; the "hosting" rule until the snapshot is refreshed with the monorepo fixes; +; then remove these carve-outs. +[content/(reference)/errors/**] +BasedOnStyles = Vale, Spacefast +Vale.Spelling = NO +Spacefast.Hosting = NO + +[*openapi-prose.md] +BasedOnStyles = Vale, Spacefast +Vale.Spelling = NO +Spacefast.Hosting = NO diff --git a/AGENTS.md b/AGENTS.md index dac7e55f..7f3cfb6b 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -89,8 +89,11 @@ alerts is the bar. rules, which mirror the vocabulary registry in the product monorepo (`packages/common/src/vocabulary.ts`): "API key" never "access token". The infra brand is "WP Cloud" (never dotted or hyphenated). Prefer "infra"; - name WP Cloud only when the external reference is necessary — never the - euphemism "the hosting provider". Marketing may use the family line "the + name WP Cloud only when the external reference is necessary. Never use the + word "hosting" in prose: say publish, serve, live, infrastructure, or + runtime (`Hosting.yml`). Generated error pages, OpenAPI prose, and the + shipped changelog are exempt until the generated snapshot is refreshed. + Marketing may use the family line "the same infra as Automattic, WP Cloud, Pressable, and WordPress.com". - Unknown technical words go in `styles/Spacefast/spelling-exceptions.txt` (sorted, case matters for proper nouns). Identifiers in prose — commands, diff --git a/STYLE_GUIDE.md b/STYLE_GUIDE.md index dd2fa3b5..2d9f9642 100644 --- a/STYLE_GUIDE.md +++ b/STYLE_GUIDE.md @@ -211,9 +211,9 @@ that is. (`ProductName.yml`). - **WP Cloud** — exact casing, never "wp cloud," "wp.cloud," or hyphenated (`WpCloudBrand.yml`). Prefer "infra" generally; name WP Cloud only when - the external reference is genuinely necessary. Never say "the hosting - provider" for Spacefast's own infra (`HostingProvider.yml`) — generic - references to *other* hosting providers are fine. + the external reference is genuinely necessary. Never use the word + "hosting" for Spacefast or its features (`Hosting.yml`). Say publish, + serve, live, infrastructure, or runtime. - **"API key," never "access token"** (`ApiKey.yml`) — "OAuth access token" is the one exempted phrase, since that's the protocol's own term. diff --git a/content/(serve)/domains.mdx b/content/(serve)/domains.mdx index f6875d29..deafb08c 100644 --- a/content/(serve)/domains.mdx +++ b/content/(serve)/domains.mdx @@ -237,7 +237,7 @@ www.example.com purpose=www dns=not_configured txt=missing ssl=missing ### Checking before you commit -`GET /v1/domains/preflight?name=example.com` runs the same name validation and hosting check as the add, so terminal problems surface before any record exists. Its `canHost` verdict is advisory. A `false` still lets you add the domain and claim it with the TXT proof, and `null` means the check was unavailable rather than negative. +`GET /v1/domains/preflight?name=example.com` runs the same name validation and serving check as the add, so terminal problems surface before any record exists. Its `canHost` verdict is advisory. A `false` still lets you add the domain and claim it with the TXT proof, and `null` means the check was unavailable rather than negative. ## Next steps diff --git a/content/api/errors.mdx b/content/api/errors.mdx index 90ced264..ad958d7b 100644 --- a/content/api/errors.mdx +++ b/content/api/errors.mdx @@ -180,8 +180,8 @@ Two retry rules that come from the wire rather than the table. A `429` carries ` | `internal_error` | retry | yes | Something went wrong on our side. | | `maintenance_in_progress` | wait | yes | This change is temporarily unavailable while maintenance finishes. | | `provider_error` | retry | yes | Spacefast could not complete the operation. | -| `provider_job_failed` | retry | yes | A hosting-provider job failed while processing this operation. | -| `provider_job_timeout` | retry | yes | A hosting-provider job timed out while processing this operation. | +| `provider_job_failed` | retry | yes | A provider job failed while processing this operation. | +| `provider_job_timeout` | retry | yes | A provider job timed out while processing this operation. | | `space_disabled` | fix_input | no | The space is disabled and cannot be served or modified. | ## Every error code diff --git a/content/platforms/partner-api/configuration.mdx b/content/platforms/partner-api/configuration.mdx index 9b5904c0..c804534a 100644 --- a/content/platforms/partner-api/configuration.mdx +++ b/content/platforms/partner-api/configuration.mdx @@ -27,7 +27,7 @@ Add a `system` block to the system Space's `sf.jsonc`. Keep the other project se { "system": { "presentation": { - "name": "Example Hosting", + "name": "Example Cloud", "logo": "https://example.com/logo.png", "supportUrl": "https://example.com/support", "claimOrigin": "https://portal.example.com", diff --git a/styles/Spacefast/Hosting.yml b/styles/Spacefast/Hosting.yml new file mode 100644 index 00000000..b98cf614 --- /dev/null +++ b/styles/Spacefast/Hosting.yml @@ -0,0 +1,11 @@ +# Ruling 2026-11-11: never define or describe Spacefast with the word +# "hosting". Say publish, serve, live, infrastructure, or runtime instead. +# Narrow uses about something else (a third-party product) are rare; rephrase +# first, and only suppress a line with an inline Vale comment when it is truly +# about something other than Spacefast. +extends: existence +message: "Don't use '%s' to describe Spacefast. Say publish, serve, live, infrastructure, or runtime." +level: error +ignorecase: true +tokens: + - hosting diff --git a/styles/Spacefast/HostingProvider.yml b/styles/Spacefast/HostingProvider.yml deleted file mode 100644 index d556a160..00000000 --- a/styles/Spacefast/HostingProvider.yml +++ /dev/null @@ -1,10 +0,0 @@ -# Ruling 2026-08-13: never the euphemism "the hosting provider" for our own -# infra. Either drop the external reference, or — when it is genuinely -# necessary — name WP Cloud. Generic third-party mentions ("other hosting -# providers", "another hosting provider") are fine and don't match. -extends: existence -message: "Don't say '%s' for our infra. Drop the reference, or name WP Cloud when the external reference is necessary." -level: error -ignorecase: true -tokens: - - the hosting provider