Moped Documentation
  • Welcome 👋
  • User Guides
    • Getting started
    • Map a project
  • Product Management
    • User communication
    • User management
    • User analytics
    • Local testing
    • Release process
    • Patch release process
    • MUI X Pro License
    • Integrations
      • Dataset documentation
      • ArcGIS Online
      • eCapris
      • Power BI
    • Features
  • Dev Guides
    • DB Docs & Data dictionary
    • Database backup policy
    • Moped Read Replica
    • How-to's
      • How do I start the Hasura cluster locally?
      • How do I launch the Hasura Console?
      • How do I get a JWT token?
      • How to ping the GraphQL API
      • How to ping the REST API
      • How do I connect a database with Postgres GUIs?
      • How do I connect to the RDS instance?
      • How to load production data into a local instance
      • How do I update seed data?
    • Hasura
      • Hasura Roles
      • Hasura Migrations
        • Getting Started
        • Installing the Hasura CLI
        • Configuration Files
        • Hasura Migration Principles
        • The Migration file format
        • Development
        • Hasura Seed Data
        • Running the Hasura Cluster Locally (video)
        • Create a migration: Exercise 1 (video)
        • Create a migration: Exercise 2 (video)
        • Latest hasura-cluster features
    • User Management
    • Authentication
      • Authentication Architecture
      • DynamoDB & Cognito
      • Secrets Manager & Cognito
      • Hasura & Cognito
      • React & Cognito
      • Flask API & Cognito
      • Single Sign-On with CTM
    • Code organization
    • API
      • Configuration Files
      • Testing
      • User Management API
    • Maps and geospatial data
      • Access tokens and API keys
      • Map libraries
      • Map data
      • Map styles
      • Map layers and basemaps
      • React patterns
      • V1 Archive
        • Map libraries
        • Map data
        • Map custom hooks
        • Map styles
        • Map layers and basemaps
    • UI access control
    • Design system
      • Branding
      • Component styles
      • Text content
    • Activity Log
      • Architecture
      • GitHub Actions and Deployment of Updates
      • Hasura Event Logs and Truncate Cron Job
      • Authentication
  • See also
  • Get Moped support, report a bug, or request an enhancement
  • Data & Technology Services
  • Github repository
Powered by GitBook
On this page
  • Capitalization and acronyms
  • Acceptable acronyms
  • Language and tone

Was this helpful?

  1. Dev Guides
  2. Design system

Text content

PreviousComponent stylesNextActivity Log

Last updated 4 years ago

Was this helpful?

Much of this is pulled from , which can be generally considered a source for more extensive guidance.

Capitalization and acronyms

  • Use sentence case for all titles, headings, menu items, labels, and buttons. Proper nouns, like department names, are an exception.

  • Avoid acronyms wherever possible.

Yes

No

Start date

Start Date

Search by project name or project description

Search by Project Name or Project Description

Program manager

Program Manager

Active Transportation and Street Design

ATSD, Active transportation and street design

Acceptable acronyms

  • ATD project owner (a project role)

  • (definitely more; there are many cases where staff recognize an acronym more easily than the full name...)

Retain the Material UI default capitalization CSS styles. These often applytext-transform: uppercaseto text in buttons, tab titles, etc.

Language and tone

When possible, avoid gendered pronouns. If you can't, then "they" or "their" is preferable to "his or her" or "he or she".

  • Much yes: Ask your admin to add an additional user.

  • Yes: Ask your admin if they can add an additional user.

  • No: Ask your admin if he or she can add an additional user.

    .

Atlassian's style guide