Last week the practice turned its care inward and took a tool of its own from an empty repository to a working set of services. A working core, though, is a private thing — a calculator that no one can yet reach. This week it was given the surface a person actually touches, and the means to be passed on: thirteen of the eighteen items closed belonged to that single, deliberate effort.
The bulk of it was the visual design system and layout shell — the part that must be built to be seen before it can be used. A full set of design tokens went in first, in both dark and light, so that every colour, space and type-step is named once and used everywhere rather than guessed at twice. On that footing: the typographic foundations, subsetted down to only the glyphs the tool needs so the first paint stays light; a boot skeleton inlined into the page, so there is something composed to look at in the moment before the application itself arrives; the layout shell proper — navigation, content and footer; and the core primitives a person handles directly, the buttons and form inputs, built once and held consistent across the whole.
Beneath the surface went the wiring that makes a collection of parts feel like one thing. A single application-state service, provided where it is needed rather than reached for from anywhere; the routing that gives the tool addressable places; and — the piece with the happiest consequence — a serialiser that keeps the tool's working state in the address itself. An expression worked out here becomes a link, and a small copy-the-link control hands it over: paste it to a colleague and they arrive at exactly what you were looking at. State you can drop into a chat window is a quiet luxury, and it was worth the careful afternoon it took.
And then the keeping-honest work that earns none of the applause. An end-to-end browser test harness was stood up, with its first specifications driving the copy-and-share path through a real browser rather than trusting it by eye. Beside it, a continuous-integration annoyance was tracked down and put right: merges to the main branch were being cancelled mid-flight by an over-eager rule meant only to tidy away superseded runs — a small misconfiguration, and exactly the sort that quietly undermines the one pipeline you most need to trust.
— On the surface —A working core is a thing you can admire alone. A face is where it begins to be of use to anyone else.
Outward, one thread that has run for a fortnight was brought to a close. The clinical canine massage practice's contact pipeline — held deliberately in flight last week as a stub — was proven end-to-end and switched to the real thing: the production credential for a third-party transactional-email provider placed in the cloud host, the live mail path walked through from the preview environment before it was trusted with a real enquiry, and a bot-protection check set on the form so the new path is a way in for people and not for spam. The practice's mail and DNS phase is done; the site now turns toward its launch.
The smaller stewardship was kept, as it always is. For a local dog-training club, a venue-booking account was set up for its treasurer — not code at all, simply the kind of practical hand a small, volunteer-run organisation needs and rarely has. And for the retained veterinary practice, another clear-down of accumulated contact-form entries: recurring, unglamorous data hygiene that keeps a modest site in good health and holds no more than it should.
Looking ahead: the internal tool turns from its surface toward release — the pre-launch checks that decide when a thing is fit to be seen, and the distance between a working interface and a finished one; the canine massage practice's site moves on from a proven pipeline toward going live; the practice's own website waits on its final pre-launch verification; and the retained clients go on being kept, as they always are.
Eighteen items to Done across four projects — thirteen of them a tool of our own, carried this week from a working core to a face that can be used and a result that can be shared. One client thread closed, the smaller work quietly kept. The same deliberate, unhurried practice, still turned inward — but beginning, now, to look outward again.