Ticket #13622 (confirmed Feature Request)
Products are difficult to select
Reported by: | anonymous | Owned by: | |
---|---|---|---|
Priority: | minor | Milestone: | 4.x |
Component: | User Experience and Interface | Version: | 4.3 |
Keywords: | Product | Cc: |
Description
As an integrator, I have trouble keeping it all together. After selecting a product that is supposed to work, then this is what I need to do:
1) Add the name and version number of the product to the eggs in buildout.
2) Add whatever slugs and other modifications are needed in the buildout file, which I find more complicated than I would like (why not add a single line + version number somewhere?)
3) Then I need to activate it in Plone (either initial start up screen or in the site setup). However, here comes the next surprise: The name that I carefully googled isn't even visible any more. So I need to be smart and guess, which of the products was which (especially if the list is long). Now I did this in english, but someone told me that all these things are also translated into various illustrous names in other languages (which makes it completely impossible to google what these are supposed to mean for persons that didn't remember (or know in the first place) what the installed product is.
4) Sometimes I then apparently need to click various boxes to activate some products as they seem to have various components. However, without extensive googling I don't know if I have to activate all of them for anything to work or if I get to choose which I can activate.
All this is confusing to me. In order to drive adoption of Plone, wouldn't it be reasonable to simplify this? Here is an idea how this could be encouraged by setting a "standard" for "high-quality" packages.
1) Product developers need to decide on a name. This name will be reused all over, so think about it for a bit to make it a SpeakingName that can be googled.
2) The same name is used all over:
- when determining original installation (in buildout or wherever)
- when actually deciding to use it in the site setup (add a help text to explain it in a sentence)
- on all other relevant occasions (e.g. ZMI? Plone Site Setup dialog ...?)
3) Dependencies are managed automatically: No product should require integrators have to remember to click multiple boxes for everything to work.