Skip to content

feat(docs): add UX writing content guidelines#860

Draft
heatherbarranco wants to merge 2 commits into
UiPath:mainfrom
heatherbarranco:feat/docs-ux-writing
Draft

feat(docs): add UX writing content guidelines#860
heatherbarranco wants to merge 2 commits into
UiPath:mainfrom
heatherbarranco:feat/docs-ux-writing

Conversation

@heatherbarranco

Copy link
Copy Markdown
Contributor

Summary

  • Adds the content/UX writing section of the Apollo docs site
  • Covers terminology, capitalization & punctuation, voice & tone, inclusive writing, and writing for translation
  • Includes reviewed terminology definitions: updated Add, Create, Build, Run, and Job entries; Add-vs-Create tie-breaker; and Latin abbreviations guidance

Scoped from #766 — this PR covers the content/UX writing pages only.

Test plan

  • Pages render correctly in the docs site
  • Navigation links to the content section work
  • Verify Add/Create/Build/Run/Job definitions read correctly in the terminology table
  • Verify Latin abbreviations section appears under Capitalization & Punctuation

🤖 Generated with Claude Code

Adds terminology, capitalization & punctuation, voice & tone,
inclusive writing, and writing for translation pages.

Includes revisions: updated Add/Create/Build/Run/Job definitions,
added Add-vs-Create tie-breaker, and Latin abbreviations guidance.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Copilot AI review requested due to automatic review settings June 26, 2026 19:39
@heatherbarranco heatherbarranco marked this pull request as draft June 26, 2026 19:39

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Pull request overview

Adds a new Content / UX writing section to the Apollo docs site under apps/apollo-docs/app/content, providing guidance pages for terminology, voice/tone, inclusive writing, capitalization/punctuation, and writing for translation.

Changes:

  • Adds multiple new MDX pages under app/content/ covering UX writing guidelines.
  • Adds app/content/_meta.ts to define sidebar labels and ordering for the new section.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.

Show a summary per file
File Description
apps/apollo-docs/app/content/writing-for-translation/page.mdx New page with translation-focused writing guidelines.
apps/apollo-docs/app/content/voice-and-tone/page.mdx New page defining Apollo voice, tone, and style rules.
apps/apollo-docs/app/content/terminology/page.mdx New terminology definitions + component copy guidance.
apps/apollo-docs/app/content/inclusive-writing/page.mdx New inclusive writing guidance with examples and callouts.
apps/apollo-docs/app/content/capitalization-and-punctuation/page.mdx New capitalization/punctuation rules including Latin abbreviation guidance.
apps/apollo-docs/app/content/_meta.ts Defines the nav labels/order for the new content section.


# Writing for translation

Write content that translates clearly and accurately across languages. Some languages (e.g. German, Finnish) expand text by 20–30%, so short, literal phrasing is essential.

**Use:** aren't, can't, couldn't, didn't, doesn't, don't, hasn't, haven't, isn't, it's, let's, shouldn't, that's, there's, they're, they've, wasn't, we'll, we're, weren't, what's, where's, won't, you'll, you're, you've

**Avoid:** Regional contractions (ain't, y'all, twas) and overly formal alternatives (do not, cannot).
Comment on lines +1 to +7
export default {
'voice-and-tone': 'Voice and tone',
'capitalization-and-punctuation': 'Capitalization & punctuation',
'inclusive-writing': 'Inclusive writing',
'writing-for-translation': 'Writing for translation',
terminology: 'Terminology',
};
Comment on lines +1 to +7
export default {
'voice-and-tone': 'Voice and tone',
'capitalization-and-punctuation': 'Capitalization & punctuation',
'inclusive-writing': 'Inclusive writing',
'writing-for-translation': 'Writing for translation',
terminology: 'Terminology',
};
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.

2 participants