This unique guide to Plone covers everything from installing Plone (on Mac OS X, Windows, and Linux) to writing code for the system. As part of the Apress library of Python programming and content management tools, The Definitive Guide to Plone is authored by a member of Plone's core development team, Andy McKay.
He emphasizes the customization of Plone and shows how to fully integrate Plone into an existing website and application. If you want to adopt Plone for some or all of its features, pick up this invaluable reference and start learning right away!
登録情報
|
この商品にタグをつける(詳細)タグは、商品との関連性が非常に強いキーワードまたはラベルのようなものです。
タグにより、すべてのお客様がお気に入りの商品の整理と確認を行うことができます。 ※タグは初期設定で公開になっています。詳しくはこちら |
Appendix A の Global Defines in the Main Template もまとまっているため、繰返し見ています。
コードから入るほうがいいという人には Appendix B の Code Listing を見て、これは!?と思ったものから本文に戻ると、英語をいっぱい読まなくても該当するアイテムに到達できる(笑)と思います
なお、英語のレベルはそんなに高くなくても、Zope, Ploneを多少知っていれば読めると思います
I started using Zope almost 2 years ago, and I discovered Plone in its early stages when looking for something that worked out-of-the-box. It is easy to install a Plone site, but it is not so easy to customize or build around Plone without some fundamentals. Andy McKay solved this problem and others for me creating The Definitive Guide to Plone.
I bought the book last week, and I have read all 13 chapters and skimmed through chapter 14. I had previously read a fair amount of documents and howtos about Plone and Zope, such as the Zope Book, Plone Book (covering version 1), or "Zope Web Application Development and Content Management." However, I could not understand fully how Plone 2 used different technologies, and I was somewhat confused. After reading "The Authoritative Guide to Plone" I feel confident about what is really going on behind the scenes or at least were to look for answers. As a consequence, I believe that I can experiment and develop new products on my own the right way. The book covers every aspect I was looking for with detail and even some extra aspects I did not know about, these provided the necessary structure to my perceptions about Plone.
The content of the book is valuable taking into consideration both Windows and Unix-like users. The book's content, which includes practical connections between different subjects, flows with a thoughtful structure, and it moves to broader concepts after reviewing the fundamentals. McKay does a outstanding job exposing the material. There have been several "what-if" situations about which I had been wondering, but McKay covered successfully those scenarios a couple of pages after. I appreciate McKay's design considerations, such as "sometimes metadata can't contain everything, but it's worth considering in the design (p. 343)," pointers, such as "Overall, most of the Plone development team has adopted Archetypes as the way to develop products (p.388)," experiences, such as "I've stored more than 100,000 objects in BtreeFolder (p. 417)," or advices, such as "My advice is to put as much logic into Python as possible and keep page templates as simple and as clean as possible (p. 149.)
Overall, this book is the source to find authoritative and consistent answers about Plone. I would recommend this book to any Plone user or anyone interested in implementing a Content Management System (CMS).
|