Hi Before talking about Joomla, Drupal, Postnuke and many other CMS in comparison to TYPO3 simply check the security issues in the past and how long it took to solve it.
If you are a developer/hoster who cares for his customers you should be able to implement these security fixes as soon as possible without the fear that any of your sites is loosing its design or even content. As many Websites get maintained by non developer these security fixes should be also very easy to do - especially for somebody who is a non programmer. --- In all of those mentioned points Joomla and Drupal are failing totally, same Postnuke. TYPO3 instead is giving you a very simple way to update your website, to update or even downgrade your extensions immediately. --- We are working here with lots of Developers which know Joomla in and out and which programmed Postnuke or Drupal but since they have been here they are coming to our office to learn about TYPO3. It is amazing what they can realize. They are working with the new framework for templavoila, using Rons incredible good package which has been adapted now by the webempoweredchurch and they are fascinated from the huge possibilities the TYPO3 CMS is giving you - to the simple user. For one year we had really problems to get any Thai developers coming in here but since 2 weeks (after a Thai student came and gave her testimony about TYPO3) everyday new students from nearby Universities and developers who heard about the ThaiPo3 Usergroup we are having here pop up in our office not to get a job but to learn about this great CMS. Yesterday I had 15 People in my small office today were 8 as 7 went to HatYai to spread the news there and we will soon will have a workshop there. After only one week one of our newbie developers is now teaching her other friends in Typoscript! As I can't speak much Thai most of it she taught herself in only some days. They even were sitting down making competitions to implement a design in Joomla, Drupal and TYPO3 and TYPO3 (with the framework for templavoila) was first every time. They see the great potentials and were looking and investigating ways and arguments for their marketing campaign about TYPO3 now. Some days ago one of our developers was afraid posting in English on the mailing list but we helped him in wording. You should have seen his face after he received a response from Ron which solved his problem he was having in only 10 Minutes after posting. Meanwhile he is enjoying the mailing list as the help is only a click away and actually popping up. With no other CMS we found such fast response times until now. And it is not only the response time it is most of all the high quality of the response which is real helpful! They watched the video on typo3.org/podcasts to learn more about it, they are at the moment translating the tutorials of the WEC into Thai, because they want to spread the news. They call themselves ThaiPo3 - The Ulitmate Usergroup of South East Asia and love it! (They are actually promoting all kind of Free Open Source Products, not only TYPO3) IMHO there is no CMS which fits you 100% but if you have tried TYPO3 once and you really were able to identify the possibilities and power of it, than you will stick to it and TYPOscript is a great invention which really helps and its easy! If you don't see the power of TYPO3 simply stick to your other CMS and try to do your best there as we will need you there. This is the best way for us to get customers polarized to high quality and secure cms with a service and support guarantee by qualified agencies. Andi 2010/3/25 Erik Svendsen <[email protected]> > I have to disagree in most of your points. Personally I started out with a > CMS system in 2003 - 2004, and started with testing Mambo, eZ Publish, > Drupal and PostNuke. As an non-developer, knowing nothing about PHP, every > one of these was easy to install and get a site up and running, but when I > wanted to implement my own design I got stuck very soon. > > Then I tried TYPO3, and in a fairly short time I had a site with my own > design up and running. > > Den 25.03.2010 11:02, skrev Cameron: > > Drupal is superior to Typo3 in almost every way. Typo3 is an exercise in >> over-engineered academic CMS concepts, whereas Drupal + CCK + Views = 90% >> of >> any website you would actually end up putting together for a client. >> > > Yes, in many part it's over-enginered - like a lot of others enterprise > CMS. And you are correct that 90 % could be made with Drupal. But I bet that > you are going to use more and less the same amount of time that I would do > with TYPO3. > > > Typoscript is quite literally the most insane thing I have seen in 14 >> years >> of my career in the IT industry. >> > > Then you havent's seen how to configure some other Enterprise CMS. > > TypoScript is the main reason that I still are using TYPO3. Of course it > has flaws and some missing logic, but the power and flexibility of > TypoScript gives opportunities I haven't seen in any other CMS. With only a > few lines of code, you can change most of you website. > > > >> The other MAJOR issue, and one that seals it completely for me, is that >> the >> community around Drupal is 50 times the size of the Typo3 one. What this >> means is that any problem you have, the solution is a Google search away. >> The same simply does not apply for Typo3. Any CMS is going to take you a >> month or so to really get up to speed with, but with Drupal you'll find >> the >> perfect balance between flexibility and functionality. With Typo3 you'll >> be >> battling this arcane, lunatic bloody Typoscript system and not being able >> to >> find anyone to help. This isn't a *criticism* of the Typo3 community, you >> guys are plenty helpful enough, it's just that there's simply not enough >> of >> you. >> >> > I have never in my years using TYPO3 had any problems getting help. In 95 % > of the cases I have found it with a Google search, or reading a bit more in > the manuals. The 5 % rest I have got help on the mailing list. And I haven't > only made small and easy websites. > > Else, the size of a community isn't the same as quality. > > > Regards > > Erik Svendsen > > > > _______________________________________________ > TYPO3-english mailing list > [email protected] > http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english > _______________________________________________ TYPO3-english mailing list [email protected] http://lists.typo3.org/cgi-bin/mailman/listinfo/typo3-english
