I've been asked to review a book. It's called Typo3 Enterprise Content Management, it's about Typo3 and it contains a lot of information.
In this article, I'm trying to find out the focus of the book, the target audience and try to write a bit about its content, too.
About the structure | |
---|---|
Looking into the book, one might notice that the backside-summary of it is pretty accurate. The answer to “What is a CMS” is a whole 2 pages long (the book itself has 595 pages) and there's no comparison to other CMSes. So we can rule out the decision makers. Still, the one page about the visible and hidden cost of Typo3 implementations is nice. We won't find any Typo3 reference sites either, nor does the book describe general content ideas. Like: How long should your articles be, how to structure them, how to market your site, how to design the navigation, how to do search engine optimizations, and so on. Let's have a closer look to the content table.
|
What does that mean? To me, the message is rather clear. The book is written for technicans, who want to deploy a Typo3 site. They might be involved in supporting editors to get their content in and also in programming extensions themselves.
To underline this thesis, let's sum up the pages first.
445 pages are about stuff a regular user (or decision maker or webdesigner) will never need (50p install + 64p admin + 202p typo-script + 14p extensions + 125p extensions developement). That's about 75 percent of the book!
Looking at the content | |
---|---|
I'll continue this review by taking a deeper look into the content. Let's see, wether my thesis holds... |
Comments - Make a comment |
The comments are owned by the poster. We are not responsible for its content. |
AdministrativeTexts
updated by freddiemac1993, 2013-06-14
wiki
Re: adventures
created by brittdavis10, 2012-02-23 (1 rply, 3 views)
thread
Re: how to run phpwebsite...
created by alexander, 2011-08-25 (2 rpls, 3607 views)
thread
Re: Forum tags
created by HaroldFaragher, 2011-08-22 (3 rpls, 8488 views)
thread