ok. I have been working almost a whole week adoing different designs to acomodate different needs, the last being this[1] one and I'm a bit tired of it.
[1] http://omploader.org/vc2Q4 I want to know what is going to go into the website. Honestly I don't care if we use submenus or menus, if they are horizontal or vertical, or if the home page has a news blurb or a three colums RoR style. The reason I'm doing this design is purely egoistic. To build myself a portfolio in case (god forbids) I have to work as a web developer to feed my cats. Not having control over the content of the site is actually part of the excercise. I would like to either see some agreement about what would be the general parameters of the site. Or we can just elect a dictator and let him decide but I wont be doing more design until this parameters are set. ======= Prameters ======= * Which theme (feeling like...) will the site have? * How many sections will the site have? * Will we use submenus and subsections? * Will the menus be horizontal, vertical, or a mix of both? * What will the contents of the home page be? * What will the contents of each sections be in generic terms? Will they have adverstiment-like introductions or a plain content summary? ========== My suggestions ========== * Which theme (feeling like...) will the site have? It should feels like the b_and_w theme. * How many sections will the site have? I think the user should be able to access any pages of the site from any other page on the site but in a way that does not overwhelm the user. I suggest to place ALL the possible options in the header like I did in [2] split in 4 categories that are hidden or shown depending on a mouseover effect. This mouseover effect should be CSS only as it is in [2] outdated browsers (ie6 and previous) should see all the options available. The navigation in [2] covers all the pages available in the current website: Main, Planet, About, People, Tracker, Download, Wiki, Manuals, Api Reference, Forum, Mailing List, Exchange. * Will we use submenus and subsections? I don't think that creating subsections for each of the 4 areas is necessary. This means I wouldn't do a home page for "Community" or "News". * Will the menus be horizontal, vertical, or a mix of both? I suggest using the same or similar to [2]. Keeping all the navigation options in the header and separated from the options on the content, like the options provided by the wiki. * What will the contents of the home page be? A brief description of the project with links to media (screenshots, screencasts) that represent the development libraries and the desktop shell in their latest state. Then a news blurb, by placing all the possible options on the menu we make the RoR colums redundant. * What will the contents of each sections be in generic terms? Will they have adverstiment-like introductions or a plain content summary? As I said I don't think its worthwile to implement a home page for each section like "Community" or "Documentation". [2] http://one.xthost.info/dresb/ ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ enlightenment-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/enlightenment-users
