ProcessWire websites

What you get

• A structure built around your data, not the other way round. Doctors, products, properties, courses — each type becomes a page with its own fields and links.
• An admin people learn in an hour. An editor sees only the fields they need. Your staff add content themselves, without a programmer.
• Speed as the norm. The static cache serves ready-made HTML, and PageSpeed above 90 on mobile is a condition of handover, not a bonus.
• Multilingual out of the box. A second, third and fourth language are fields side by side, not a copy of the site.
• The code and the data are yours. Open source, plain PHP and MySQL, documentation. Any developer can carry on without us.

How it goes

1. A conversation and an estimate. An hour’s talk about the task, the audience and what already exists. Within 2–3 days, a written estimate broken into stages.
2. Structure and prototype. Sitemap, page types, fields. An HTML prototype of the key pages, on real content.
3. Design. Typography, grid, states. The mobile version is designed together with the desktop one.
4. Development and import. Templates, fields, a scripted import of the content from the old system. Redirects from the old addresses.
5. Launch and training. The move to production hosting, a check of PageSpeed and Schema.org, and an hour of recorded training for editors.

When we are not the right fit

• You need an ordinary site on a site builder within a week — Tilda will do it, and that is fine.
• You need a marketplace with thousands of sellers — that is a different class of task and a different team.

We name the timeline and the cost after the first conversation: they depend on the amount of content and on what already exists. The estimate is in writing, and it has no “just in case” lines.