The results and main findings, btw, of those user tests I mentioned in my reply to Matt's feedback, can be found here:
http://wiki.magnolia-cms.com/display/UX/User+tests+on+Feb+10%2C+2010 Unfortunately, I can't make the recordings of this session widely available, sorry. Cheers Andreas Am 13.02.2012 um 18:20 schrieb Andreas Weder <[email protected]>: > Hi Matt, > > thanks a lot for your feedback. You'll find my remarks below. > >> As you requested, here are my initial thoughts: >> >> 1. I have to admit, it took me a moment to figure out that I had to click on >> an area to get the edit bars to show up. Once I realized that, I really >> liked it. Something that may help, would be to add hover & focus states to >> the editable regions, both states could just add an outline property around >> the component. I think this might also help to distinguish between what >> regions are editable vs. those that aren't. For instance, the Table of >> Contents on the Large Article page isn't editable, hence, it wouldn't get >> the hover & focus states. > > What you experienced is also what our user tests have shown. One of the last > things we did before testing this snapshot and releasing it for you to > comment on, was to turn off area bars on the top-level. The tests have now > shown that this change was too aggressive. Our users felt somewhat lost > having to edit a page without any bars at all. And, clearly, we do not want > that editors have to click on every visible component in order to find out > what is editable and what not. > > What we plan to implement 4.5 is: > - to show top-level area bars if you enter a page. > - maintain both the position and the selection state of components during > page reloads. > > The latter should properly bring you back to where you where when you started > your last edit and right before the page reload. > > The reason why I do not want to introduce hover states currently is two-fold. > For once, I believe they won't solve the problem: you still have to move the > mouse over the entire page to detect what's editable or not. I prefer to have > a clear "call to action", so to say, in the form of a visible bar. In fact, > that's also what some users have suggested. > > Second, hover is new and not connected to the existing way of editing. We've > already introduced a number of visual changes and if it is not absolutely > necessary, I'd like to avoid introducing another element to the set. > > 4.5 is supposed to be an important step towards Magnolia 5, while still > remaining true to what users know from the 4.4 family. We tried to clear-up > the fog of bars and rework templating, readying it for the future. Magnolia > 5, on the other hand, has the goal to make things more tangible in general. > The main and mostly only focus of Magnolia 5 is the UI. We'd like to deliver > a more direct interaction with your content and with the tools allowing you > to work with it. Intuitively, to me, hover belongs to Magnolia 5, if we'll > ever introduce it at all. > > >> 2. I really like the 'New Component' placeholder. One thing I'd suggest >> would be to make the entire 'New Component' placeholder clickable, instead >> of just the 'Add' button. > > Absolutely. Every user in our tests (double-)clicked on the placeholder. > We'll add that. > > >> 3. The '+' to add another tab item to the Tabbed Teaser component may be >> easily missed. Not sure I have a recommendation for this. For reference, >> see the Tabbed Teaser component at the bottom of >> /demo-project/multimedia.html >> 4. I really like the other placeholder areas :) > > Great. Placeholders, btw, are automatically injected, but you can also > provide your own HTML/CSS to style them. So, theoretically, we could use only > the "+" tab here (and no contained component placeholder) to add a new tab. > Likewise, in the carousel on the home page, we could supply a (+) button next > to the numbers for switching panels, allowing you to add a new teaser > directly. > > However, if I remember correctly, the problem we currently have here is that > the tabs are generated using JS. We thus will have to also add a way to > programmatically add a placeholder as well - and I'm not sure if that will > make it into the final release. I'll have to double-check this last point > with Philipp, however. > >> 5. I really like that the title of each component is shown in the edit bars >> (i.e. Internal Page Teaser) > > Glad to hear you like them. We've aligned all labels on all bars on the left, > so that you can skim them quickly from top to bottom. The buttons are all on > the right, with the more destructive "delete" operation slightly set off from > the others. The current plan calls for the removal of all buttons from the > bars in Magnolia 5 and to make the bars more interactive (e.g. you just drag > and drop the bar to move a component). > >> >> Ok, that's what I have for now, I'll try to add some more to this list as I >> work with it more. I think content authors are really going to like these >> changes! Thanks for the awesome work! :) > > Thanks a lot, Matt, and keep your suggestions and feedback coming. We really > appreciate it. > > Cheers, > Andreas > >> >> Cheers, >> Matt >> >> -- >> Context is everything: >> http://forum.magnolia-cms.com/forum/thread.html?threadId=939ca472-a01f-4178-a619-0b25aa5c3647 >> >> >> ---------------------------------------------------------------- >> For list details, see: >> http://www.magnolia-cms.com/community/mailing-lists.html >> Alternatively, use our forums: http://forum.magnolia-cms.com/ >> To unsubscribe, E-mail to: <[email protected]> >> ---------------------------------------------------------------- > > > > ---------------------------------------------------------------- > For list details, see: > http://www.magnolia-cms.com/community/mailing-lists.html > Alternatively, use our forums: http://forum.magnolia-cms.com/ > To unsubscribe, E-mail to: <[email protected]> > ---------------------------------------------------------------- ---------------------------------------------------------------- For list details, see: http://www.magnolia-cms.com/community/mailing-lists.html Alternatively, use our forums: http://forum.magnolia-cms.com/ To unsubscribe, E-mail to: <[email protected]> ----------------------------------------------------------------
