Web development
Websites that stay cheap to own.
Built around what the site needs to do, with editing, hosting and handover considered from the start. You keep the repository, content and accounts.
Two kinds of thing
We separate content sites from applications. A site made mostly of text, images and forms may not need a public application runtime or database. Accounts, calculations and live integrations usually do.
That decision comes before the stack. We avoid page-builder dependencies and design the repository, content and accounts so another developer can take over.
What we build
Marketing site
A focused site with an explicit performance budget and a browser editor built around your content.
Content site
A blog or documentation site with categories, authors and archives, where the content model is a schema rather than a convention.
Custom PHP application
Accounts, calculations and integrations need application logic. For those projects we use PHP 8 and selected Symfony components.
E-commerce
We build catalogues with checkouts, and assess whether an existing shop should be replaced or improved in place.
Performance and technical SEO
Structure, speed, schema and redirects on a site you already have. Often this is more useful than a rebuild.
Optional maintenance
Maintenance is available where the system needs it, with a scope you can cancel or hand to another developer.
The stack, and why
Astro for content sites, Tailwind for styling, Keystatic for editing and git for version history. PHP 8 with Symfony components where there is real application logic.
The value is not the list of tools. It is choosing a small, documented set that another developer can run and maintain.
Content with version history
Every committed change has an author and a date, alongside separate backups of repositories and assets.
No database where none is needed
Fewer moving parts means fewer services to host, update and secure.
Documented build
The repository includes the commands and configuration needed to install dependencies and produce the site.
| Question | Runtime CMS | Static publishing site |
|---|---|---|
| What serves a page? | Application code and usually a database | Files produced during a controlled build |
| Where does editing happen? | Inside the public application | In a separate editor connected to structured content |
| What needs routine updates? | The public runtime, CMS and extensions | Build dependencies and any separate form or search services |
| What does hosting require? | A supported application runtime and database | A static-capable host; dynamic features remain separate |
| What do you own? | Depends on the platform, theme and extensions | The repository, content, configuration and hosting account |
Questions we get
How long does a small site take?
Four to six weeks for something in the ten-to-fifty-page range, and most of that is content decisions rather than code. The build is rarely the slow part.
Who writes the content?
Usually you, with editorial feedback from us. We can also scope writing as part of the project when that is useful.
Where does it get hosted?
On a static-capable host for content sites, or an appropriately sized server for applications. You own the account either way.
What if you disappear?
You have the repository, the content, the accounts and the build instructions. A developer familiar with Astro or PHP can take over without moving the project first.
Can you work with our designer?
Yes. Share the design before implementation and we can identify costly or fragile interactions while they are still easy to change.
Send us the brief.
Or the URL of the thing that is annoying you. Either works.