Re: implication of removing portal_skins
"Wohnlich, Eric (IMS)" <[email protected]>
| Newsgroups | gmane.comp.web.zope.plone.devel |
|---|---|
| Message-ID | <[email protected]> |
For the record, I tend to side with TTW configurable being an anti-goal and it is something I only rarely use and even then only temporarily. But we run 100+ portals on the same Zope instance. They just have very different user groups and content but I want all configuration in code so it can be versioned/etc for the sake of stability. I don't understand why TTW configurable is being conflated with running multiple websites - if you are just trying to make a point about design decisions that seems an awkward one since it's about 10 years too late. Eric -----Original Message----- From: Wichert Akkerman [mailto:[email protected]] Sent: Wednesday, July 03, 2013 3:50 PM To: Nathan Van Gheem Cc: Plone Developers Subject: Re: [Plone-developers] implication of removing portal_skins On Jul 3, 2013, at 20:42, Nathan Van Gheem <[email protected]> wrote: > Just because we say we want to focus on one sector does not mean to abandon the other. Sometimes goals are just not compatible. For example I strongly feel that a Zope instance should only run a single website and that configuration should be in configuration files and not in databases, which is why I dropped all use of plone.registry, ZMI properties, local component registries, etc. in favour of z3c.appconfig. That allowed me to make things a lot simpler and manageable by normal admins without any Zope knowledge, but I had to abandon other things. My main point is that you need to have a single target audience in mind for all roadmap decisions, and I feel that that has been missing so far. Which customisation options make sense will depend strongly in your target audience. For enterprise-style usage TTW configurable is probably a strong anti-goal, while it would be very important for people who run 500 simple sites in a single instance. So depending on who you want to cater to you will need to make different design decisions. Wichert. ------------------------------------------------------------------------------ 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 ________________________________ Information in this e-mail may be confidential. It is intended only for the addressee(s) identified above. If you are not the addressee(s), or an employee or agent of the addressee(s), please note that any dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this e-mail in error, please notify the sender of the error. ------------------------------------------------------------------------------ This SF.net email is sponsored by Windows: Build for Windows Store. http://p.sf.net/sfu/windows-dev2dev