implication of removing portal_skins
Nathan Van Gheem <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <CAL8hw9GXZFsL6whDQLwbkT8EJxN4mRQmS5e_0a7=an8R5ixE=w@mail.gmail.com> |
Hi all, Kim Nguyen is wanting to take up the effort of making sure we fill the functionality hole correctly when we remove the use of portal_skins in Plone 5. He, and many others, are concerned that doing quick edits on functionality in plone will become very difficult with the removal of portal_skins. When managing MANY sites, as he does, being able to do quick edits through the ZMI is very important to the power of Plone and his deployment. Kim created a document with his concerns enumerated and asked me to respond. I have, and we've now put that document, unlinked, in the collective developer docs with the idea of the document eventually morphing into a howto on doing things the "plone 5" way without portal_skins. The document is located at: https://github.com/collective/collective.developermanual/blob/master/source/misc/plone5way.rst Warning, my responses are NOT assumed to be the absolute correct response. These are just things I've thought of right now. Please, if you can explain things better or know of a better way, modify the responses. Also, this is no a place or a discussion of why portal_skins is bad or wrong for the future of Plone. We've had that discussion, done :) Thanks, Nathan ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev _______________________________________________ Plone-developers mailing list Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org https://lists.sourceforge.net/lists/listinfo/plone-developers