Style guide

Proudly Serving editorial and design guidelines.

Editorial

General

  • Follow 18F’s inclusive language style guide
  • Follow AP Stylebook
  • Write for a non-technical audience. If you need to use a technical term, define it.
  • Be concise
  • Avoid acronyms or jargon
  • Use the active voice instead of passive voice
  • Use descriptive links
  • Avoid using footnotes

Chapter

  • Overview
    • Brief description of topic
  • The problem
    • The problem and why it matters
  • The solution
    • The future when the problem is successfully solved
  • Context
    • Helpful background information
    • Examples
  • Mantras
    • Inspirational
    • Memorable
    • Concise
  • Checklist
    • Actionable steps
  • Questions to ask
    • Things people should ask themselves, their team, and their organization
  • Learn more
    • Links to specific articles, videos, tools fo the topic
    • Identify the type of resource in parentheses

Design

Close window