Docs
Published · checked on 1 October 2026. This is the site you are reading. Publishing a page about a feature does not make the feature exist; most pages here describe proposals.
The docs site holds what the team has researched, decided and specified, the design prototypes — and, for now, the landing page. It is the only part of Store Deputy with a public address.
What it holds
| Section | What is in it |
|---|---|
| Concept | What the product is proposed to be, and the problem it addresses |
| Product | The first product, the authority contract, the implementation proposal, the bridge protocol and the roadmap |
| Architecture | This section: the parts and how they are built |
| User Flow | Clickable design prototypes of the module, sign-in and dashboard. They are designs, not the product |
| Market | Competitors, customer needs, business model and the evidence register |
| Decisions | The product proposal, the name and the open questions |
The home page is the landing page.
How it is arranged
- A static site. Pages are Markdown files built into plain HTML by VitePress. There is no server and no database, and the site never calls the API.
- Three languages. English is the source. Ukrainian and Russian mirror every page, with the same headings and the same link targets, so switching language keeps the reader's place.
- Scripted demonstrations. The landing page, the store demo and the account-flow preview are components inside the docs site. They make no network requests.
- One visual system, shared by the landing page and the documentation.
- Hosting. A static site on DigitalOcean App Platform, built from the repository's main branch. A change appears there only after it is committed and pushed.
Why CleanSlice does not apply
CleanSlice describes applications built with NestJS and Nuxt. The docs site is neither. It has no slices, no layers and no gateways, because it has no rules to protect and no data to fetch. Its content is organised by section and by language.
Rules that do apply
- Every claim has a status. Verified, built but not verified end to end, accepted direction, proposal or historical — and the status must be visible at a glance.
- Nothing invented. No measurements, customers, screenshots or successful runs that did not happen. Where proof is missing, the page says it is missing.
- Three languages change together. A check compares the three page trees, their heading anchors and every internal link after a build.
- A build before a claim. A page is not called working until the production build and the language check pass.