Slashdot Log In
A Good Style Guide Under the Creative Commons?
Posted by
ScuttleMonkey
on Friday February 29, @04:12PM
from the build-something-that-doesn't-suck dept.
from the build-something-that-doesn't-suck dept.
eldavojohn writes "I've been charged with making a specific user interface style guide for a suite of software by my employer. I'm not quite sure where to start. So I turned to my favorite search engine only to be brutally disappointed with what is out there to help me. I'm a software developer but have not had any formal training in UI design or look and feel. I'm looking for something more than just "keep it simple, stupid." I'm looking more for something that is specific but not technologically dependent. This doesn't have to be a global standard, merely a document that illustrates how one would effectively describe look and feel. Does anyone know of such a guide either created by an organization, government or company for their own uses — possibly one even released under the creative common license?" In addition to just documentation, what other UI advice can Slashdot readers offer in order to ensure quality development?
Related Stories
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
And what's so wrong with ... (Score:2)
Apple Human Interface Guidelines (Score:5, Informative)
Re:Apple Human Interface Guidelines (Score:5, Informative)
The KDE Usability Guide [openusability.org] also has some good material, although at this time it looks much less mature than the GNOME docs.
Re:Apple Human Interface Guidelines (Score:5, Informative)
For an introduction to UI design, here are some good resources:
Not really sure what you're looking for, but... (Score:5, Informative)
GNOME HIG
http://library.gnome.org/devel/hig-book/stable/
Apple's HIG
http://developer.apple.com/documentation/UserExperience/Conceptual/OSXHIGuidelines/XHIGIntro/chapter_1_section_1.html
Re: (Score:3, Insightful)
Gnome is consistent and very usable - so their guidelines seem to be working. I'm not sure what your complaint is.
Re: (Score:3, Informative)
Only with itself ... the order of buttons on dialog boxes is f*cked up. For example, in the GIMP : Create a New Image, the order is [Help] [Reset] [Cancel] [Okay]. Last I looked, this was an LTR (left-to-right) locale.
Re:Not really sure what you're looking for, but... (Score:5, Informative)
Except Windows, where the default action is in the middle (i.e. the hardest to find possible choice):
Windows Dialog [georgetowncollege.edu]
Or Mac OS Classic, where it works just like in Gnome:
Mac Classic Dialog [georgetowncollege.edu]
Or In Mac OS X, where it works just like in Gnome:
OS X Dialog [primarysou...arning.org]
I can't find a screenshot, but KDE seems to work like Windows.
I still don't see what the problem is here. There are two common ways of doing it. Mac and Gnome do it one way, Windows and KDE do it the other. *shrug*
Re: (Score:3, Interesting)
No you don't - the rightmost button is the 2nd, or 3rd, or 4th, or whatever - it varies with the number of buttons.
Putting the default as FIRST would mean always hitting the same lo
Some suggestions (Score:5, Informative)
Know the author Ed Tufte [edwardtufte.com].
Know what HCI [wikipedia.org] stands for.
Know your audience and let them evaluate Throwaway Prototypes [wikipedia.org].
If you are looking for a book to teach you UI design, you are misguided. If you are looking for a Creative Commons and/or Open approach to UI design, register a domain called "Principles of UI Design" and launch a Wiki on it, then license it with the license you desire (but I would recommend CC0).
If all goes well, this thread will serve as a good starting point for getting ideas/content to populate your new Wiki with.
Re:Some suggestions (Score:4, Insightful)
I think the ribbon has been unfairly criticised since it became public. It eliminates the redundancy of having both menus and toolbars with the same commands in them, and makes better use of the space on the screen.
To be clear, I'm generally a critic of Microsoft, since they can be trusted to act in their own interest no matter how much they try to make it seem otherwise, and I've never used Office 2007 before. Despite that, I disagree with the ribbon bashing bandwagon people seem to want to jump on - there's plenty of legitimate things to criticise about Microsoft, no need to latch onto something that is actually a good idea. Also, this isn't directed at the post I'm replying to specifically, it's more of a generic rant about ribbon bashing.
Your Platform/Toolkit's HIG (Score:3, Funny)
Wrong question... (Score:3, Insightful)
You don't know where to start because you don't work as a tech writer!
Tell your tightwad boss to pick someone more suited to the task - Even the weenies in Marketing can probably do the task better than an engineer (unless you just happen to have a background in technical writing, but it sounds like that doesn't fit into your job description/requirements).
Geeks can do anything - That doesn't always make us the best person for every job even tangentially related to "computers". If you want me to design a website, I can make it do anything HTML supports, but prepare for a color scheme that makes most people's eyes bleed...
Re:Wrong question... (Score:4, Interesting)
When geeks design a Style Guide, it looks like this [ieee.org]. Simple, elegant, uncluttered.
When the weenies in Marketing design a Style Guide, the audience ends up trying to punch a psychedelic virtual monkey. Please don't suggest anything that would put marketing personnel in a position to produce anything that will guide me, thankyouverymuch.
Have I got a job for you (Score:3, Funny)
That would make you the perfect Microsoft employee.
A Great Brochure (Score:3, Insightful)
http://www.humanfactors.com/downloads/guistandards.pdf [humanfactors.com]
Page very close attention to page 14. It describes your situation as "Pitfall #4." And it's right.
Curly Brace OK/Cancel (Score:3, Interesting)
Try this HCI web comic, I don't think it is updated anymore but there's lots of great archives:
http://www.ok-cancel.com/ [ok-cancel.com]
Don't re-invent the wheel (Score:3, Insightful)
Start with Facebook... (Score:3, Insightful)
Then work with real users and find out what they want the app to do, how they want it to do it, and assess what their knowledge and skills levels are. In all likelihood you are entirely the wrong person to judge what's appropriate for end users.
Usability Guide (Score:4, Informative)
Hopefully this helps.
I'm not a UI Designer but I play one on TV (Score:3, Informative)
Then your proper response is, "Are you sure you want me to do this? I have no training in this area."
And put it in writing as a CYA.
Do you understand what you're being asked to do? (Score:4, Insightful)
I have a feeling that 99% of the replies here are misundertanding something crucial. And so is your employer, and so are you. (OK, so it's more likely I'm the one who doesn't understand. But hear me out.)
First off, what is a style guide?
Here's how I would define it.
A style guide is a document which prescribes standards for subjective matters of presentation, which are to be followed for material created within a specific framework. For example, the material might be written articles for publication in a newspaper. Or the material might be programs created to run on an OS, or with a GUI or application framework. Or C language source code written to be read and modified by a programming team.
A style guide's purpose is to enforce consistency among material created by multiple parties (or one party over multiple sessions). This consistency is for the benefit of the end user, not necessarily the creators. And the style guide is for use by the creators, not the end user
A style guide governs presentation, not content. Grammar and article length, not viewpoints or what gets discussed and what doesn't. How a pushbutton looks and behaves, not how it gets drawn on the screen. Code indentation and naming, not what the program does.
A style guide does not prescribe standards that are enforced elsewhere. It doesn't tell writers to properly end their sentences with punctuation, because that's a rule that applies to all writing. It doesn't say that scrollbars in a GUI should not be placed at 45-degree angles, because the GUI API provides no means to do so anyway. It doesn't say that curly braces must be balanced, because the compiler will catch that anyway.
A style guide is the sole authority on the issues it covers. If an issue within the domain of the style guide is not governed by it, then there is no rule on it.
A style guide prescribes standards as the preferred choice among various possible options, none of which is objectively correct or incorrect. The standards take the form of "for such-and-such, do it this... way, not that... way. There are some who do it that... way, but we do it this... way because such-and-such."
A style guide can not be legitimately created by someone who doesn't define the standards in it, and have the authority to decide what to prescribe.
So, if your employer is asking you to make a UI style guide for their software, there is a basic issue that you haven't explicity made clear:
Does this software provide a framework for creating material that should conform to some standard? You say you are creating a user-interface style guide, so is it a user-interface creation tool (or something that allows external components with their own user interfaces)? If that's not what your software does, and the user-interface you're referring to is something that your software uses, rather than provides, then your company is in no position to create a style guide (that is, define standards) for it. Whoever created the GUI (Windows? Mac? QT?..) has already done that, and chances are they've published it, and your software engineers have been following it. Any attempted style guide would be merely descriptive, not prescriptive. It would say "for such-and-such, our software does it this way...", possibly even while the actual standards say to do it that... way.
Now if your software is in fact a UI-creation tool and it's already been created, then allthe content that needs to go into your style guide is already in the heads of, or has already been written by, whoever created the software. You know who to talk to.
And if the software is UI-creation tool but you're still at the design stage, then what you're being asked to do is actually create the standards, not just write a document. Your employer is asking you, a software engineer with no UI expertise, to define the rules which all of your customers, as software developers, will be mandated to follow, and which will in
Re: (Score:3, Funny)
Re: (Score:3, Funny)
Signed,
Chester W. Lampworth
President and CEO
Amalgamated Manure, Inc.
Re:Hire an artist. (Score:5, Insightful)
Creating a good interface is about FAR more than just pretty pictures. An artist might make it look good, but looking good and being functional are not related in any way, shape or form. I've seen art houses produce UIs that were illogical and violated many basic UI principles but look nice. The worst part is your client will fall in love with the looks without thinking about the damage that is being done.
If you are going to bring in outside sources, there are art houses that have specific UI design experience. You should make sure you engage one of these. Or come up with a design, then have the art house make it look nice.
Real UI design is about user cases, apprentice-master relationships, and other things 99.9% of artists don't know anything about.