Foundations
Where the writing lives.
Product documentation is published per product, on that product's own surface. This page points at the material that belongs to the house rather than to one business.
Foundations
- Design systemThe type scale, the measured contrast pairs and the motion durations, with the reasoning kept beside each value.For anyone building an interface that has to sit next to ours.
- BrandThe mark, its three variants, how a product is named, and the clear space that keeps the lockup legible.For designers, and for anyone putting the name in front of other people.
Using the products
- Help centreTask-shaped articles, grouped by product. The situation first, then the steps, then nothing.For someone using a service today who needs it to do one specific thing.
- QuestionsShort answers to what comes up repeatedly, filed under the same categories the help centre uses.For a question that wants an answer rather than a procedure.
- ResourcesEvery written surface in one index, read from the same menu the navigation is built from.For when you know it has been written down but not where.
Operating
- Service healthWhether each service is up, what up is taken to mean, and where an incident is posted while it is open.For the person who needs to know now.
- Security policyWhere to send a vulnerability report, and what happens after it arrives.For researchers, and for anyone who reached something they should not have been able to reach.
- Terms of serviceWhat we commit to, what we ask in return, and how an agreement ends. Versioned, so what it said on the day you signed stays quotable.For whoever signs it, and whoever has to live with it afterwards.
- PrivacyWhat is held, why it is held, and how long it stays.For anyone who wants that settled before they sign up.
Not on this page
Documentation for a single business lives on the surface of the business it describes, not here. Each of the three keeps its own reference: what the service does, how it is configured, and what running it involves.
That split is deliberate. Documentation kept beside the thing it describes changes when the thing changes, whereas one index maintained on behalf of three teams goes stale quietly and is trusted anyway. Start from the product you are using.