Re: New Website for opengroupware.org project

Mario Minati <[email protected]>
Newsgroups gmane.comp.cms.opengroupware.discuss.general
Message-ID <[email protected]>
chris h schrieb:

>On June 27, 2005 01:27 pm, Mario Minati wrote:
>
>  
>
>>I think most important is the look and feel of the user interface (not
>>colors but usability)  for normal users, if you are not logged in. 
>>    
>>
>
>Ok. I beleive content is king. Hence zero effort was extended at UI efforts. 
>
>  
>
>>The 
>>normal and unexperienced user must be guided. That was primarily my
>>concern when I thought of a wiki. You have a start page where you could
>>decide which topic of the contents you would like to browse and than you
>>have many interconnections where you can find more informations and
>>backlinks to related pages. Can you realise that with Plone?
>>    
>>
>
>sure. have a look here. http://plone.org/documentation 
>the next rev of the docs site has that structure planned as soon as 2.1 goes 
>gold with the related projects to duplicate this structure. 
>  
>
I checked that site. Three issues:
- It feels a little slow. It would be interesting to know what server is 
delivering the content (Squid or Plone).
- I don't like this kind of layout, maybe it reminds me much of an 
explorer and not of a website, but Helge said already that the look of 
the menu should be preserved for the website. I think that can be 
accomplished somehow.
- I didn't see any backlinks. (For me backlinks is: "Which page 
references this site")

>  
>
>>At the 
>>moment everyone is submitting some context but there is not linkage
>>between, which is beeing done almost automatically in a Wiki. My only
>>chance is to search and if I use different terms than the author I won't
>>find any information.
>>    
>>
>
>two points. Use the search and extended search feature as its a complete text 
>search function. 
>  
>
1. terms problem
2. user might get the feeling that he can't get the imformation his 
looking for right away. I would prefer a well organised structure where 
the information is sorted in. I think some kind of tree where the 
information is getting more specialised when you go downwards, like the 
concept of the manual, with links between similar sections.
(Sorry for all this "user might think" stuff, beside my normal job as a 
lighting designer i am a psychological consultant, so usability is one 
of my main concerns.)

>Linkage between documents is available however most contributors have not used 
>that functionality. the feature exists if users were to use it,
>  
>
You mean it exists already? Than it might not be used because it's 
compilcated to use or the user just is to lazy do use this, becuase he 
just wants to put in the information and has no concept to which pages 
it could be linked (that is what the wiki does for you) or the user 
simply doesn't  know.

>Some history. docs.opengroupware.org was setup very early in projects history 
>to gather needed information. I would agree with you that its time to upgrade 
>the user sites. 
>
>However correct me if I am wrong here. I though you were working on 
>opengroupware.org which is maintained by Skyrix not the community. docs and 
>manuals.opengroupware.org are community sites.
>  
>
The main website opengroupware.org is what Helge has his focus on at the 
moment, but in my first ideas I thought of a complete solution for all 
websites. I think the docs site belongs in the ogo homepage. The dev 
section can be seperated, but it would be good if it is the same system, 
so that it could be administrated the same way/by the same people.
The manual site is only one where I have problems to imagine as a wiki, 
all other pages could be realized as wikis.

However we should find out what is best for ogo regarding 
speed/usability/maintainence no matter if plain wiki or plone.

Mario
-- 
OpenGroupware.org Discussion [email protected]
http://mail.opengroupware.org/mailman/listinfo/discuss
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.