Re: KOffice team is looking for webmasters

Hello,

It just came to my attention that the discution has somehow moved away from 
koffice-devel, well it's the problem with cross posting I guess (which is 
evil but was the best way to reach more people that could be interested in 
working on that). I would appreciate though if koffice-devel (at least) stays 
in the loop.

Now I saw a couple of questions in the lists archives, lets try to answer 
them.

An independent website isn't a must have for establishing a brand. If you take 
very famouse brand like Macbook, ipod or windows, their official page is part 
of the Apple or Microsoft website. But when you go to those page the only 
name you see is 'Macbook', 'ipod' or 'windows', mentions to Apple and 
microsoft are put in the background. Yet on those examples, work is done to 
associate the prodcut to the mother brand in the idea that if you use one of 
the product you will automatically want to use the other products, you have a 
macbook go get an ipod. In KOffice, for the 2.x series, we are going to give 
the message that, while KOffice is based on KDE's libraries, you can use it 
outside KDE, you can use it in Gnome, in Xfce, in Windows and in MacOSX (of 
course you will get the best user experience if you use everything from KDE). 
That's the reason why I feel an independent website is a good idea. In that 
aspect the first page of the current site isn't that bad ( To the exception 
of "KOffice is a free, integrated office suite for KDE, the K Desktop 
Environment."), it still show the link to KDE and yet KOffice is what is put 
in front.

As to the question of the relation with userbase and other KDE website. I must 
admit that I don't understand the goal of userbase, I had a look at it, and 
in the application section I see two types of pages, presentation of 
applications (KOffice, digikam pages for instance) and then tips&faq (plasma, 
konsole...). When I first heard of userbase I understood that the idea was to 
concentrate user knowledge in one site, and that the content would be more 
about tips&faq&tutorial&documentation than application presentation. From now 
then I will assume that my first impression of the goal of userbase is the 
correct one, and I clearly see how it fit with an external koffice website.

The koffice website would be limited to a general presentation of 
applications:
* list of key features
* some visual information like screenshots
* release notes
* koffice related news entry

Which is pretty much what the current website has.

Then the "user" knowledge content can go on the userbase website (we currently 
have some in koffice's wiki which should go elsewhere but was there in lack 
of a better solution). Tutorials, FAQ, etc... And of course the koffice 
website would link to that content.

-- 
Cyrille Berger
____________________________________
koffice mailing list
[email protected]
To unsubscribe please visit:
https://mail.kde.org/mailman/listinfo/koffice