WordPress or TYPO3?

WordPress or TYPO3?

WordPress or TYPO3? Many users ask themselves this question, although it is actually not really correct. Both systems have their own advantages and disadvantages and are just right for individual tasks. The following article shows which system is particularly suitable for which tasks.

Content for small tasks: WordPress in detail
Anyone who has ever been to various blogs or looked at private news sites will probably have stumbled across WordPress – without perhaps knowing it. As the name already suggests, the written word can be easily entered into the Internet with WordPress. 

Numerous templates for blogs are supplied with the free software package as well as aids that assist the user with practically every change, no matter how small. Smaller pages that are operated by one or two people can be put online with WordPress within a few hours.

However, the details suffer from this: Really independent pages can hardly be created due to the template formula, so WordPress pages always look a little as if they had already been there. In addition, essential components such as user-specific rights management are missing, without which larger pages are practically impossible to handle – but this is exactly where TYPO3 comes into play.

For larger tasks: TYPO3
Text and images can be uploaded with WordPress, but this is still a long way from a complete CMS. TYPO3, on the other hand, has the necessary tools to fully manage larger websites. 

One of TYPO3’s strengths is its flexibility, which goes far beyond comparable CMS such as Drupal: New functions, for example, can be added relatively easily via extensions without having to write even a single line of program code. The rights management that is missing in WordPress is also on board, so that company websites can also be looked after by TYPO3. 

The separate division into a front-end and back-end part makes development for TYPO3 even easier.

The disadvantages are obviously to be found in the high administrative effort: TYPO3 can hardly be used without extensive administrative knowledge, since the setup is simply too complicated. For private users, the framework is hopelessly overloaded. Learning languages ​​such as TypoScript for configuring the CMS can also be tedious – but TYPO3 is still made for larger websites.

TYPO3 vs. WordPress: summary

We primarily offer our customers the two CMS systems TYPO3 and WordPress and when advising customers we are often concerned with the question of which system is best suited for individual requirements, what differences there are between the two systems and what advantages and disadvantages they have Systems?

We compared the CMS TYPO3 and WordPress and summarized the results in a table. We analyzed the most important aspects such as security and development, expandability and flexibility, requirements for multilingualism and multi-site management, as well as user administration and content editing.

first version19982003
Open sourceYesYes
Support / LTSLong time supportregular updates
Market shares worldwide (January 2019 according to cmscrawler.com)1.5%60.2%
securityBasic configuration has sufficient securitysome additional configurations are necessary
Multi-site management (several websites in one CMS)Yespossible with plugins
MultilingualismYespossible with plugins
Structure of the contenthierarchical, based on tree structureflat within taxonomies
Management of contentcomplex, larger learning curveintuitive, smaller learning curve
Version controlYesYes
WorkflowYespossible with plugins

Both WordPress and TYPO3 have their right to exist, which shouldn’t be surprising. The vast majority of authors who want to put news in the world or want to write about a certain topic are very well advised with WordPress. However, the system lacks important components for commercial applications – and that is exactly what TYPO3 can offer.