About This Site
This page explains the site itself: what it is, what it is not, and how to read it.
Two sites, one honest split
Section titled “Two sites, one honest split”The yoyopod repository carries two documentation sites, and the split is deliberate:
| Site | Accent | What it documents |
|---|---|---|
| the as-built engineering docs (in the repository) | coral (device tokens) | What is actually implemented today, code-verified, with honest gap ledgers. The engineering source of truth. |
| this site | amber & midnight (the brand kit) | yoyopod as a whole: what exists today, and the target experience the product is being built toward. |
Nothing on this site is a promise that a feature exists. When a vision page and an as-built page disagree, the as-built page wins.
Who this site is shaped for
Section titled “Who this site is shaped for”Three audiences, three entry paths from the landing page:
- Families — parents (the buyers) and kids 7–14 (the users): setup, everyday use, safety, and privacy, written for people who will never open a terminal.
- Builders — engineers and contributors: the hardware platform, the software platform, and the developer guide.
- Company — anyone who wants the why: mission, principles, anti-positioning, roadmap.
Two cross-cutting sections serve all three: User Stories (persona narratives that show what the product is for) and Applications (the experiences themselves: Listen, Talk, Locate, the Parent App, Setup).
Content status: how to read this site
Section titled “Content status: how to read this site”Every page is in one of two states, visible both in the sidebar badge and at the top of the page:
| State | Sidebar badge | Meaning |
|---|---|---|
| As-built | (no badge) | Condensed from real, as-built documentation. Ends with a Sources note. |
| Vision | Vision |
The target experience yoyopod is designed to deliver — design direction, not a description of today’s prototype. |
Sibling pages share a heading skeleton (all story pages have the same four headings, all app pages the same five, and so on) so the site reads consistently regardless of state.
Where the vocabulary comes from
Section titled “Where the vocabulary comes from”The structure is grounded in the repository’s real product language —
docs/product/ and the root README: “the first device before a smartphone”,
the V1 pillars (whitelist calls & voice messages, live-ish location,
music/audio, the parent app), the on-device screens (Hub, Listen, Talk,
Setup), and the anti-positioning list. Every page echoes that vocabulary so
this reads as yoyopod’s docs, not a generic template.