[TYPO3] Joomla! vs. Typo3

[Ryan Off]

Dave, you shared my thoughts exactly. I used Mambo for just over a  
year (and still using it for my personal site until I switch it over  
to Typo3). I've even thought about going back to it recently as well.  
I like the simplicity of Mambo. Lot's of plug-and-play extensions,  
etc. It's quite easy to configure a nice site with a lot of added  
functionality (gallery, front end users, document management,  
newsletters, etc). The problem is that as you mentioned, it is hard  
to customise the extensions. As my PHP skills are much better than my  
Typoscript skills, I don't mind going in to the source code and  
changing around the PHP files. For me that was a lot less time  
consuming than struggling with Typoscript.

Managing a large site is not a problem, but ONLY IF that large site  
has a lot of similar content. Meaning that if you can create a few  
categories you can have a lot of pages that are dynamically generated  
by only adding new content items. Making a 100+ page site is quite  
easy to manage, but only when 90% of it is very similar with only  
changed content.

For me, the selling point of Typo3 is the intuitive backend structure  
using Pages with content items. If Mambo (or another CMS) did this,  
then I would definitely look in to changing to rid myself of the  
Typoscript (and other bugs/configuration) problems I have with Typo3.  
So thus, I'm sticking with the enormous learning curve with the hopes  
that one day I will finally understand Typo3 and website creation  
will be a snap. I've been using a low-end commercial CMS at work with  
uses a page structure in the backend. It's quite nice, but definitely  
lacks a lot of features/modules/etc which Typo3 has.

My recommendation would be that if you would like an easy to setup  
site with similar content, then go with Joomla/Mambo (or Drupal)  
which are category/section based. The mambo community is also really  
great at helping you with configuration problems (a bit more young  
and fun, although more un-professional than the corporate/intelligent  
feeling I find with Typo3). Of course as you know, the Typo3  
community is quite active and nice as well. But if you want high  
power/flexibility or the ability for content creators to understand  
the page structure (which as I mentioned is a HUGE benefit to Typo3)  
then buckle down your boots and learn Typo3. Both CMSes have many  
strong points and if they were both a bit like each other all of us  
would be better off (no mambo backlash here please.. I'm praising  
both systems). Try them out and let us know how you feel.

For me, I'll stick with Typo3 for now (although I'm going to give  
Drupal a test run in a few days).

enjoy..

Ryan


On 20 Jul 2006, at 11:18, dave ashton wrote:

> Hi,
> Had a look at Joomla as I was getting completely frustrated with typo3
> (well, typoscript!)
>
> Joomla, to me, is good if you want a news or article type site.
> Out of the box, it is arranged in sections, categories and pages.  
> You create
> menu's, then create section/categories/pages then create content,  
> then say
> which cat./section/page you want the content putting.
>
> This process in Joomla, you seem to stuck with.
> Joomla seems to have lot of extensions that are plug and play (how  
> well they
> work, I don't know)
>
> Typo3, I think, when you get the basics down, can be configured to  
> look and
> work exactly as you want it, frontend and backend.
> It has a more logical way of setting up content - create pages (you  
> can see
> these logically in the page tree) then put in content. If content  
> is to go
> on various pages, then share the content with a shared page.
> However, typoscript is a big pain in the arse to learn IMHO.
> I think most, see the power of typo3, so bear with the pain of  
> learning
> typoscript.
> However, you have to weigh up the cost of learning some typoscript  
> (lots of
> time spent!) and getting what you want configuring-wise or having a  
> more out
> of the box solution which may not do exactly what you want.
>
> IMHO if you need a news article site only, with most stuff working  
> out of
> the box, with not much else configured then Joomla might do it.  
> Even if you
> get a site on the frontend to look and work as you want with  
> Joomla, the
> backend is still arranged in cats./sections/pages, etc.  (after  
> using mambo
> for a year or two, (joomla is based on Mambo), clients can get  
> confused with
> the cat/section page way of working.)
> If you want a cms frame work that you can configure from the ground  
> up, as
> you want it, frontend and backend, use typo3. However, be prepared  
> to have a
> steep learning curve (probably the angle of Everest!)
>
>
> You can argue, until the cows come home, which is the best, etc.  
> The only
> real test is to install both, have a play with them and see which  
> fits your
> needs.
>
> At the end of the day, time is money as a developer, so you have to  
> weigh up
> what can do the job and hopefully, further jobs with the least  
> headache.
>
>
> Dave
>
> -----Original Message-----
> From: Dmitry Dulepov [mailto:typo3 at accio.lv]
> Sent: 20 July 2006 08:45
> To: typo3-english at lists.netfielders.de
> Subject: Re: [TYPO3] Joomla! vs. Typo3
>
> Hi!
>
> Sean Gonsman wrote:
>> Has anyone used Joomla? Does anyone have any good information that  
>> would
>> give one the advantage over the other?  I have used Typo3 to  
>> develop one
>> site and I have done a comparison at cmsmatrix.org.  Now I am just
>> looking for real world comments.  Thanks.
>
> In case if you did not know, Secunia (security company) released the
> following bulletins about Mambo/Joomla for the past week (only one  
> week!):
>
> [SA21082] Mambo VideoDB Component File Inclusion Vulnerability
> [SA21079] Mambo-SMF Forum Component File Inclusion Vulnerability
> [SA21077] Mambo LoudMouth Component File Inclusion Vulnerability
> [SA21068] Joomla PollXT Component File Inclusion Vulnerability
> [SA21059] Joomla Joomlaboard Component "sbp" File Inclusion
> Vulnerability
> [SA21055] Mambo SiteMap Component File Inclusion Vulnerability
> [SA21053] Joomla com_hashcash Component File Inclusion Vulnerability
> [SA21044] Mambo / Joomla perForms "mosConfig_absolute_path" File
> Inclusion
>
> Eight security bulletins withing one week...
>
> Dmitry.
> -- 
> "It is our choices, that show what we truly are,
> far more than our abilities." (A.P.W.B.D.)
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english
>
>
> _______________________________________________
> TYPO3-english mailing list
> TYPO3-english at lists.netfielders.de
> http://lists.netfielders.de/cgi-bin/mailman/listinfo/typo3-english