Quote from: Roberto at Jun 03, 2009, 03:19 AM
Hi, I’m posting just to inform you that we chose MODx.
It beats TYPO3 for a couple of reasons:
1) Templating is really simple, whereas with TYPO3 you have to learn TypoScript.
2) Very intuitive backend, with almost the same functionalities as TYPO3.
3) Immediately operative. With TYPO3, before you can make something, you have to spend a lot of time learning it.
4) Creating snippets for custom behaviors is quite simple, thanks to MODx API and the use of PHP.
Bye!
I’m currently exploring the advantages of MODx in comparison to TYPO3 which I’m productively working with. I’m quite new to MODx, and one of the main reasons why i’m interested in MODx is that it seems to be really VERY FAST, while i have to admit not to have built a more complex test site to proof if that promising performance is always true...
As regards TYPO3 i have to disagree to some of your statements:
1) Templating is really simple, whereas with TYPO3 you have to learn TypoScript.
That is not true, if you have installed the extension "TemplaVoila". For me TemplaVoila was the ticket to TYPO3! Once you have understood the way how it works, which in fact isn’t hard at all, and templating is VERY easy. Just take any HTML layout you like - you don’t even have to put any placeholder code or any php stuff into that template -, just define, with the help of a few mouse clicks, where you want to have dynamic content, menu or submenu(s). That’s all.
2) Very intuitive backend, with almost the same functionalities as TYPO3.
As far as i can see now... for me this is not really true. While i have to admit, that an interface you are familiar with will always seem to be more "intuitive" than any other one. For me, the backend of TYPO3 is one of the most intuitive interfaces i’ve ever seen (i’ve been working productively with Joomla, Contenido, DerDirigent, Sefrengo, TYPO3, i have tried WebsiteBaker, Concrete and Drupal).
3) Immediately operative. With TYPO3, before you can make something, you have to spend a lot of time learning it.
Partly i have to disagree here. Since i’m new to MODx, i can tell about having A LOT to learn, a lot to explore regarding both terminology and workflow, before getting a first test site up and running.
Well, maybe one have to spend more time to learn how TYPO3 works. My experience with TYPO3 has been so far, that nothing worked "out of the box". One always have to know EXACTLY HOW to get things done. But once you know, it’s actually very easy! It’s always a good idea to keep notes for future needs. Every time i learn something about TYPO3 i write down everything, i’m still keeping that habit, it helps me a lot.
Actually, "immediately operative" isn’t true for both systems.
4) Creating snippets for custom behaviors is quite simple, thanks to MODx API and the use of PHP.
Currently i’m finding out how true this is with MODx. On the other hand, there are thousands of modules for TYPO3, for each and every purpose, so you don’t have to do any handicrafts at all...
When you start with TYPO3, one of the most important and time consuming things is:
configuration. It’s not that so much had to be done, it’s just HOW configuration has to be done. Once you know, you find it easy an logical.
Michael
Congratulations! But let’s hope that’s "au revoir", not "Bye!"??
