More than once, you've asked us where to find an explanation of a screen once you're outside the app — without having to write to us and ask the same thing you asked the week before. That's what these two pages fix.
What's visible now
A guide, at /guide: one page per app module — getting started, GPS tracking during an outing, your dogs, breeding, the training plan, traces and recaps, races and stages, gear, club and leaderboard, team, settings and subscription. Each page stays short and reads on its own, without the app open next to it.
An FAQ, at /faq: short questions, each one expandable, grouped by theme. It starts with GPS — what the indicator states mean while recording, the "Always allow" permission, the battery-optimization exemption on Android, an approximate position, resuming after a pause that feels slow, a short stop that wasn't detected. These are the questions that come up most often, which is why they open the FAQ.
The two are linked to each other — a guide page points to the FAQ question that completes it — and both are reachable from two places: the app's footer (visible even when you're logged out) and the main menu, next to Settings and Feedback.
What it doesn't do yet
French and English only. If your interface is set to Italian, Swedish, or Norwegian, the guide and the FAQ show in English — the same rule as this journal, which also exists in only two languages.
The FAQ covers GPS only, for now. The themes account and subscription, dogs and kennel, plan and sessions, data and backup already exist in the page's structure — you'll see their categories — but no question is written for them yet. That's not an oversight to fix in the next batch: those are empty shelves we'll fill in as we go, one theme at a time, rather than publishing ten rushed questions per theme just to tick a box.
Nothing in the app's own GPS error screens links to the FAQ yet. The link exists the other way — from the guide to the FAQ — but not yet from the mobile app itself to a specific question. That's coming later, not in this batch.
The choice we didn't make
This journal you're reading runs on a real database, with an admin screen where we write, preview, and publish every post with one click. That's actually what gave us the idea for the guide and the FAQ — you'd asked us for something similar for documentation.
We didn't build it the same way. The guide and the FAQ are Markdown files, managed like the rest of the code, with a single line — status: published or status: draft — deciding whether a page is live. No new table, no new admin screen.
The reason is simple: that admin screen doesn't exist for the guide and the FAQ, and building one would have been the heaviest piece of this whole batch for a benefit we weren't sure we wanted. A Markdown file gets corrected, reviewed, and published exactly like any other page on the site — which is what will let us keep it current without making every small fix depend on a new tool.