Subscribe to Acqal

Got Thoughts? Write Us!

Contact
Request
Validate

Approved TYPO3 Agency

Acqal is an approved TYPO3 agency focusing on support, training and website migration.

This means that we...

  • are available on TYPO3.org
  • make substantial contributions to TYPO3 teams
  • are registered as business members of the TYPO3 Association
  • have completed more than four TYPO3 projects
  • have proven our technical abilities with quality TYPO3 extensions
  • use TYPO3 for our own website

Acqal is a TYPO3 Association Business Member

Popular Blog Posts

Blog Topics

Virgil on Twitter

Please wait while virgilhuston tweets load Twitter is loading

Recent Blog Posts

Blog Archives

TYPO3 is the Best Enterprise Content Management System (CMS)

Saturday, March 14, 2009 12:15 AM EDT
Topics: Business, TYPO3

By: Virgil Huston

voting in progress Submitting your vote...
Rating: 4.8 of 5. 5 vote(s).
Click the rating bar to rate this item.

TYPO3 versus other CMS platforms is a constant discussion. This week, in Twitter discussions, the question was again asked: "Why is TYPO3 the CMS of choice in Europe and Drupal more popular in the US (for open source solutions - I have previously covered why no company ever should waste their money on a propritary CMS). The first reason is that TYPO3 was developed in Europe and first took hold there. US CMS developers were/are slow to take it up. Drupal was also developed by a European, but has a larger US presence.

I know what my opinion is, TYPO3 is superior, I came to that conclusion after months of research. I decided to take a look at what others have said. Joomla, Wordpress, and other platforms are always discussed, as well as TYPO3 and Drupal. Joomla and Wordpress are great for certain situations, but not for complete enterprise level content management.

I did a google search on TYPO3 / Drupal comparisons and I was actually surprised at what I found on a random basis. While not scientific, this was a random sample that eliminated sites run by official Drupal / TYPO3 organizations.

A few quotes:

from Typo3 vs Drupal

Along the way, I discovered Typo3 - a very powerful and interesting content management system. Typo3 looks like it can do just about anything, and looks extremely flexible. I spent quite a bit of time with it.

The problem with Typo3 is that it is very difficult to set up. The main problem are the templates - very powerful, but they are not based on any standard such as HTML or PHP etc. The developers have invented their own system, and you have to learn it from scratch. This is no trivial proposition, even for people who are good at this sort of thing and very tech-savvy.

Does Typo3 have place in the online world? It certainly does - it allows you do to do just about anything you could possibly imagine with a content management system. If there is a CMS out there with a feature, Typo3 probably has it too.

Unless you need a very specialized installation for a large organization, you are probably better with Drupal. Between the two, I recommend Typo3 only if Drupal does not meet your must-have requirements, or if you really like fiddling with esoteric systems. If you choose Typo3, you will certainly have a great site, as long as you put in the long hours and hard work to learn it properly.

A comment on the above post:

Hi guys, I used to love drupal I spend over 2 years using it, until I found TYPO3, with all the respect Drupal is great but when we are talking about enterprise solution, where you have a distribute content generation proccess, with a lot roles and access control policies, when you have to set up workflows for many sections on your site (or sites, Intranet, extranet, etc) then I think Drupal it’s not enough. Maybe installing a lot of modules of drupal and even modifying it to feet your needs you could set up these requierements, but then who is the one who “is very difficult to set up”? So if you have e scenario like i describe above, I truly recomend TYPO3.

TYPO3 vs Drupal CMS

In our opinion, TYPO3 CMS appears to be the most appropriate system for complex websites, because the system is able to maintain an overview at all times. The management of several language versions, for example, remains very clear.

TYPO3 includes a multitude of advanced features that are often indispensable for larger organisations, such as workflow management and draft workspaces. Mia offers thorough training courses for TYPO3 users, and these are necessary in order to learn to manage all the applications.

Drupal CMS started as a community platform. Therefore, the core system contains a whole range of community features like creating profiles, social tagging, etc.

In Drupal CMS, the website is always modified via frontend editing. Drupal frequently operates in a self-explanatory manner, and therefore appears to be more accessible for the user. We would therefore recommend this system for simpler websites with a lower update frequency. Drupal is nevertheless able to provide an answer to any requirement that the client may have.

There are many more similar examples, but this post is already way too long. There are two major conclusions I derive from this sample of reviews:

1. For do-it-yourselfers without extensive technical knowledge, don't use TYPO3. Drupal probably isn't appropriate, either. Wordpress or Joomla is the way to go. Just realize that if you grow out of one of these platforms you are looking at completely replacing your system or doing extensive and expensive customizations. Both TYPO3 and Drupal are quite scalable, although TYPO3 is more so.

2. A huge porportion of the complaints about TYPO3 is the learning curve. I am not as technically inclined as many, so I felt the pain, too, and still do. If you have complex web site needs, any platform is going to have a big learning curve. This is not a reason to reject TYPO3 or embrace another system like Drupal. Yet, this is probably the most common reason I see for not using it.

