Skip to content

docs: Update the style guide with colon and Cloud console rules - #931

Merged
developerjamiu merged 1 commit into
mainfrom
docs/style-guide-colons
Nov 19, 2026
Merged

developerjamiu merged 1 commit into
mainfrom
docs/style-guide-colons

Conversation

@developerjamiu

Copy link
Copy Markdown
Contributor

Changes

  • Em dashes and colons (section 8): Em dashes are replaced with a comma, a parenthesis, a word that names the relation, or two sentences, not a colon. A colon that joins two clauses reads as machine-written, so colons are kept for bold lead-ins and for sentences that introduce a list, table, or code block. Two colons in the guide itself now follow the rule.
  • Serverpod Cloud console (new section 10): Docs explain what the screens can't show, locate a step in one line, document every capability, and add screenshots only where something is hard to find.
  • Voice examples (section 1): The first weak example no longer uses "ultimate", which is now part of the brand line.

@developerjamiu developerjamiu self-assigned this Nov 19, 2026

@SandPod SandPod left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@developerjamiu developerjamiu added the enhancement New feature or request label Nov 19, 2026
@developerjamiu
developerjamiu merged commit ae0398a into main Nov 19, 2026
7 checks passed
@developerjamiu
developerjamiu deleted the docs/style-guide-colons branch November 19, 2026 10:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants