Hi In this point, i wish to share my experience about site. One step before to give a general context of what i will speak.
In Brazil, we had problems with the brand "OpenOffice", because a company already registered the brand some years(1998) before of OOo(2000), so we changed the name to BrOffice.org. Was I that compiled by ~7 years the BrOffice for brazilian users. In there time, the federal gov had a clean support line for open source and open standards. As we had our binaries, problems with mirrors, a different marketing strategy from core, and others, we did the choice of make a CMS (and all other fronts) out of OOo infra. We made a portal only with pt-BR content, where we agregated around 2.2 M of unique users/year and around 12k visits/day. This numbers based in ~90% only from Brazil. ~10% was visits from other parts of the world. Based in this volume, i spoke with an friend - Frederik van Amstel - that is a information architect, and we did a long study of usability of broffice site, comparing with others native lang projects, and with others big projects, interacting with final user, to see a best way to build a site that attempt the colaborative and market requests. This was his master degree work, and source for a new concept of webdesign: "free design". At final, after all problems with the fork of LibO, uncertain of OOo project and all, the reformulation of Broo site was dropped. This was the last status of Broo project[1]. [1]https://speakerdeck.com/filhocf/marketing-strategies-for-developing-countries-the-broffice-dot-org-case Anyway, I believe that is a good idea understand more that a CMS or up some pages. Is necessary to see the user need and how he can interact with our site to find the fast as possible what he wish and return with a satisfaction in use this service, adding value to our desktop product. In this way, i suggest that we see what we wish. Some things that i think are: * support for wide design - from a study of information architecture we can do a draw/mockup and the tool returns our wishes (give easy way to do this draws, like creation of templates); * support for translation - after we see the core content, find an easy way to translate this content for any language; * support for dedicated spaces - e.g. for native langs, i can do a customized space - if is the wish of there local community - to put them special contents, like news, events, etc. If someone have some curiosity about this work, bellow have some references (in pt-BR, unhappily, but some pictures can help to understand). http://www.slideshare.net/usabilidoido/arquitetura-da-informacao-participativa-do-portal-broffice-org http://dl.acm.org/citation.cfm?id=1497501&dl=ACM&coll=DL&CFID=333837345&CFTOKEN=83037928 http://www.academia.edu/656676/Arquitetura_da_Informacao_Participativa_do_Portal_BrOffice._org Best, Claudio 2013/5/29 Samer Mansour <[email protected]>: > Hello, > > I want to start up the discussion with the website work once again since > the logos are very similar and will be picked by next week. > > I have already documented different pages and sites we currently have > running. > > I think we should start mocking up templates, colors, lorem ipsum, colours, > the logo placement, footer, header, etc. We should stick to wireframing, do > not place a lot of work into details or copying content yet. jpeg or png > mock ups are fine. > > We can start brain storming here: > > https://cwiki.apache.org/confluence/display/OOOUSERS/AOO+4.0+Website+Ideas > > Samer --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
