Structure before design
We start by working out what kinds of content you have and how many of each. That determines the post types, the fields and most of the build.
Designing first and discovering the content structure afterwards is how sites end up with fifteen service pages that all look different.
Four things we insist on
- Your accounts — domain, hosting and code in your name
- Authenticated mail, so forms actually deliver
- Plugin discipline — every one justified
- A handover guide, two pages, that someone will read
What we avoid
- Multipurpose themes with more features than any site needs
- Page builders on sites that matter commercially
- Plugins for things a few lines of code would do better
- Anything that makes leaving us difficult
How we communicate
A weekly note: what moved, what did not, what we need from you and whether the date has changed. Short, honest and on the same day each week.
You hear about a delay in the week it happens rather than at the deadline.
After launch
| Included | Duration |
|---|---|
| Small fixes as real use reveals them | First month |
| Redirect and form verification | Launch day |
| Training and handover guide | At launch |
| Maintenance arrangement | Optional, your choice |
We would rather be kept because the work is good than because leaving is difficult.