*bump* On Tue, Oct 1, 2013 at 4:02 PM, Prateek Saxena <prtksxna(a)gmail.com> wrote: -- Yuvi Panda T http://yuvi.in/blog _______________________________________________ Design mailing list Design(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design

On 04/10/13 08:44, Pau Giner wrote: Good work, Prateek. Just some quick comments: - *Facilitating input.* For adding categories it may be useful to provide more support than asking to write each category in a textarea line. Although the control can be presented as a text area, it would be helpful that it behaves like the recipient list of many apps<http://i.imgur.com/6agolDj.jpg>(where items are auto-completed and visually added as items and not just text). Calling in HotCat (or mimicking its behaviour, since at its base it's pretty simple) for that would probably be a good idea, since that's the interface most Commoners will be used to using anyway. - *Reducing complexity.* The UI shows all sections at the same level of prominence. If some parts are less likely to be modified (or you can provide good default values) you can make those more compact. Some examples (you need to evaluate the right prominence level according to the real/expected use): - If it is uncommon to provide the tutorial info, that part of the form can be replaced by a "Add tutorial" link that reveals the form part once it is clicked. - Fields asking for user input can be presented in a more compact way while they are not being edited, becoming expanded once the user is editing them. This. There should probably be two differentways the form is handled, though - one for campaign creation, which would emphasises the most importent sections and perhaps collapse less important/less commonly used ones, and one for editing an existing one, which would probably have all the used sections displayed outright, with unused collapsed so that they can either be ignored or added as needed. - *Clarity.* For some fields the placeholder is "WikiText". Although that clarifies that you can use rich formatted text, it provides no information on the purpose of the field. If it is a description it should indicate that it is a description, and it may additionally inform that wikitext is allowed. Hope this helps Pau I'd suggest not using placeholders at all for most of them beyond maybe things like 'wikitext supported' - placeholders disappear when the user starts typing, and most of this stuff will still be relevant after they've already entered something, especially on a complex form such as this. You'll also definitely want the input labels to be labels (as in outside the textareas/inputs) since otherwise when someone goes to edit an existing campaign they'll have no idea what each field actually is. Another thing that I noticed was the on/off mechanism. This actually confused me at first, since what I'm used to for that kind of thing is just a checkbox, which is a more immediately clear affordance that folks tend to be used to anyway from other forms. Nitpicking done, I too hope this helps. Now maybe YuviPanda can unlock these manacles? -I On Fri, Oct 4, 2013 at 8:32 AM, Yuvi Panda &lt;yuvipanda(a)gmail.com&gt; wrote: -- Pau Giner Interaction Designer Wikimedia Foundation _______________________________________________ Design mailing listDesign@lists.wikimedia.orghttps://lists.wikimedia.org/mailman/listinfo/design _______________________________________________ Design mailing list Design(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design

Hey Guys, Thank you so much for the feedback. I am sorry for the late reply, I was busy with client work. Yuvi and I did see some of the problems pointed out by you guys but ignored them for two reasons (1) Its better than editing a JSON and (2) I didn't have any time last two weeks. I do have some time now and will iterate over the design based on your feedback. To sum it all up - * Labels instead of Placeholder text (use placeholder text wisely, where required) * Collapsing and Expanding fieldsets based on their importance and frequency of use * Better copy to guide the user * Well thought of form-inputs for different kinds of data (expanding textareas, radio controls etc) * Slightly different forms to edit and create Campaigns (though this was only for edits) * Stop using the primary button twice (use text for "Add another field") So, Yuvi and me will go over this and fix things and share another version soon. We might be working on the "Campaigns List" page first as Yuvi said it has higher priority. Thanks again for the feedback :) Regards, Prateek _______________________________________________ Design mailing list Design(a)lists.wikimedia.org https://lists.wikimedia.org/mailman/listinfo/design