All

This is d2pro, the pro demo: a small online shop that sells coffee gear, built on d2. Everything here is made up and resets on every update, so try anything.

The specification of d2pro: what it's for, its parts, and what's decided

The components of d2pro: its functional areas, what each is for and what it uses

The design of d2pro: the mechanisms that realise its specification, for any code base

The API of d2pro as designed: conventions and the routes each feature uses

A flow is what d2 does when something happens: a message comes in, the rules that handle it run, one statement after another, and each can send more messages. The shop's

The pro demo: a small online shop that sells coffee gear, with its model, sample data and flows. It's a wiki topic, Home, like every project's start page: change it any t

This is a project on d2: a notebook and an app in one, built with an AI.

The project log of d2pro: changes and decisions by the people on it, dated

How Prototype 1 (a d2 prototype) met the design of d2pro, per feature

this project's own way of working, on top of d2's skills; read after them. Its person and its AIs keep it.

A small online shop, Grindstone Coffee Gear, as a domain model: what it sells, who buys, their orders, and how orders get to them. Its sample data is in shop-samples; wha

Two flows about carts. A new cart tells the shop who's shopping. Abandoned carts runs once a day (a cron, declared in Init): any cart still open after 48 hours is marked

Every message the shop sends goes through this one rule. Here it keeps the message in the shop's outbox (a Message object, see shop), so the demo shows what would go out

Order placed. When an order is created, the shop issues its invoice, reserves the stock for each line (from the first warehouse that has enough), checks whether that left

Shipped. When a shipment's status becomes shipped, its order is marked shipped and the customer gets the tracking number.

Low stock. When a stock level drops below its reorder point, whoever runs the shop hears about it, with the supplier to call and how long they take to deliver. It runs wh

The black-box tests of d2pro: at least one per spec line, each run as a person

The UI specification of d2pro: how its UI behaves — screen flows, layouts, what each page shows

Each shop flow, run by hand on the sample data (in the [Fiddle](/fiddle?tab=stories&topic=Story:shop-flows), nothing is kept). The triggers in Init start the same flows w

Sample objects for shop: Grindstone Coffee Gear, a made-up shop with 12 products, 6 customers, carts, orders in each status, two warehouses and a return. Each $object Cla

Open items for d2pro