Ask Any Question

Content Management: Joomla VS Typo3?

www.PCinvent.Info - 2007-04-18 16:21:02 - Programming Design

Joomla CMS now looks like the most popular CMS in the World now while Typo3 CMS is still very active in Germany community. However, my Web design company is still focus on Typo3 and not decide to pick up Joomla. Here, I jsut want to know in general. Anyone knows which CMS will be good for American in the coming few years (Let say 3 years). Please compare Joomla Typo3 base on English user. Please guide, Thanks! Anyone Know what Typo3 is? Anyone who can help on this comparison in detail, I will give it as best Answer. Thanks! I evaluated both before I give up Typo3. Typo3 is a good CMS, especially it can allow you to create many content item at once before your fill in the content. However, Typo is absolute Not recommend for English user who don't read dutch to use. If you don't need any modification, development on their existing code, it will be ok. If you do, you will: 1. waste a lot of time to maintain your Typo Script 2. can not find help resources which are written in English. 3. Find out the development is slow and inactive. ( Look at their release you will know. How long had MySQL5 been released? Long enough, Right? But Typo3 is still in Beta now trying to support MySQL 5. Anyway, just my little cents here. You will see if you evaluate both. Comparison between the Joomla and Typo3 - 3 times "1st Winner of Open Source Project" - Included CMS of course ( TYPO3 never be the winner of any) - Joomla its offical website reached 100,000 users; an average of 172 new user sign-up each day (Don't knowTY

Best Answer:

First of all, I am somewhat Biased being a professional .Net developer. When I was learning .Net, I was also looking into the php side of the world. I looked at all the CMS's and bopurds and found that none of them stood up very well. What I use is DotNetNuke(DNN) on the Asp.Net platform. Because it is compiled code and not script code, it simply scales better. And makes it very simple and easy to create code to cache certain things server side and lighten the loads on SQL and your web server. DNN is fully skinable with 100s of free and 1000s of commercial skins available. Installing skins is beyond simple, you go to the skins page and use the skin upload page to upload a zip file with the skins content and DNN unzips the skin and installs it. DNN also has a very good module inertace that allows for custom modules to be added. Modules are installed like skins, go to the modules page, use the upload to upload the module zip file and DNN takes care of installing it. Ther are many 100s of free DNN modules and 1000s more for sale. Installing skins and modules of course does require the proper security role. DNN is completly clean URL. Now for the features that really make DNN stand out over the php crowd.... DNN supports multiple sites per install and each site can have its own set of addresss aliases, The way it handles this is by the uise of its own HttpHandlers and is handled along ith the code that does the url rewriting for clean urls. By looking t the domain that is in the target url of a request it can know which site the request is for, and tag that with an id. And unless you are the top most level of admin, called host or super user, you cannot tell there are more than one site there. You can view sourse and opick through the HTML, you still cant tell. And of course each sites gets its own skin selection so those dont effect the other sites. DNN also automatically takes care of creating and managing a Google SiteMap of all the sites on an installation. By default only host admins can upload skins or modules. The host can howvever enable sites to upload there own skinds and modules and those will by default only be usable to the site that uploaded them. The host also designate skins and modules to opnly be available to certain users. You can find out a lot more at http://www.dotnetnuke.com/ And for the stats, the DNN site has 423,550 users as of the time of this writing with an average of around 630 new users per day.

Answers:

First of all, I am somewhat Biased being a professional .Net developer. When I was learning .Net, I was also looking into the php side of the world. I looked at all the CMS's and bopurds and found that none of them stood up very well. What I use is DotNetNuke(DNN) on the Asp.Net platform. Because it is compiled code and not script code, it simply scales better. And makes it very simple and easy to create code to cache certain things server side and lighten the loads on SQL and your web server. DNN is fully skinable with 100s of free and 1000s of commercial skins available. Installing skins is beyond simple, you go to the skins page and use the skin upload page to upload a zip file with the skins content and DNN unzips the skin and installs it. DNN also has a very good module inertace that allows for custom modules to be added. Modules are installed like skins, go to the modules page, use the upload to upload the module zip file and DNN takes care of installing it. Ther are many 100s of free DNN modules and 1000s more for sale. Installing skins and modules of course does require the proper security role. DNN is completly clean URL. Now for the features that really make DNN stand out over the php crowd.... DNN supports multiple sites per install and each site can have its own set of addresss aliases, The way it handles this is by the uise of its own HttpHandlers and is handled along ith the code that does the url rewriting for clean urls. By looking t the domain that is in the target url of a request it can know which site the request is for, and tag that with an id. And unless you are the top most level of admin, called host or super user, you cannot tell there are more than one site there. You can view sourse and opick through the HTML, you still cant tell. And of course each sites gets its own skin selection so those dont effect the other sites. DNN also automatically takes care of creating and managing a Google SiteMap of all the sites on an installation. By default only host admins can upload skins or modules. The host can howvever enable sites to upload there own skinds and modules and those will by default only be usable to the site that uploaded them. The host also designate skins and modules to opnly be available to certain users. You can find out a lot more at http://www.dotnetnuke.com/ And for the stats, the DNN site has 423,550 users as of the time of this writing with an average of around 630 new users per day.