WordPress or TYPO3? This is a controversial question. The agency d-mind implements both systems. We spoke to Jens Fuchs about the advantages and disadvantages of WordPress vs TYPO3.

This involves issues such as scalability, security and the implementation of multilingual projects. But expansion using plugins and extensions also plays an important role. WordPress has its strengths, as does TYPO3. You are welcome to join the discussion: Use the comments at the end of the article.

Jens, how do you decide which CMS to use for which project?

Customers often already have specific ideas about a system when they make an inquiry. If this is the case, then this is set - subject to a technical and price check. If there is a free choice of CMS, we like to use TYPO3 for multilingual sites and increasingly complex technical requirements. We tend to use WordPress for small to medium-sized sites.

SEO and multilingualism

WordPress is suitable for heavy editorial maintenance, i.e. a constant stream of new articles with a focus on search engine optimization (SEO). Especially due to the easy-to-use backend, especially since the new Gutenberg Editor.

Is the switch to Gutenberg working well for your customers? What do you have to bear in mind?

We have not yet converted any existing websites to Gutenberg, but in these cases we allow you to choose between Classic and Block Editor. The latter is to be supported until the end of 2021. As the old editor only supports text and images, it is in principle upwards compatible. The old text block can also be converted to Gutenberg blocks using "Convert to blocks".

Editing with Gutenberg

Personally, I think the Gutenberg editor is a success. When copying and pasting from third-party applications, it converts list elements, hyperlinks and blocks - better than other editors. Drag & drop also works well. A significant difference is the consistency in handling custom fields (Advanced Custom Fields). We used to place these controls below the content in the backend, but now we build flexible Gutenberg blocks instead.

Let's start with the typical reservations. TYPO3 is considered powerful, but expensive and cumbersome. Companies keep telling me that even the smallest changes are developed manually by their agencies - at high cost. Why is that?

The initial development of a website with the same technical requirements will not differ fundamentally between the systems. In the past, however, updates of old TYPO3 versions involved enormous effort. Especially if you were working with third-party extensions that were no longer being developed. In the past, this was sometimes done short-sightedly, even in our company.

WordPress has an advantage here. This is because popular plugins are constantly kept up to date and are usually also sold commercially due to the quantity. However, I don't see a huge difference now that third-party plugins and extensions are largely avoided.

WordPress scores with the plugins

However, it is also true that TYPO3 was offered at a higher price in the past. The cost of updates or an extension that cannot be mapped using an extension can be particularly shocking for customers who do not have much experience with agencies. However, large customers usually understand the effort involved.

WordPress, on the other hand, has a reputation for being insecure. Is that true? And what measures do you use to secure your customers' WordPress projects?

Apparently, a third of all websites worldwide currently run on WordPress. Its widespread use makes it an attractive target for hackers. However, we haven't had a hack on sites we have developed for years. Simple measures are:

• Invididual database prefix
• Change salt key in wp-config.php
• No username "admin" as admin, a strong password
• No third-party plug-ins and updates four times a year
• You are welcome to set the access data in the environment variables
• Possibly secure the admin area twice via the .htaccess or use the Wordfence plugin

Since the hosters rarely keep backups for long, I still make sporadic backups for local backup. Successful hacks in the past have always been caused by third-party plugins. So be careful when choosing.

Another explanation for successful hacks and the reputation of being insecure: Compared to TYPO3, WordPress is often set up by non-experts with a lack of security.

Cookie solution, backups and child themes

What are your most important tips and plugin recommendations for WordPress?

Advanced Custom Fields Pro is the plugin I wouldn't use WordPress without. It enables individual input masks in no time at all and is well documented. If it does need to be multilingual, I have had good experience with Polylang. When using the Bootstrap CSS framework, I find Bootstrap Blocks a great extension for the Gutenberg editor.

Borlabs Cookie is currently our tool of choice for implementing the new mandatory cookie policy. Incidentally, I use the CMS Commander tool for an overview of all our pages, including the version and plugins used. A one-click backup is also possible here for sites that are not too large.

My tip: If it is foreseeable that a customer will have several similar pages created, then create a theme for them - with the most important settings and the main CSS. You can then customize and add everything at child theme level. You can also use Github to deploy the theme when making changes. Another tip: For a project, you should communicate the follow-up costs - in the form of updates - to the customer straight away.

Advantages of WordPress and Typo3

Where do you personally see the most important advantages of WordPress?

WordPress has a low barrier to entry, as the PHP requirements are not high. There are excellent third-party plugins if required. Almost all the problems you have during development have already been experienced by someone else. In this respect, the forum or Stack Overflow are often helpful. Editors like to use the backend. If necessary, there are also instructional videos on YouTube for editorial use.

And what are the advantages of TYPO3?

The scalability and the requirement for developers to work properly. Not forgetting the native multilingualism and granular rights management. In terms of security, it is also unlikely to be a worthwhile target for hackers due to its low distribution.

What should companies look out for when choosing an agency for WordPress or TYPO3? In your opinion, how can you determine and test the quality of an agency?

The age of the agency and the size of the team can be an indication of secure, sustainable support. The price offered must be realistic. If you take the cheapest offer, you will end up paying more later. The offer should include a transparent reference to support after the end of the project.

Support counts

This concerns issues such as support, response times and updates. I would also look at current reference projects. Are they visually appealing and GDPR-compliant? You should also check a few technical details, but not everyone can do that.

How did you come to rely on both systems and not specialize?

TYPO3 is usually used for large projects with high technical requirements. We want to do big, beautiful projects. But they don't come along every day. And that's why we added WordPress to our portfolio a few years ago. If you look at the market share, you can hardly avoid it. Incidentally, most agencies do this now.

Can you name any projects that could only be realized with WordPress or TYPO3?

TYPO3 has been the tool of choice for the Akademie für Lehrerfortbildung Dillingen due to the mass of contributions and the complexity. For our main customer Wirtschaftsförderung Region Stuttgart, a WordPress setup with a constantly evolving main theme has paid off. We can set up a new website here in just a few minutes. In principle, however, most sites can be implemented with both systems, or with others. The decisive factor is not so much the system, but how it is set up.

Development for TYPO3 & WordPress

Do you have developers who implement WordPress and TYPO3? Or do you need special expertise for each?

We have two developers who do both. All the others specialize in one system. When it comes to front-end development, the switch is easier than with back-end development. Of course, this also has to do with the order situation. But specialization naturally makes more sense.

A few words about you and your agency? Are you still looking for developers?

d-mind is based in the beautiful south of Stuttgart and has been making websites since 1999. We are currently a team of 10 men and women, with a focus on development. We also often work in the background for other agencies.

We are looking for developers who are able to carry out tasks independently in a web environment. Preferably a synthesis of planning, front- and backend. In my opinion, specific CMS experience is not crucial, especially as WordPress can be learned and is well documented.

Featured image: Domenico Loia