We work to better the web for everyone, but much of what we do is invisible. People form opinions and feelings about things they can’t see based on things they can — including our words.
Being consistent with our words helps build trust. These guidelines help us ensure that what we write reflects the same thought and care we put into everything else we do at Faculty.
-
01
Usage and grammar
- Acronyms. Try not to use them. If you must, provide a definition when you first use one.
- Contractions. Use them whenever they won’t sacrifice clarity. They generally make copy sound more conversational.
- Em dashes. Format them with a space on each side — like this. To a browser’s line-breaker,
word—word is a single unbreakable token, which can force awkward overflow at narrow widths. Spaces give the line-breaker somewhere to wrap.
- En dashes. Use to denote a range, such as October 7–9.
- Jargon. Speak plainly and avoid jargon as much as possible.
- Numbers. Spell out numbers one through ten. Write higher numbers as digits. For example: use 13, not thirteen. Two exceptions: technical specifications take digits (“8 characters minimum,” not “eight characters minimum”), and related numbers share a format (“one was 8 and the other 13,” not “one was eight and the other 13”).
- Oxford or serial comma. Use it here, here, and here.
- Their. Use it as a gender-neutral possessive pronoun.
- They. Use it as a gender-neutral pronoun to refer to multiple people or just one. For example, “They rode their bike to lunch.” and “They rode their bikes to lunch.” are both correct. (It’s also good to use words like folks or y’all to address groups of people instead of using the gender-specific guys.)
- Your (not my) is the possessive pronoun we use to describe features or items that belong to a user.
-
02
Website guidelines
- Use sentence case for all headers and button copy.
- Use ampersands in headings when space is tight. Otherwise, just use the word and.
- Use title case only for titles (e.g., the title of a blog post or newsletter).
- Don’t use terminal punctuation in headers or titles, unless you need a question mark or exclamation point. And if the latter, you probably don’t. The exception: a header that runs to more than one sentence — where the punctuation between sentences forces the issue, and the final one should terminate too.
- Don’t link terminal punctuation.
- Ensure linked text describes the result of clicking the link. Ideally, linked text meant to prompt action appears at the end of a sentence, so the reader can take action as soon as they understand the task.
-
03
Word list
Adapted and extended from the O’Reilly Style Guide, our favorite reference for many years.
Cc
- caps lock
- caret
^
- checkbox
- checkmark
- check-in (a, n)
- check in (v)
- click-through (a)
- click through (v)
- client-side (a)
- client side (n)
- coauthor
- cofounder
- command
- command-line (a)
- command line (n)
- compile-time (a)
- compile time (n)
- control
- control + alt + delete
- control + n
- copyleft
- copyright
- copywriting
- coworker
- cross-reference
- CRLF
- CTA
Dd
- database
- data center
- data
Data is singular. If you think data are plural, we hope you also think spaghetti are delicious.
- decision-making (a)
- decision making (n)
- delete
Make sure you don’t mean backspace.
- DevOps
- DNS
- DOM
- dot-com (a, n)
- double click
- double quotes
- down arrow
- download
- drag-and-drop (a, n)
- drag and drop (v)
- dropdown menu
Ee
- e.g.
- ecommerce
- email
- end user (n)
- end-user (a)
- enter
- escape
- et al.
- ethernet
Gg
- G Suite
This is now called Google Workspace.
- gateway
- Gb (gigabit)
- GB (gigabyte)
- Gbps (gigabits per second)
- GHz (gigahertz)
- GIF or .gif
- Git or git
If referring to the actual command, use git, otherwise use Git.
- Google Workspace
- gray
When using American English, gray is how you spell the color. That’s why it’s called Castle Grayskull.
- grayscale
- greater-than sign or right angle bracket
>
- GUI, GUIs
Hh
- hardcoded
- hardcode (v)
- hash or pound sign
#
- high-level (a)
- home page
- hostname
- HTML
- HTTPS
- hypertext
Kk
- kb (kilobit)
- kB (kilobyte)
- kbps (kilobits per second)
- keepalive (a, n)
- keystroke
- keywords
Mm
- machine learning (n)
- machine-learning (a)
- man page
- Markdown
- markup
- Mb (megabit)
- MB (megabyte)
- Mbps (megabits per second)
- MHz (megahertz)
- menu bar
- metadata
- microservices
- mobile first (a)
Oo
- object-oriented programming
- okay
- offline
- onboard
- online
- open source (a, n)
- option
Pp
- password
- PDF
- %
In most cases, it is unnecessary and less clear to use the word percent.
- Perl
- PHP
- plain text (n)
- plain-text (a)
- plug in (v)
- plug-in (a, n)
- p.m.
- PNG
- pop up (n, v)
- pop-up (a)
- post-process
- private key (n)
- processor
In most cases, it is better to avoid jargon like CPU and speak plainly instead.
- public-key (a)
- public key (n)
- Python
Uu
- UK (United Kingdom)
- Unix
- uppercase
- up-to-date
- URLs
- US (United States)
- username
Ww
- web
- web client
- web page
- web server
- webhook
- website
- whitepaper
- whitespace
- WiFi
- wildcard
- wireframe
- workaround
- workstation
- wraparound
- writable
- write-only (a)
- WYSIWYG
Colophon
Style Guide is the third of three small guides on the virtual studio shelf, alongside Good Work and Best Practices.
Set in Mallory by Frere-Jones Type, with marginalia in Pitch Sans by Klim Type Foundry.