Re: [Muddleftpd-users] General project questions

[Joerg Jaspert]

Kevin Golding <address@hidden> writes:

> Well I was working on the assumption of savannah being the only site and
> was actually quite surprised when I found 1.3.12 hiding out at it's old
> address.  If the tarballs end up matching I'll include a backup but I
> won't loose any sleep if things stay the way they are.

I dont have access at that site. It will remain there until one with
access deletes it. :)

>>Well, just write the homepage stuff and its the one on savannah :)
> Well sheesh I'm doing the FreeBSD port/package already! :-)

Packaging muddleftpd is easy. At least for Debian, but i dont think it
is hard for other systems. :)

>>Uumpf, i probably import the old layout into the savannah project this
>>evening. We can change it later if someone volunteers to do that :)
> Fair enough, suggestions?  Requests?  Favourite fonts? :-)


Requests:
XHTML or HTML4 clean. Transitional or strict XHTML is up to the writer.
No Java/Javascript. Except one little javascript: To escape stupid
brainless framesets from people linking to us.
W3C Validator clean. If CSS is used CSS validator clean.

Suggestions:
It should be readable in *every* browser at *every* resolution. Dont
depend on latest IE/Mozilla/whatever. Yes, in lynx it doesnt look "as
nice" as in Galeon, but it should be readable.
No frames if possible. :)

> Seriously though, if anyone has any ideas about what's needed/wanted
> give a shout and I'll take a look.

Pages:
Summary.
Features.
Documentation.
A FAQ (if someone has questions).
Download (incl. Links to the CVS).
Links to the savannah parts like Bugs, Tasks, etc.

Summary should be the index, having a short summary about muddleftpd
and the people behind it (all, docu-writer, webpage-writer, every
developer) and links to the other sites. And latest news. I dont now if
you can access the Savannah news from your own site, never made a
webpage for savannah. We have to look into the savannah-docu for it. If
not - well, just a link to the news items?

The features is a area for itself, listing everything muddleftpd can
do. Maybe with additional documentation on special features or just a
link to the normal muddleftpd documentation.

The documentation should be a subdir in the webroot. If we use DocBook
or texinfo to write the documentation i setup a cronjob to put the
newest documentation into that subdir, so we always have the
documentation online. (Thats one reason i want it written in
DocBook/texinfo :) ). The features site can then link directly into the
documentation to show docu for related items.

FAQ should be maintained as DocBook/texinfo too. Then we can generate
the HTML of it and put it in a seperate file at the homepage.

Links: Hmm, a navbar in all documents maybe.

Thats what i think the website should be structured. :)

Do you want to do it? If yes tell me your savannah account so you can
have access.

I imported a 12 line index.html into the webcvs, stating that
muddleftpd is a ftp server and more is to come, page in work.
So go on. :)

-- 
begin  OjE-ist-scheisse.txt
bye, Joerg                 Encrypted Mail preferred!
Registered Linux User #97793 @ http://counter.li.org
end

pgpCUzAWAcJNh.pgp
Description: PGP signature