Ten plates for pages, files, offers, desks, and provider calls
Each plate is one job. The design band settles the opening line and the control before a palette is opened. The build band puts the booking action first in the file, then keeps a part from rewriting the page. The offer band writes one sentence and keeps that sentence on the page, in the email, and on the card. The desk band asks whether a coworker can run the week without a tour. The connection band agrees a listing noun, orders the calls, and stores a session as a clock.
Web design
Open Web design →
Layout decisions to make before colorSet the opening line, the reading length, and the gap around the booking control before any palette is opened on the page.
Designing every state of a controlDraw ready, hover, focus, pressed, disabled, and failure together, and include the empty screen that sits around the control.
Web development
Open Web development →
Build the page in the order people meet itWrite the HTML in the order a person should meet it. Place it with CSS, and add script only after the page already works.
Keep a component inside its boundaryA reusable part takes named inputs and emits named outcomes. The page passes values between parts. The part does not edit the page.
Digital marketing
Open Digital marketing →
Write an offer a stranger can repeatPut who it is for, what they can do, and where everyone else goes into one sentence, then give that sentence one next action.
Use one message on the page, in the email, and in the announcementRepeat the same offer on the page, in the email, and on the announcement. Change the room each place has. Keep the sentence.
Software
Open Software →Integrations
Open Integrations →
How multi-provider API integrations workAgree on one listing noun, match a stable identifier, and map each new provider into that noun instead of inventing a second shape.
API orchestration for a B2B platformOrder provider calls so a withdrawn listing cannot publish, record a failed write, and test the timetable with a stand-in.
Session architecture for a multi-provider platformStore a session as a start, an idle limit, an end, and the provider and title ids. Leave the title’s own rules with the provider.
