In general the feel and styling of Typo3 is plain and unimaginative. But just as most every CMS available today, the Cascading Style Sheets can be edited to fix the aesthetic issues. This isn't a big deal to a coder or a business user who is familiar with CSS technology, but other end-users will find it confining. Although several regular contributors do document and release a wide array of "plug-ins" and "extensions", they are very infrequently in a stable state upon release. If you took a moment and visited Typo3.org you would quickly notice the disorganized presentation and massive lack of general information concerning the CMS. In an effort to combat that lack, wiki.Typo3.org was launched, which does a good job of presenting organized information about the CMS which is easily navigated. But one really needs to know exactly where he/she stands as an end-user/developer to find the specific information they'd be looking for.

Overall Typo3 is a run-of-the-mill CMS with a boring initial layout and simple administrative structure. However, instead of being at the bottom of the barrel, Typo3 moves to a hearty top-middle position in my mind by offering a "mounting ability" for folders on the server. Although this can easily be accomplished in many other CMSs, Typo has made it even easier and secure. Kudos goes out to them for this integration, but they should have just made it an add-on or plug-in for another CMS, nto try and create a new solution around a single cool function.