Re: [Gzz] Fenfire WWW

[Tuomas Lukka]

On Sun, Apr 06, 2003 at 03:27:32PM +0300, Tuukka Hastrup wrote:
> 
> Before we get any content at fenfire.org, maybe we should plan the 
> structure. 

Great idea!

> First I hoped we wouldn't need to add the generated pages to 
> CVS, but it seems we can't use an autobuilder like with himalia?

Yes, savannah seems to insist on cvsing the old versions.

> At the moment we can keep the documentation from subprojects in fenfire 
> CVS, but should we plan it so that some parts can be moved away?

Do you mean subprojects as in  libvob, glmosaictext &c ?
They shouldn't go into fenfire cvs at all; we want to emphasize their
separateness, since they can easily be used by others in other projects.
Which won't happen if people just see them as part of fenfire.

> When new visitors come to fenfire.org, I suppose they expect to learn what
> Fenfire is: our vision, current state, downloadable software, screenshots,
> user documentation. 

Yes. 

> I think we should promote subprojects here as well,
> giving a description for each: their vision, their part in Fenfire, their
> usefulness outside Fenfire.

That sounds like the right amount. 

> Project news are nice at the front page, but I hope we could do with a 
> short status report instead of a long list of news like gzz.info, and have 
> the news list as another page.

Not sure - otoh, the front page should be
1) good starting point for people who come there first time
2) not contain too much static content for people who visit regularly

I think a weblog-like approach might be appropriate.

> The main sections of the site could then be:
> * Fenfire - short status report, introduction to the vision

Status report is really dangerous - that can easily be left unupdated
for arbitrary lengths of time. That's why I'd prefer the main page
as a weblog.

Vision should be on a separated page, accessible easily from the first.

> * Vision - explanation of what we plan Fenfire to become
> * Status - what are we tackling at the moment, what's working, roadmap

Again: this is really dangerous. Screenshots and the weblog should convey
this information, if possible.

> * Subprojects - explanation of subprojects, relations between them

This could also be in the vision.

> * Screenshots - pictures of our main features and applications
> * Downloads - Links to currently usable software
> * Documentation - list of articles, user documentation, developer info, 
>                   history

Good... forgot just one: FAQ link must be on the first page. 

So the first-time user would come and see Vision, FAQ and then continue 
somewhere.

> The classification could be fuzzier and pages more granular, if we can get 
> navidoc to produce navigation maps in time.

I don't think it should be too much fuzzier...

        Tuomas