Usability review
| Project: | Embed widgets |
| Version: | 6.x-1.x-dev |
| Component: | User interface |
| Category: | task |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | closed |
Jump to:
I tested the module as you requested (http://groups.drupal.org/node/13738).
My compliments for requesting a review!
You find my experience below a I went through the configuration pages step by step.
My general conclusion is that you need to explain the concept of the module more that you already do. 1. The three step process of Source - Widget - Using the code. 2. Explain what Sources are, what a Widget is and how to use the code. 3. Show examples of ready widgets. The screenshot on the project page catches the eye, but does not reveal any usefull information. You probably want to show the widget code at the bottom, but there is too much noise in the picture distracting me from it.
I hope my review is useful to you. Feel free comment.
The review:
Project page
Could use some more information on what the module can do for me. What it can a what it can't.
Help page
On the help page "... and then copy the embed code." raises a question. I guess it means to say "... and then copy the embed code into ...."
Adding a widget Adding a source
admin/build/embed-widgets/sources/add
No need for the fieldsets to be collapsible
The description of the Source Information does not tell me a lot. Title and description are relatively self explanatory. What is still on my mind at this place is the concept. There was something of a three step approach ... does this "... that are availabe to be added to widgets." refer to this? Please emphasize on this.
Us a short checkbox title and the current title as description ("Allow users to add this source as a tab when customizing their widgets.") Is this about the way the information of the widget will appear as a tab or as plain text??
Only now I think to understand something of the concept. This page is about the 'source of information' that a future wdiget will use. hmm
Add a widget
No need for the fieldsets to be collapsible
I just skip the 'Google gadget' the 'IFrame' and the 'Widget theme'. I do not know what they mean or do in this context.
Descriptive text of Backgound color
'Enter a color as a hex value.' This could use an example, perhaps even a link on how to obtain the hex value. But this may need some testing with the intended target audience of the module. I don't need it myself.
'This will be used as the background color for the widget.'
Shorter: 'Background color for the widget.'
Even shorter: 'Widget background color.'
The list of source/widgets
Very handy this preview option.
Hmm, I get a white screen :( (admin/build/embed-widgets/10/view). Perhaps because I did not check 'Google gadget' or 'IFrame'.
Edit widget
Descriptions of input field can be shortened. This improves read/scannability.
Some suggestions:
'Lists the author of the gadget.'
Shorter: 'Author of the gadget.'
'Provides the gadget author's email address.'
Shorter: 'Gadget author's email address.'
'PNG is the preferred format, though GIF and JPG are also acceptable.'
Shorter: 'Allowed formats: PNG, GIF and JPG' Is it so important to mention a preferred format? If it works, it works ... ;)
View the Multi-Widget
Ah, I now understand this tabs setting I had in the Add source page. It realy looks like tabs.

#1
Had a quick look at the module. I did not even investigate deeply what your module does at all. So this review is from a standpoint of a passer by who sais: this might be interesting, it has the name Google in it. I don't even know what Google widgets are.
Well, the issues I find are those that apply to almost any Drupal module, but yours is new....
When I come to the "Embed Widgets" Page, I'd like to have some introduction or visual representation what this is all about. What I really liked and spontanuously understood is the Glossary. Nodes are ordered alphabetically in a nicely browsable Interface. Good.
The mini widgets are way too small to be useful. So your module does allow to embed any Google widget? Cool.
The edit forms are also typically Drupal: Just vertical arrangement of fields whith no visual hints at what they're for. I warned you about critique that was true for any generic Drupal module ;) Only module I know that tries a different path is Views 2 and partly Panels2 and also partly Imagecache 2
A link from my side, which has influenced my greatly and I just read two days ago:
http://mpt.net.nz/archive/2008/08/01/free-software-usability
Hope this is helpful ;)
#2