Website

Draft built; runs on a developer's machine · 1 October 2026. One page in three languages. Not deployed, and no domain is chosen. Its selling copy has not been reviewed by the founder.

The website is the marketing site: what a shop owner reads before deciding to try Store Deputy. It is a different thing from this documentation, which is for the team, and it links to nothing here.

What exists today

• One page, built to sell. In the order a buyer decides: what it is, a demo, the chores it takes over, how to start, who stays in control, the usual questions, and where to join.
• A status the buyer can see. A badge in the first screen says the product is in development. The setup steps end with where things really stand, and the first question in the list is "Can I use it today?" — answered "Not yet".
• A scripted demo. Four everyday tasks play out in a sample admin with sample data. Its message box answers that it is a scripted preview with no store connected.
• One call to action. "Get early access" leads to registration in the app when the app has an address. A production build has no such address, so there every call to action leads to a block that says early access is not open yet.
• No waiting list. The site collects nothing: there is no form, because there is nowhere to send what it would collect.
• Three languages. English at the root, Ukrainian under /uk, Russian under /ru. The address decides the language.
• No accounts and no API calls. The website stores nothing about a visitor and never talks to the API.
• A local port. 4148 on a developer's machine. The command that starts the whole local workspace starts the website too.

The landing page that opens this documentation site is an internal concept demo. It is no longer the same page as the website and is not kept in step with it.

How it is arranged

website/slices/
  setup/
    theme/    Tailwind with the design tokens, and the local fonts
    i18n/     the three languages
    link/     the address of the app
  common/
    action/   the one call to action every section shares
    shell/    the page frame: header, language switch, footer
  marketing/
    home/     the home page sections and the scripted demo

Each slice is a Nuxt layer, picked up automatically, as in the app. The page itself is thin: it renders one provider component, which puts the sections together. The demo has its own provider, which plays the chosen scenario from start to finish and clears pending steps whenever the visitor switches or replays. Every sentence a visitor reads lives in the slice's translation files.

The site can be built into plain files — one page per language — and served from any static hosting.

What CleanSlice says

CleanSlice describes three parts — api/, app/ and an optional admin/. It does not describe a marketing website. The website is built with Nuxt, so the Nuxt rules are applied as they are in the app: all code in slices, each slice a Nuxt layer, setup slices first, a provider in every component group.

Where the draft differs, and why:

CleanSlice	Here	Why
Setup slices for state, the API client and error handling	None of the three	The website keeps no shared state and calls no API
UI components from shadcn-vue	Tailwind classes only	The page has buttons and native disclosure elements, and no forms, menus or tables of its own
Two plans agreed before any code	Built directly as a draft	The founder asked for a quick draft, then for a more selling one, on 1 October 2026; the review of it is still open

The sibling Agentfy repository builds its public website the same way — Nuxt, slices grouped as setup, common and marketing. That was the precedent used here.

To decide next

• The copy. The headline, the chores, the control commitments and the answers were written in one pass. Each claim describes how the product is being built; the founder has not confirmed them.
• Where early-access sign-ups go. Today the only real step is registering in the app. A waiting list needs a place to store addresses and a decision about who reads them.
• Price. The page says pricing has not been announced. See Business model.
• OpenCart versions. The page says OpenCart 3 from 3.0.3.5, with OpenCart 4 planned next. Only the first half is built.
• Domain, name and hosting. The collision with Deputy.com must be checked before a domain is bought; see The name. No hosting is chosen.
• The design guide. The website uses the accepted colours, type and shapes, with its own order of sections. The guide still describes the older landing composition.