The document discusses simplifying Plone by identifying areas that can be streamlined and improved. It outlines a process of asking questions, categorizing issues, evaluating options, and identifying specific things that could be "chopped" or removed. Key areas discussed include installation, branding, content types, behavior, templating, and non-content management tasks. The document envisions future improvements like unified portlets and viewlets, simpler content types defined through the web, increased use of adapters, and avoiding non-content tasks in Plone.
12. Colours/logo Now Custom folder CSSManager DIYPloneStyle Problems Need to know Plone TTW/filesystem cliff ZMI is scary Future? Plone GUI: Front end to customisation registry
13. Branding Now Page template Skin layers Browser views Browser resources Viewlets Portlets Pain! Problems Too many ways No separation between customisation and theming Future? CSS should be enough Deliverance (NG?) plone.maintemplate?
15. Content types Now ArchGenXML Archetypes plone.app.content Problems Need to learn Python Lots of boilerplate ArchGenXML product != custom product Future? Simple schema + view TTW Filesystem round-trip No boilerplate! Specialisation of labour
16. Behaviour Now Skin layer scripts Tools Methods in classes Adapters Problems Knowing where to put it Patterns Zope2 vs Zope3 Future? Adapters! Re-usable behaviours? Introspection Published Patterns ... but you shouldn’t need to do it as much!
17. Non-content management Now Archetypes Custom views Custom Python Problems Performance Consistency API fit Future? Don’t do it in Plone! WSGI SSO Indexing Deliverance Repoze Grok