Worked on Site Settings: Import/Export Screen.
Site settings changes
|
October 2008 |
|
||||
|---|---|---|---|---|---|---|
| Sun | Mon | Tue | Wed | Thu | Fri | Sat |
| 1 | 2 | 3 | 4 | |||
| 5 | 6 | 7 | 8 | 9 | 10 | 11 |
| 12 | 13 | 14 | 15 | 16 | 17 | 18 |
| 19 | 20 | 21 | 22 | 23 | 24 | 25 |
| 26 | 27 | 28 | 29 | 30 | 31 | |
Round 1 design mock-ups
Design requirements summary
Comments (5)
Oct 09
Nathan Pearson says:
Hi Ashish, A few questions/comments: 1. What does the cancel button do? Can yo...Hi Ashish,
A few questions/comments:
1. What does the cancel button do? Can you describe that behavior?
2. Have you considered swapping the position of the import and export options? I'm not sure it would help much, but would be worth a look. The spacial logic might be more in tune with the user's expectations.
3. The helper texts you've added are different. The import one is lighter in color with a smaller font. The export is darker. What's the thinking for this?
4. I'm not hip to the "admin" title for the tab. Maybe we should call it something else. Any ideas?
Nathan
Oct 15
Ashish Singal says:
1. What does the cancel button do? Can you describe that behavior? Use Case: I h...1. What does the cancel button do? Can you describe that behavior?
Use Case: I have written down the path of the file which I want to import in, but now I decided not to go ahead with import and come back to the initial state of the screen. I can use the 'cancel' button, otherwise you don't know what to do.
2. Have you considered swapping the position of the import and export options? I'm not sure it would help much, but would be worth a look. The spacial logic might be more in tune with the user's expectations.
Changed and uploaded, though I am not sure of what comes first. I have been hearing Import/Export as a term more frequently compared to Export/Import.
3. The helper texts you've added are different. The import one is lighter in color with a smaller font. The export is darker. What's the thinking for this?
The text for Import is helper text and the text for export is descriptive text, therefore different font sizes and colors.
4. I'm not hip to the "admin" title for the tab. Maybe we should call it something else. Any ideas?
I agree, a label of import/Export chimes more with the user for the task associated with this screen.
Oct 20
Nathan Pearson says:
I thought I'd share the igoogle sample I referred to earlier. I have samples fro...I thought I'd share the igoogle sample I referred to earlier. I have samples from other sites if it helps. But it seems to me, this is just simplified enough to make the difference in understanding what the intended goal of the page is. Do you agree?
To be honest, I'm not even sure we should use any other text as helper or descriptions, and if we do, I wonder if the "XML" jargon is helpful or confusing to the end user.
Oct 21
Judy Stern says:
1. So Cancel is for simply erasing the field? I can see a user wanting to do tha...1. So Cancel is for simply erasing the field? I can see a user wanting to do that but maybe it's possible to come up with a simple erase/delete icon to be placed in the field or in proximity to it. (I kind of like the little grey circle with the white x in it on my iPhone, but don't if that's the right thing.)
Oct 21
Judy Stern says:
3. Seems like Import and Export are inextricably linked, at least in terms of pr...3. Seems like Import and Export are inextricably linked, at least in terms of primary use (i.e. most users will not do one without the other). If so, perhaps it makes sense to put the descriptive text at the top of the page, changing slightly to explain the relationship (simply but with enough transparency that an inexperienced user will know exactly what Export/Import accomplishes. Maybe also text, or link to help text, that tells user exactly what to do, e.g. do they go to the "other site" to do the import). Users that don't need the descriptive text ("experienced users") can ignore it, and it won't be cluttering the area in which they're doing their work.
I also agree that it's not necessary (for most users) to clue them into the fact that it's an XML file, and is even somewhat intimidating. (How about about a "Technical details" link that shows info that lets them know it's XML and what the implications for that are?)
Then again, thinking about our less technical users makes me ask the bigger question of why this task ("apply one site's settings to another site") needs to be accomplished in a two step (export/import) process. Is it not feasible to have it happen as a "Copy site settings to/from another site" action? (Apologies if I'm missing something key.) Or perhaps the task isn't one that we ever expect less experienced/less technical users to do, in which case you can ignore most of this comment