How this help centre works

Two things about this help centre are unusual enough to be worth explaining.

We document what the app does, not what it is meant to do

Several articles here say plainly that a feature is missing, half-built, or advertised somewhere else in the product but not actually available. The data export button. The notification toggles. The referrals section.

That is deliberate. A help centre that describes the intended product rather than the shipped one is worse than no help centre, because it sends you looking for a control that is not there and leaves you assuming you are the problem.

So where there is a gap, the article says so, says what happens instead, and gives you a way to get the outcome by hand. Those articles are collected on the known gaps page.

These live next to the code

Help articles are written in the same repository as the application and ship with it. That is not an implementation detail you should have to care about, except for one consequence: when a button gets renamed, the article describing it changes in the same edit. It is the cheapest way we know to stop documentation drifting into fiction.

Every article carries the date it was last checked.

What we will not write

We will not describe a feature that does not exist yet, however close it is. If it is not in the product, it is either absent from here or explicitly marked as absent.

We will not give ship dates. Nothing here says "coming soon" with a month attached, because a missed date is worse than no date.

We will not pad. If the answer is one paragraph, the article is one paragraph.

If an article is wrong

Tell us. There is a "was this helpful?" control at the end of every article, and saying no gives you a box to say why. That goes to the same place as a support message and a person reads it.

If an article contradicts the app, the app is right and the article is a bug. Those get fixed quickly.