WordPress deserves its reputation both ways. Built carelessly it becomes a plugin graveyard nobody wants to touch. Built deliberately it is still the best place to put an editorial team that publishes every week.
Blocks, not a page builder
We build custom blocks for the patterns your content actually uses: a comparison table, a quote, a call to action, a case study card. Editors compose pages from those. What we do not do is install a page builder that turns every layout into an unmaintainable nest of nested rows.
Content modelling first
Custom post types and fields that describe the content rather than the page it happens to sit on. That is what makes a redesign a template change instead of a re-entry project, and what lets the same content feed a newsletter or an app later.
Performance
Full-page caching, images in modern formats at the right sizes, a theme that does not enqueue every script on every page, and third-party tags kept in Tag Manager rather than hard-coded across templates. Core Web Vitals are measured before and after, and the numbers go in the handover.
Security and maintenance
Least-privilege roles, two-factor on admin accounts, updates applied on a schedule against staging, off-site backups that have been restored at least once. Most compromised WordPress sites we are asked to clean were running a plugin that had a patch available for months.
When it is the wrong tool
If nobody will publish more than twice a year, a static build in Astro is cheaper and faster to run. If one content set has to feed several front ends, look at a headless CMS instead.
Editorial strategy sits with content marketing; the commerce variant is WooCommerce.