What we use WordPress for
WordPress is our system for sites with a clear structure and one editorial team: company websites, location and property presentations, product pages without a sales function, blogs and news sections. When a website is mainly there to inform and does not serve several departments in parallel, a WordPress project is live sooner and easier to maintain day to day than a TYPO3 installation. The Gutenberg editor is usable for that, provided the available blocks have been settled beforehand.
WordPress often arrives as a second site alongside an existing system as well: a careers portal, a campaign page, a specialist blog. Projects like these have a narrow scope and still have to fit the corporate design. We build them with a custom theme that carries the design rules, and we take them into maintenance and monitoring. A website without an update plan is not a project, it is an arrangement to deal with it later.
How we work with WordPress
We develop custom themes against the design instead of bending a bought theme with a page builder. The difference shows in operation: a custom theme has the code it needs, a builder setup drags along options nobody has ever used. We define blocks to match the content types, and add custom post types and fields where content has to be structured rather than ending up as running text in the editor.
The security situation of a WordPress installation almost always hangs on the plugins, not on the core. That is why our plugin list is short and justified: every plugin needs an active maintainer, a traceable update history and a reason why it is not replaced by a few lines in the theme. We install updates on a staging instance first. Backups, PHP version and availability are monitored as part of the hosting, and support is there Monday to Friday, 9:00 to 16:00 CET.
Limits: when WordPress no longer carries
WordPress is quick to start and expensive to maintain badly. Whoever clicks something together cheaply pays later for the untangling. The limit is reached when many editors are meant to work with different rights, when several tenants or genuine multilingualism are called for, or when the page tree grows past the point of being readable. Role and translation plugins can imitate that, but each one is another point of dependency. For requirements like these we recommend TYPO3.
For selling, the same applies on a smaller scale: WooCommerce turns WordPress into a serviceable shop for a manageable range. As soon as B2B pricing logic, customer hierarchies or an ERP connection are added, Shopware 6 is the more suitable system. And when a requirement is essentially an application — a configurator, a portal with user accounts, a process chain with approvals — we build it as custom software instead of hanging it off an editorial system as a plugin.