Brand systems
Names, marks and rules that stay usable after the launch week.
What we do
Five kinds of work. Each one starts with your content, not with a template.
How a project runs
Four steps, in this order, on every project.
We read before we draw
Every project starts with your existing pages, your analytics and your inbox.
We collect the questions your customers already ask. We count the pages nobody opens. We then cut the site to the pages that carry the work.
This step takes one week. It removes most of the guesses later.
One screen, one job
Each page answers a single question. The reader never hunts for the next step.
We design the small states first: the empty list, the error, the slow connection. A layout that survives those states survives the launch.
Type sizes, spacing and colour come from one token file. Your team can change the palette without a designer.
Static files, no server
The build writes plain HTML. A CDN serves it from the city nearest to the reader.
No database runs at night. No plugin asks for an update. The site costs almost nothing to host and stays fast under load.
When a page needs live data, one small function answers that request. The rest of the site stays static.
You own everything
The repository, the content and the domain stay in your accounts.
On the last day we walk your team through the editor and record the session. You get the video, the written guide and the commit history.
You can hire another studio next year. Nothing in the project locks you to us.
What you get
The list below is the contract, not a sales page.
Build
- Astro 5 with type-checked content
- Tailwind 4 tokens in one file
- GSAP and ScrollTrigger for reveals
- GSAP tag drop in the hero, no physics engine
- Swiper for every carousel
- Lighthouse above 95 on mobile
Content
- Markdown in Git, checked by a schema
- Sveltia CMS at /admin later
- A draft flag on every entry
Access
- Keyboard paths on every control
- Reduced motion respected
- Contrast tested against WCAG AA
Speed
- Zero JavaScript on static pages
- Scripts split per component
- Images served in modern formats
- Fonts preconnected and swapped
Care
- Two weeks of fixes after launch
- A written guide for your editors
- Dependency updates four times a year
Ways to start
Fixed scope, fixed price, fixed dates.
From 12,000
Rebuild
Your words and pictures move to a static site. The design stays close to the old one.
Ask for a dateFrom 6,000
One week audit
Speed, accessibility and content structure. You get a list of faults with a cost for each fix.
Book a week2,400
900
The workshop
We share one room above a bakery. Three desks, one plotter, and a wall of printed pages. Every project lives on that wall until it ships. Visitors are welcome on Thursday afternoons.
Read about usFrom the wall
Pictures from recent work and from the workshop.
Paper first
We print every layout before we code it.
See the method
Kiosk screens
240 stations, one interface, three taps.
Read the project
Harbour catalogue
Sixty books, two editors, no developer.
Read the project
Field archive
Thirty years of soil samples, now public.
Read the project
The wall
Every open project hangs here until it ships.
Visit on ThursdayJournal
Notes about the craft and the tools.
Contact
Tell us about the project. We answer in two working days.
Write two or three lines about the work, the date you need it, and the budget range. A rough range is enough. We reply with a plan, or with the name of a studio that fits better.
You can also come to the workshop on a Thursday afternoon.