Timeline for UX style guide techniques
Current License: CC BY-SA 3.0
10 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 13, 2017 at 12:32 | history | edited | CommunityBot |
replaced http://ux.stackexchange.com/ with https://ux.stackexchange.com/
|
|
| S Oct 6, 2014 at 18:03 | history | suggested | Frank Visaggio | CC BY-SA 3.0 |
broken link for gnome style guide
|
| Oct 6, 2014 at 17:13 | review | Suggested edits | |||
| S Oct 6, 2014 at 18:03 | |||||
| Sep 25, 2012 at 13:36 | comment | added | Sauce McBoss | Thanks @Michael! That's awesome. I really appreciate the updates. Very helpful! | |
| Sep 25, 2012 at 12:56 | history | edited | Michael Zuschlag | CC BY-SA 3.0 |
Addressing questions below
|
| Sep 25, 2012 at 12:51 | comment | added | Michael Zuschlag | See added paragraphs above for the ideal case. In my cases, usually my audience is small, so I’ve used hyperlinked Word .doc format. For a large audience, we once made a website. Wiki technology may make building a website easy. However, normally you’re going to want more control over the product than one usually associates with Wikis. In most organizations, you simply meet personally with just two or three others to decide what the guidelines will be. | |
| Sep 24, 2012 at 20:33 | comment | added | Sauce McBoss | Could you elaborate on how you typically deliver documentation for projects? PDF? Website / wiki? Something else? I like the idea of creating a wiki, and I think it may work well for my purposes. Do you think this may be the right path? | |
| Sep 24, 2012 at 20:25 | vote | accept | Sauce McBoss | ||
| Sep 24, 2012 at 20:25 | comment | added | Sauce McBoss | Thanks Michael, I hadn't thought to look at OS style guides. Also thanks for the reference -- it answers the majority of my question. | |
| Sep 24, 2012 at 20:17 | history | answered | Michael Zuschlag | CC BY-SA 3.0 |