> isn't the wiki suitable for this kind of thing? The biggest reason behind my decision to design a website rather than including UX guidelines in the wiki is mostly prettiness. We're going to be telling people how to do pretty and usable apps, we have to give the correct example, and give the UI designer the inspiration and motivation to create beautiful and easy to use applications.
The second reason is that this method can easily be worked on little by little. If we add it to the wiki, some day it will get big, and it will require a lot of work to be prettyfied and published properly. Less important is the ability to add interactive widgets to demonstrate functionality. I liked N9 UX guidelines website very much, (http://harmattan-dev.nokia.com/docs/ux/index.html) and I got my inspiration from there. When I visit that site I feel I want to browse and find ideas for my app. While fiddling around I get to read the guidelines too. Similar websites exist for android and BB10. iOS and symbian have the guidelines more visually integrated with the developer documentation, which gives me the impression that this is a page that I am obligated to read, a set of rules that I should follow, not a collection of good practices that will help me build better software. > Also, in terms of a general Nemo website wouldn't it make sense to use a > CMS? Designing the artwork to make the CMS look original is a demanding job, something I can't do with my present time constraints. As the UX Guidelines website is a separate entity which is usually maintained by a specific set of people, I think it's not a waste to create it now. Later it can be included as a category in any cms (it's pure HTML/js) with minimal effort. Finally, the CMS that will be used must be discussed thoroughly as I doubt a general-purpose CMS (joomla!, drupal) can fulfil the needs of nemo. We should check out all alternatives (midgard comes to mind) and decide before any set-up or adaptation happens. > Besides UX guidelines, there should be other stuff on that site too. This website is created for that sole purpose. See it as a microsite for UX guidelines. We can publish it in a subproject so that it's like nemomobile.github.com/UXguidelines and link to it from the main website. However it would be useful to know what other stuff we need so that I can plan ahead. > One comment: the picture used at "iconography" looks quite frightening to me. Frightening? It's just 3 rectangles. References: http://docs.blackberry.com/en/developers/deliverables/41577/ http://developer.android.com/design/index.html http://developer.android.com/guide/practices/ui_guidelines/index.html http://developer.apple.com/library/ios/#DOCUMENTATION/UserExperience/Conceptual/MobileHIG/Introduction/Introduction.html http://harmattan-dev.nokia.com/docs/ux/index.html http://www.developer.nokia.com/Resources/Library/Symbian_Design_Guidelines/
