Typo3 has a list of what Typo3 is not good for- real handy

lorriman · Post by **lorriman** » Thu 24. Mar 2005, 20:18

I almost chose Typo3 as my CMS, but thank God, the author had written a short paragraph on what Typo3 is not suited for, and I realised I would have been making a big mistake.

I realised since then that it is really handy to have lists made by the author of what their work does not do, doesn't do well or is not suited to. Roadmaps are very useful too.

The info at CMSmatrix and other places did not adequately warn me of the nature of Typo3, whereas the author's own words did, and at the very least complements the info at such cms portals.

Therefore my feature request is for a list of cons, a bit like Typo-3, but perhaps more detailed.

Thankyou!!

Greg

DusX · Post by **DusX** » Mon 14. Nov 2005, 20:20

so what words... leaned you away from Typo3?

cheers

lorriman · Post by **lorriman** » Mon 14. Nov 2005, 20:59

Its a long time ago, I can't remember exactly. But I do remember that Typo3 is a large, complex, flexible cms suited to the industrial domain and used by dedicated and experienced web developers. It has a steep and long learning curve. I was looking for a cms for a light-weight purpose. I was happy to forego flexibility.