Simpler.Grants.gov Public Wiki
Grants.govSimpler.Grants.govGitHubDiscourse
  • πŸ‘‹Welcome
  • GET INVOLVED
    • Why open source?
    • How to contribute code
    • How to file issues
      • Report a bug
      • Request a feature
      • Report a security vulnerability
    • Community guidelines
      • Code of Conduct
      • Reporting and removing content
      • Incident response protocol
    • Community events
      • Fall 2024 Coding Challenge
        • Event Submissions & Winners
      • Spring 2025 Collaborative Coding Challenge
        • Event Submissions & Winners
    • Communication channels
  • Product
    • Roadmap
    • Deliverables
      • 🏁Static site soft launch
      • 🏁Static site public launch
      • 🏁GET Opportunities
      • 🏁Open source onboarding
      • 🏁Co-Design Group planning
    • Decisions
      • ADR Template
      • ADRs
        • Dedicated Forum for Simpler.Grants.gov Community
        • Recording Architecture Decisions
        • Task Runner for the CI / CD Pipeline
        • API Language
        • Use Figma for design prototyping
        • ADR: Chat
        • DB Choices
        • API Framework and Libraries
        • Back-end Code Quality Tools
        • Front-end Language
        • Communications Tooling: Wiki Platform
        • Use Mural for design diagrams and whiteboarding
        • Ticket Tracking
        • Front-end Framework
        • Front-end Code Quality Tools
        • Front-end Testing & Coverage
        • Backend API Type
        • Front-end Testing & Coverage
        • Deployment Strategy
        • Use U.S. Web Design System for components and utility classes
        • FE server rendering
        • Use NPM over Yarn Architectural Decision Records
        • U.S. Web Design System in React
        • Communications Tooling: Video Conferencing
        • Back-end Production Server
        • Communications Tooling: Analytics Platform
        • Commit and Branch Conventions and Release Workflow
        • Cloud Platform to Host the Project
        • Infrastructure as Code Tool
        • Data Replication Strategy & Tool
        • HHS Communications Site
        • Communications Tooling: Email Marketing
        • Communications Tooling: Listserv
        • Use Ethnio for design research
        • Uptime Monitoring
        • Database Migrations
        • 30k ft deliverable reporting strategy
        • Public measurement dashboard architecture
        • Method and technology for "Contact Us" CTA
        • E2E / Integration Testing Framework
        • Logging and Monitoring Platform
        • Dashboard Data Storage
        • Dashboard Data Tool
        • Search Engine
        • Document Storage
        • Document Sharing
        • Internal Wiki ADR
        • Shared Team Calendar Platform
        • Cross-Program Team Health Survey Tool
        • Adding Slack Users to SimplerGrants Slack Workspace
        • Repo organization
        • Internal knowledge management
        • Migrate Existing API Consumers
      • Infra
        • Use markdown architectural decision records
        • CI/CD interface
        • Use custom implementation of GitHub OIDC
        • Manage ECR in prod account module
        • Separate terraform backend configs into separate config files
        • Database module design
        • Provision database users with serverless function
        • Database migration architecture
        • Consolidate infra config from tfvars files into config module
        • Environment use cases
        • Production networking long term state
    • Analytics
      • Open source community metrics
      • API metrics
  • DESIGN & RESEARCH
    • Brand guidelines
      • Logo
      • Colors
      • Grid and composition
      • Typography
      • Iconography
      • Photos and illustrations
    • Content guidelines
      • Voice and tone
      • Editoral style
      • Terminology usage
    • User research
      • Grants.gov archetypes
  • REFERENCES
    • Glossary
  • How to edit the wiki
Powered by GitBook
On this page
  • External style guides
  • Editorial perspective
  • Mechanics
  • Contractions
  • Capitalization
  • Coming soon
  • Punctuation
  • Abbreviations
  • Number formatting

Was this helpful?

Edit on GitHub
  1. DESIGN & RESEARCH
  2. Content guidelines

Editoral style

This page outlines the rules and recommendations for grammar, punctuation, word choice, and formatting to ensure clear, consistent, and on-brand content.

PreviousVoice and toneNextTerminology usage

Last updated 2 days ago

Was this helpful?

External style guides

We follow a few trusted external style resources to ensure our content is clear, consistent, and user-centered:

  • : Our primary reference, which adopts AP style with specific exceptions tailored to federal websites.

  • : We follow USWDS guidance for content within design components, such as using sentence case for buttons and form elements.

  • : These federal plain language guidelines serve as our foundation for writing in a way that’s clear, concise, and accessible to all users.

Editorial perspective

Consistent use of pronouns is key to creating a clear and cohesive editorial perspective. Switching between first-person ("my account") and second-person ("your account") can confuse users and disrupt the flow of communication. We use the second person (e.g., "your account") throughout the product to maintain a consistent, user-focused voice. This approach reinforces clarity, reduces ambiguity, and aligns with how most users think about interacting with a product from their perspective.

Mechanics

Contractions

Using contractions (like we're', it's' or you'll) helps our writing sound more natural, approachable, and human, just like how people speak in everyday conversation. They soften overly formal language, making our content feel more friendly and accessible, especially in user-facing experiences. By using contractions, we create a tone that’s warm, relatable, and easier to connect with.

Capitalization

Simpler.Grants.gov uses sentence case in most cases. Sentence case makes content easier to scan and digest, especially in long text. It also aligns with how many people naturally speak and write, making it feel more conversational. In contrast, excessive use of title case can engender formality, making our product look stiff and unwelcoming. Sentence case examples

  • H2 and lower

  • Column headers

  • Labels and other UI components

  • Progress indicator labels

  • Modal titles

  • Buttons (per )

Title case examples

  • Page titles

  • H1 headings

  • The subject line for Simpler.Grants.gov newsletters

    • It follows a format where "[Month] Updates" uses title case, while the latter portion after the pipe symbol uses sentence case. Example: "May Updates | Building momentum with every release"

Uppercase examples

  • Opportunity statuses. Examples: CLOSING, OPEN.

Coming soon

Punctuation

Abbreviations

Number formatting

HHS Web Style Guide
U.S. Web Design System (USWDS)
PlainLanguage.gov
USWDS