A crash course in UX(richoakley.com)
richoakley.com
A crash course in UX
http://richoakley.com/2011/11/a-crash-course-in-ux/
8 comments
We've started doing something similar. We build a lot of sites upon WordPress and upload a basic version of the twentyeleven theme (with a few base plugins) and start getting content populated ASAP, this gives the designers a good base to start from and also highlights potential content-styling before they're a problem rather than the day before go-live.
The design part is nice, but this former HN submission made a stronger point:
http://www.visualmess.com/
http://www.visualmess.com/
Here's a UX tip for him... people click on underlined text. Find another way to highlight content.
Also, he uses low-contrast grey text on a white background (might be better readable on a better screen, but on my shitty laptop it makes things harder to read than necessary) + the navigation links on top have no text at all on them (this might be intentional, due to his server having problems).
I, for one, like my advices best from people with at least basic skills in the area. Or from people who at least try to adopt the things they say/just learned/want to pass on.
I, for one, like my advices best from people with at least basic skills in the area. Or from people who at least try to adopt the things they say/just learned/want to pass on.
In the author's defense, the advice is from a talk by Rian van der Merwe: http://speakerdeck.com/u/rianvdm/p/an-introduction-to-user-e...
The link to MailChimp's "Voice and Tone" style guide was an interesting find. I wonder who their target audience for that site is? New hires? http://voiceandtone.com/
I could see many UGC sites needing something like this as a boilerplate starting point before creating content (or even customer service reps before engaging users). But even if this was simply a publicized internal document, I really like it.
I could see many UGC sites needing something like this as a boilerplate starting point before creating content (or even customer service reps before engaging users). But even if this was simply a publicized internal document, I really like it.
Anyone have a cached version?
http://webcache.googleusercontent.com/search?q=cache:http://...
Might be of help
Might be of help
Being a page on UX, looks horrible. Hopefully the orignal was better?
Edit: Reader on Safari makes it not-so-bad.
Edit: Reader on Safari makes it not-so-bad.
[deleted]
I rather mucked up their nice ganntt chart by insisting that content entry was bought way forward, before the site design was signed off. "Lets the get the content types defined and get some real content in there - give me any kind of cobbled together basic back-end you can" then we can see how the designs work with real content.
It actually worked very well - and avoided the death march at the end of the process where you have to port all the old content into the new system at the last moment.