[Framework-Team] Feedback on New Collections for Plone 4.2

[Alec Mitchell]

I just want to thank everyone for your input on this question.  We
appear to have arrived at a very strong consensus.

Regards,
Alec


On Wed, Jul 6, 2011 at 9:13 AM, Sally Kleinfeldt <sally at jazkarta.com> wrote:
> On Tue, Jul 5, 2011 at 6:56 PM, Cris Ewing <cris at crisewing.com> wrote:
>>
>> On Jul 5, 2011, at 3:53 PM, Jon Stahl wrote:
>>
>> >
>> > My feeling is that very few of Groundwire's existing deployments would
>> > be harmed by disabling adding of Old Collections in favor of New
>> > Collections.  Clear documentation about how to re-enable them would suffice
>> > for the tiny minority of exceptions.  I'd prefer to keep superfluous stuff
>> > out of the Add menu by default.  Alternatively, demoting it to the "more..."
>> > section of the Add menu would be fine, too.
>> >
>> > :jon
>>
>>
>> +1 from me to this.
>>
>> My sense is that anything we can do to fix collections should be done as
>> soon as possible.  In a lot of my work at UW I simply avoided teaching
>> collections to users until I had some idea of their competence level.  The
>> UI for them was complex enough that unless I felt a user had some fairly
>> solid skill level it was easier to just pretend they didn't exist.
>>
>>
>> Cris Ewing
>
> +1 from me too. Collections are so useful, but so hard to teach. Trainers
> and trainees will all be happy to see this improvement.
>
> I do like the idea of differentiating by name on the UI - "Old-Style
> Collections" or "Sexy New Collections" or some such - so people can tell
> what's what. Either Site Setup or the Add menu "more..." seems a fine way of
> re-enabling. And some sort of documentation page or handout that explains
> what happened, why, and how to re-enable would be invaluable, so we can give
> to clients when we do those migrations.
>
> Thanks!
>
> Sally
> --
> Sally Kleinfeldt - sally at jazkarta.com
> Open Source Technology Solutions
>
> http://jazkarta.com
>
>
>
>