TYPO3 is an enterprise level solution and requires enterprise level expertise to get a complete site going. That is what Acqal does. Users don't see this, with some training, required with any system, even Wordpress, TYPO3 is a pleasure to use.

A lot of people who choose Drupal over TYPO3 do not understand TYPO3, that is very clear when reading many of blog posts, articles, etc. They think Drupal is easier so it must be better. It ignores the capability of TYPO3. This hurts TYPO3 market penetration in the US, no doubt. One of Acqal's missions is to help change some of these invalid attitudes.

Keywords:

  • typo3,enterprise content management system,ecms,cms,wcm,web content management

Please Share This Post

Tweet thisRedditBookmark on deliciousStumble thisShare on Facebook

Send this article via email to your friends and peers.

Leave a Comment

Add comment

* - required field







Notify me when a new comment is added.
By Michael Cannon on Wednesday, December 31, 1969 8:29 PM EST
Gravatar: Michael Cannon Great article Virgil. I hadn't seen a couple of these quotes yet. Thank you for sharing.

Don't forget to Digg the article.
By Jasbir Khehra on Wednesday, December 31, 1969 8:33 PM EST
Gravatar: Jasbir Khehra Well researched post. As someone who is using both Typo3 and Drupal, I agree Typo3 has a steep learning curve but it matches Drupal on every count.
By Monis K on Wednesday, December 31, 1969 8:38 PM EST
Gravatar: Monis K Nice to find some thing like that! We are serving with TYPO3 since a long time and really we never looked back for some different or alternate solution. I can say TYPO3 is a 'frame work'.
By Dmitry Dulepov on Wednesday, December 31, 1969 9:50 PM EST
Gravatar: Dmitry Dulepov Some people choose using different principles. For example, though I use TYPO3 for my blog I will never do this again. I'll go with WordPress. My principle is "use right tool for the job".

People may prefer Joomla or Drupal because it will be faster to achieve their goals with those systems. Being a TYPO3 developer, I am still on their side in this case. Not everyone needs a Boeing, often a Cessna will do :)

Much worse problem is those marketing reports about enterprise CMSes. This is where we should talk back.
By Michael Cannon on Wednesday, December 31, 1969 9:54 PM EST
Gravatar: Michael Cannon Agreed on using the right tool for the job. Use WordPress is you're only going to be blogging, TYPO3 is overkill.

I helped a friend recently migrate to WordPress from a custom static and SSI website. I wouldn't have wanted to do it in TYPO3. See http://www.foreignpolicyjournal.com/.

On the enterprise CMS and WCM talk back, Virgil's on it at http://www.acqal.com/a/article/typo3-and-other-open-source-wcm-systems-dissed-again-159.html.
By Virgil Huston on Wednesday, December 31, 1969 10:12 PM EST
Gravatar: Virgil Huston Dimitry,
I completely agree with you on using the right tool for the job and I actually recommend Wordpress to a lot of people, depending on what their goals are.

Virgil
By Jesse Taylor on Thursday, May 27, 2010 5:36 PM EDT
Gravatar: Jesse Taylor I am trying to maintain a site that is content/information rich (1000+ pages), and contains a blog and news feed. I am only planning on having a single developer (myself), and two contributors to start out with.

I've been digging through the sources of both Wordpress and Drupal lately, and both of them are a total spaghetti-fied, unreadable, poorly designed disaster.

It TYPO3 going to be overkill for what I am trying to achieve? Can a single developer manage a TYPO3 site? I am willing to spend a month or two getting it set up, if it will save me time hacking Wordpress to try to make it into a CMS.

Just how "enterprise-level" is TYPO3 -- does it require an enterprise-size team to manage it?
By Virgil Huston on Thursday, May 27, 2010 6:00 PM EDT
Gravatar: Virgil Huston Hi Jesse,
Thanks for the comment. TYPO3 is truly enterprise level software, but is used in many simpler applications. One of the great things about TYPO3 is you have almost unlimited expandability and scalibility, so you'll never have to change your CMS.

One person can easily manage a TYPO3 site. Your major limitation is going to be content entry if you are adding things daily. But, you would have this issue with any CMS.

One more thing about TYPO3, the community is great and there are now some great quickstart packages to help you get started:
1. Ron Hall's Templaviola Framework, a complete TYPO3 setup: http://templavoila.busynoggin.com/
2. Web empowered church package - this one has tons of features and is geared to churches, but easily used for non-church sites: http://webempoweredchurch.org/
By Ali Shaheen on Thursday, May 27, 2010 6:08 PM EDT
Gravatar: Ali Shaheen I would do the following:

1. simple content+blogging site: Wordpress
2. Social network: Drupal
3. Enterprise CMS + potential for eCommerce: TYPO3.

By the way, we just launched one of the world's first cloud based hosted TYPO3 solution. Simple go to http://easyweb.coeus-solutions.de and start your site in simple clicks. Key features are:

1. No programming required
2. No upfront investment
3. It's €25/month with FREE domain registration if you want it.

Try it out for your next TYPO3 project?

Best wishes,

Ali Shaheen
EasyWeb - a project of Coeus Solutions GmbH