[prev in list] [next in list] [prev in thread] [next in thread] 

List:       koffice
Subject:    Re: RFC: Koffice web pages
From:       Shawn Gordon <shawn-gordon () home ! com>
Date:       2000-09-06 0:26:38
[Download RAW message or body]

After an initial talk with my web master, I have a couple of questions. 
Is there a need for a logo design?  This is a big issue, because it is
pricey and time consuming, but it's also important.

thanks,
shawn


Thomas wrote:
> 
> RFC: Koffice web pages.
> 
> The goal of the website is threefold (in order of importance):
> 1) It has to sell the product to newcomers, a first impression thing.
>     What is an internet-community without a website to show what is has.
> 2) Documentation/downloads etc should be available for users.
> 3) It is the frond-end for developers. Filter examples, dtd's should be available.
> 
> 
> The first means that it should shine (I think theKompany website looks about right ;)
> 
> The second means that we should be writing docs. Or recruiting people to do that.
> It also means that a section of the site has to be lightweigt for the documentation.
> Dont forget the download, things like filter-updates need a place.
> 
> Developers corner means more docs, nothing new there. CVS-update stuff, web-links etc.
> Not really exciting stuff really.
> 
> 
> Structure:
> 
> Main page, really slick.
> +- Info about the different software packages.
>     A page/frame or layer per package which displays a short story on the purpose of the package and
>     a set of capabilities.
> +- Download
>   +- Links to mirrors/RPMs/install docs etc.
>   +- Updates of filters
> +- User documentation
>   +- Online manuals (same as in koffice itself)
>   +- FAQs
>   +- User tutorials etc.
> +- Developers documentation
>   +- Who made the stuff, how can you contact us
>   +- Documentation on porting TO koffice
>   +- Documentation of koffice formats for porting to other applications
>   +- Other relevant docs
> +- News page with CVS updates page.
> 
> 
> Technical:
> Do it in seperate dirs so you can bookmark it. (That means no frames..)
> 
> parts/koshell.html
> parts/kword.html
> parts/kpresenter.html
> parts/kchart.html
> parts/killustrator.html
> 
> download/index.html
> download/updates.html
> 
> documentation/user/index.html
> documentation/user/ etc...
> documentation/developer/index.html
> documentation/developer/ etc..
> 
> news/index.html
> 
> 
> For the graphical design (I used to create that, but I spend my time differently nowadays ;)
> I would like to Shawn up on his offer, to create a face for the pages.
> 
> Gerrit, could you look more at the techincal side of things, like implementing the structure
> I mentioned and Taking care of creating/maintaining a package which can be run on unix.
> (and believe me, most graphic designers need that extra help!)
> 
> The desing Gerrit made also has the coloring scema I like, white with a light color. Yellow in
> this case. While I dont want to restrict the designer to much, I think a "passionate" color
> would have to be used to overcome the dull-ness of most sites from KDE. Think a red-line
> or something. As long as it is NOT blue.
> 
> Again: Gerrit I like your work, it is just not what it takes to be an action figure on the web..
> 
> Shawn; if you like I'll draw a scetch of what I wrote in words here, so you can talk to your
> designer in grahpics ;-)
> 
> But first, let hear you guys. Flames, applause ?
> 
> --
> Thomas Zander                                            zander@earthling.net
> The only thing worse than failure is the fear of trying something new

[prev in list] [next in list] [prev in thread] [next in thread]