Ticket #8807 (closed Feature Request: invalid)
Plone core should no longer use portal_skins
|Reported by:||hannosch||Owned by:||hannosch|
|Keywords:||Cc:||dukebody, rossp, spliter|
Right now Plone uses both the old Zope2 / CMF way for providing templates, resources and scripts via portal_skins, as well as the new way of Zope3 using browser views and resource directories.
Plone itself should only use one approach. Explaining two similar but not quite compatible stories for such an important part of customizing Plone is not acceptable.
The Zope3 approach has clear benefits over the Zope2/CMF approach and we should move to it for the entire application.
We should ensure that the portal_skins approach is still working, so not all add-ons products have to be rewritten.
A new clear and easy customization story for non-developers needs to be found and the caching infrastructure needs to be updated to support the new approach.
The new customization story is connected to a new theming approach under discussion and development.
Started simplifying the number of skin layers inside Products.CMFPlone to get an easier overview of the remaining work.
Moved default views for standard content types over to ATContentTypes and to browser views.
- Component changed from Visual and templates to Templates/CSS