Typo3 Enterprise Content Management
Several months ago I mentioned an experiment that I was attempting to conduct using Typo3.
The problem, as I noted at the time, was the lack of accessible documentation.
At the time the only book that I could find on the subject hadn't been translated into English, so I was left to my own resources and those of long suffering Tom Doyle from 2Bscene. Tom develops a lot in Typo3, so both he and his team are very familiar with its functions and possibilities. We've been using Typo3 inhouse for over a year, as Tom developed our current site using it.
Fortunately there is now an English translation of the book available, so I got a copy of Amazon this week. Although I haven't read it cover to cover yet (it's close to 600 pages long) I've already made a lot of progress in understanding the internals of the Typo3 system. If only I'd had this book sooner.
The book's authors are all actively involved in the continued development of Typo, so they know what they are talking about. They also do not make any assumptions of the reader, so whether you are a seasoned user or a fresh "newbie" you won't be disappointed.
The book is divided into seven sections, which guide you from basic principles of content management systems (CMS) through to advanced topics, such as extending the system via plugins (extensions):
Typo3: Enterprise Content Management
- Introduction - including an introduction to CMS systems and the Typo3 project
- Installation - fairly self-explanatory
- TYPO3 for Editors - from a content provider's perspective
- TYPO3 for Administrators - more technical aspects
- TypoScript
- Extensions
- Extension Development
- Index
Typo3: Enterprise Content Management


My name is Damian Carvill and I work for Packt, the company that is responsible for publishing the TYPO3 book. I’d like to respond to one of the points that you raised in your review concerning the quality of screenshots, if I may?
We have noted this as a problem and are currently looking into ways of improving them. It is difficult for us to reproduce the quality of screenshots in most technical books because we print our books on demand, which, as far as we are aware, is a unique model for an IT publisher.
Although our individual print costs are higher, we end up saving money by only printing books when they have been ordered, which means we don't have large stocks of unsold books sitting in a warehouse, unused and ready to be pulped. We also sell our books exclusively direct and online, which means our costs are lower because we don't give bookstores big discounts. Ultimately, this allows us to publish books on smaller, niche or up-and-coming software and topics that most traditional publishers wouldn't be able to publish into (because they won't appeal to bookstores or sell enough copies). Hence we can support projects like TYPO3, SpamAssassin, phpMyAdmin etc. and also pay our authors a larger royalty.
The only drawback with printing on demand is that we are experiencing problems with the quality of screenshots due to the print process. We have been spending much of the last year working on ways of fixing this and we believe we are coming close to a successful solution, which will improve the quality of the images in our books.
As an aside, when we publish a book on an Open Source subject, we pay a percentage of all the book sales directly to that project. This allows us to support the Open Source community with the aim of establishing publishing royalties as an essential part of the service and support business model that sustains Open Source.
I hope that helps answer the point you raised in your review :)
Thank you for giving me the opportunity to comment on this.
Damian
Damian Carvill
Packt Publishing | www.PacktPub.com
Damian
Thanks for the explanation.
Michele