Web design · WordPress
WordPress for teamswho publish.
Templates, a short plugin list, and editors who can ship a page without opening a ticket.
The short answer
When WordPress is the build.
WordPress is the right build when several people publish and the pages are not one layout repeated. Locations, services, staff, and articles can share a design and still be different templates. It is a weak fit when the business is a catalog with tax and a hosted checkout, or when nobody will log in after launch. A demo theme with sample plugins still on is not the system we ship.
Right fit
Choose it for the editors, not the market share.
WordPress fits a firm, a clinic group, a publisher, or a company whose marketers ship pages every week. The block editor can carry that if the allowed blocks are few and the required fields are obvious. Training is part of the project. A CMS nobody opens is a brochure that happens to have a login.
It is the wrong tool when checkout, inventory, and tax are the product. That conversation is WooCommerce, Shopify, or BigCommerce, decided before design. It is also wrong when the page is a fixed composition and the team will never edit it. A smaller marketing site is cheaper to keep than a CMS built for a staff you do not have.
- More than one person will publish, and they are not all developers.
- You need real templates: locations, services, people, articles, or landing pages.
- Hosting can move if the vendor relationship changes.
How the build differs
Fields, roles, and a plugin list with names.
The build starts from the templates, not from a theme-marketplace screenshot. We decide which blocks an editor may use, which fields are required, and what a location or service page must contain before it can go live. The second page should look like the first because the template enforces it, not because someone pasted a deck.
Plugins are a bill of materials. Forms, redirects, SEO fields, and caching each get one maintained plugin. Staging exists, and updates run there before production. The editor notes live in the admin, where the work happens. A PDF that names a plugin you removed last quarter is not a handoff.
- A block set small enough to teach in one sitting.
- Separate roles for author, editor, and administrator. No shared admin login.
- Staging, plus a backup that has been restored once on purpose.
What fails later
Two builders and a theme nobody can explain.
The usual failure is a page builder, a second builder 'for landing pages,' and an SEO suite that overlaps both. Every URL was drawn by hand, so the next edit breaks the header. The agency after us quotes a rebuild because nobody can say which plugin owns the homepage.
The other failure is a custom theme with no notes and a habit of editing production. A PHP update then whitescreens the site, and the backup has never been tested. We will not take over a site by clicking update on the live server to see what happens.
- No nulled themes and no plugins from a marketplace you cannot name.
- No two plugins writing the same title tag.
- No hand-built layout for every URL when a template would do.
What we check
An editor publishes, and the header survives.
We do not grade the build on a single speed screenshot. We grade it on whether a trained editor can publish a real page from a draft without breaking the header, the form, or the navigation. The first weeks after launch are for that test. If every change still comes back as a ticket, the template model failed.
We also keep an update log and a written plugin list. Speed problems get a plugin removed before a new plugin is added to hide them. Search Console is a check that the templates you meant to publish are the ones getting fetched, not a promise about rankings.
- Time from draft to published, done by your editor on a standard template.
- A plugin list that states the job of each plugin.
- An update log: what moved, and what was rolled back.
Example engagement
A professional services firm with four editors.
Professional services firm, four people in marketing, a WordPress site that had passed through three agencies. The homepage used one page builder. Interior pages used another. Staff bios were posts in a category called Team. Publishing a location meant cloning the homepage and deleting sections until it looked close.
We replaced that with templates for location, service, person, and article. Each person got a role that could not install plugins. The planned window for a marketing-site template set of this shape is 8 to 12 weeks, and that is what we scheduled. After handoff, the team published two service pages with no developer on the thread. That is the outcome. It is not a traffic promise.
8 to 12 wk
Planned window for this kind of marketing-site template set
Roles
Author, editor, and admin kept as separate logins
The example uses anonymized results from a Quorum engagement. It is one account, not a benchmark you should budget against.
Questions
WordPress questions.
Should we start from a theme we already bought?
Only if the theme is maintained and we can strip it to the templates you need. A demo import with sample content and bundled plugins is a cleanup project, not a head start. We would rather build the four templates you will reuse.
Can our marketers edit the homepage?
Yes, inside the blocks we allow. They should not be able to install plugins, edit PHP, or restyle the header from one page. If the homepage is a one-off drawing, the next campaign will break it.
Do you build custom plugins?
Rarely. Most sites need a careful choice of maintained plugins and a clear content model. A custom plugin is justified when a real workflow does not fit, and it gets the same staging rule as everything else.
What if we also sell a few products?
A handful of simple products can live on the same site if someone will maintain them. The moment tax, shipping rules, or a large catalog show up, we stop and choose a store platform on purpose. We do not bolt a store onto a blog and hope.
Is the SEO plugin the SEO program?
No. The plugin stores titles, descriptions, and the sitemap settings. The program is the page map, the internal links, and the content. That work is a separate engagement from this build, even though the fields have to be ready on day one.
More in this lane
Other Web Design platforms.
Talk through wordpress.
One conversation. A diagnostic. A plan you can kill if it is not the work.