Talk:Main Page: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 1: Line 1:
The intro essay is the only thing that makes sense on this page.  Thankfully it contains links to all the good [[starting points]].  So maybe what's needed is just to divide up by [[advocate]], [[developer]], [[designer]] roles?  So that we figure out what people can do for Consumerium, and send them to the right place?
The intro essay is the only thing that makes sense on this page.   
 
:So, of course, sysops delete it, and trolls restore it.
 
Thankfully it contains links to all the good [[starting points]].  So maybe what's needed is just to divide up by [[advocate]], [[developer]], [[designer]] roles?  So that we figure out what people can do for Consumerium, and send them to the right place?


:hmmh. hmmh. Thanks. True. Aren't developer and designer the same thing in practice? Shouldn't that be the other way around?
:hmmh. hmmh. Thanks. True. Aren't developer and designer the same thing in practice? Shouldn't that be the other way around?
Line 6: Line 10:


::Why should the person who chooses the words "Main Page, Recent changes, View discussion", layout and other aspects of the user interface be the same as the person hacking the code?  In general the two skill sets are totally different.  Bad user interfaces like say [[TikiWiki]] come from setting up stupid development cycles where if you can't talk like a developer, you can't be heard about the user interface.  Why do you think Microsoft rules the soft-world?  Because they have Program Managers to design things and mock them up, and Project Managers to deliver them in good debugged code.  There's nothing in common except the "look and feel" between the two jobs.
::Why should the person who chooses the words "Main Page, Recent changes, View discussion", layout and other aspects of the user interface be the same as the person hacking the code?  In general the two skill sets are totally different.  Bad user interfaces like say [[TikiWiki]] come from setting up stupid development cycles where if you can't talk like a developer, you can't be heard about the user interface.  Why do you think Microsoft rules the soft-world?  Because they have Program Managers to design things and mock them up, and Project Managers to deliver them in good debugged code.  There's nothing in common except the "look and feel" between the two jobs.
::A good guide to how to lay out a main page for a meta type discussion like this is at http://meta.wikipedia.org/wiki/Main_Page_style - this style is expressed for Meta-Wikipedia in http://meta.wikipedia.org/wiki/Main_Page_Neutral which is sort of the "users' main page".  A Main Page *HAS TO* give a concrete and specific understanding of a project, and it *HAS TO* provide clear visible up-front links to the values and concepts of the project.  Look at *ANY* non-profit organization's page.  They do *NOT* open with all the wonderful technology they are going to use... or a vague mission statement.  They open with very specific stories and images.


--------
--------
Anonymous user