Hallelujah! The KDE site has quite a new
look! It's been completely redesigned and I like it, thank you very much!
But judge for yourself... Is the new layout better? Is
the new art better? Are things easier to find? We want to know what you think! I asked Kurt
Granroth, the KDE core developer behind the changes, a few questions you might have as well. Read what he had to say below.

I conducted a brief interview with Kurt Granroth, the force behind the new KDE.org
design. Here is what he had to say:

Dre. What motivated the changes to the design?

Kurt. We had two principal objectives in mind. First, navigating the
old
site was a bit difficult. There were too many links on the front
page and things were not organized as well as they should be. Second, we
wanted to switch to dynamic page generation. As it stood it was quite
difficult to update pages, as we did not use templates. Now we are usingPHP and templates so maintaining the
site will be much easier.

Dre. It looks like the look-and-feel has changed as well. How did that come about?

Kurt. The site design had not changed in several years. KDE has changed a
lot in that time and we felt it was time to get a more modern look for the site.

Dre. How long has this redesign been in the works?

Kurt. The idea to redesign has been floating about for quite
some time, but all active development has occurred in just the last
couple months.

Dre. So how did the new design get implemented?

Kurt. Most of the PHP coding, artwork, and layout was done by me,
but it was a highly interactive process. We set up a mailing list two
months ago for people interested in the new site. There was a lot of
discussion and debating that went on, and the result is a consensus
project.

Dre. What about mirror sites? How do they keep being mirrors?

Kurt. The entire site is still available from CVS in the www
module, though it's mostly PHP pages now. All the PHP code is
available under an Open Source license, though we haven't decided on
the exact license yet. For mirrors to be a "true" mirror they will
need to PHP-enable their site and mirror the PHP code. The settings
that are required to use the pages will be available soon.

Dre. What about mirrors that cannot use PHP? Can you make a static version of the site available?

Kurt. We'll consider this. Perhaps we can create a tarball
of the site nightly and let mirrors update their site with that.

Dre. What about other KDE application sites that used the KDE site
design as a template. Are they able to use this new design as well?

Kurt. Absolutely. As I mentioned, the PHP code is freely
available from CVS. Many of the KDE applications are hosted onSourceForge, which supports PHP so
updating those pages should be fairly painless.
Otherwise they can download pages from the KDE.org site and modify the static
HTML to taste.

Dre. So how is the server handling the increased load?

Kurt. Great so far! We are very happy with PHP. Plus the
front page is only regenerated every 30 minutes and served statically.

Well, first, let me say the more I look at the Zope, the more I'm amazed. There's a huge number of third party apps and community support out there, updating the system is a breeze (just drop in a Hotfix, restart, and you're done), the ability to rollback changes (though it doesn't always seem to work) is wonderful. Almost everything can be minutely customized and there's a solution to almost every problem.

One problem: KDE has a long history of storing in and updating the website from CVS. Multiple people can work on the website and keep track of it this way. Zope, by default, however uses some sort of proprietary DB (still OpenSource, of course) that you can't directly access, and so one would have to use the Web interface or the rather clunky FTP interface to update it. The Zope FTP interface is not fail-safe either and doesn't support many of the usual FTP features. A comprehensive script would have to be written to handle the situation. Would it even work? Probably not, but maybe you can correct me.

Assuming that KDE dropped CVS and started the Zope Web interface instead, personally I don't see this working too well with multiple people trying to update and maintain the site.

Second, mirror sites... but we've got a similar problem with PHP. Then again I'd imagine, PHP would be less of a problem than Zope for mirror sites, as PHP is pretty common out there. It's almost the defacto Linux web-scripting platform.

Third, I didn't feel comfortable advocating Zope instead of PHP to Kurt, because after all this time, I still haven't learnt it properly and I still have trouble figuring things out. I'm not generally dense, but I had trouble figuring out some of the Zope syntax/API without reading lots of seemingly inadequate documentation (which sometimes don't help if you don't know Zope basics :).

On the other hand, although I don't know PHP, Andreas Pour has constantly impressed me with how much and how quickly he can accomplish something in it. I get the impression that PHP has a less steep learning curve than Zope and is easier to grasp for someone who just wants to get down to hacking. I'm sure if it came to it Andreas could offer Kurt a PHP solution faster than I could figure out one in Zope. :)

In short, more people around knew PHP and less of us knew Zope. No doubt Zope would have been a great solution too, but the implementation would have probably required a little more effort and possibly outside help (although Kurt may certainly be better at grasping Zope than me). ;)

Navindra answered this pretty well.. but here is the short (and 100% accurate since I made the decision) reason:

1. Zope natively uses an internal database to store the pages. I wanted to keep the pages in CVS. I know it's possible to skip the database.. but that brought me to the second point..

2. I am not very familiar with either Zope or PHP.. but I know a LOT of people in the KDE community that know PHP and don't know of any beside Navindra that know anything about Zope. If I have a PHP question, I can get it answered very quickly. If I had a Zope question, I wouldn't have known where to start.

So in the end, in spirit with the KDE style of development, I chose the solution that worked for me at the time... and it was PHP.

*nod* ... and thats fine. The site DOES look well, regardless. Maybe we can get an IOSlave for WebDAV and XML-RPC/SOAP for KDE, and make accessing the Object Database somewhat easier for KDE Users (I envision managing Zope from Konqueror). Well, at any rate, use what ya know, be it PHP or whatever - just keep up the excellent work!

Or is the Emperor wearing no clothes? This new
site seems really, well, boring and bland, to say the least (like the series finale of Seinfeld). Very functional and sophisticated under the hood, but borrrring.

Oh well, there's no accounting for taste....

> There was a lot of discussion and debating that > went on, and the result is a consensus > project.

Well, sure we could go for something much more flashy with lots of fancy graphics etc. However, we decided a long time ago that we wanted a web site that was quick to load, and that if there was choice between looking exciting and being a no-nonsense way to get to the information you wanted then we would go for the latter. The new design aims to provide a modern look and feel without sacrificing the accessibility of the information.

A lot of sites today are very nice to look at, but are a nightmare to use if you actually want to find a piece of information, we don't want the KDE web site to be numbered amongst them. I think the new design provides a good balance between the two. If people have suggestions for how we can make the site better (bearing in mind the above) then we'd be happy to hear what they have to say.

Please DO remember that the big audience (and the decision makers!) expect a clean, sophisticated website. The site is probably their first introduction to KDE and therefore it *must* look slick and clean. To be honest, I am not too satisfied with the current site. It just cannot compete with the 'company' sites out there and that is a potential loss for us all. Again: you never get the second chance for a first impression...

It's about time! *sigh* Nearly any major player, whether it be open source or commercial, has a decent website. I have always been embarrassed to show newbies that site so I always pointed them to the comercialized kde.com.

Why do you begin the "screenshots" section with screenshots of KDE 1.x? People who come to www.kde.org want to see what's new, not what's old :-)
Also some screenshots are JPG, some are PNG. JPG format is not suited well for screenshots so please don't use it since compatability with old browsers is not your concern anyway.

I quite like the new design, both from a usability and aesthetical POV. The more blueish color looks better than the old violet one as well. My only tiny complaint is, that it could be a little bit lighter and more colorful. Maybe a few lighter and darker shades of that blue here and there?

The new site looks great! Clean and not cluttered; I like that. I would humbly suggest that you put a date on the announcements, though. The KDE 2.0 announcement says, "The KDE Team today announced..."

Of course, clicking thru will reveal that "today" is actually Oct. 23, but it's a bit confusing :) Anyway, congrats on the new site!

Great job, guys! I am so happy about the changes! We have always beaten GNOME with the software, and finally, we have beaten them with our website. I especially like the "Applications" section, so I can stay up to date on the latest and greatest software for KDE. Kongratulations! I was just wondering if the other KDE sites (such as developer.kde.org) will follow the same design as this.

Yes, I really like the new look especially the top banner with Konqui the dragon showing things off. It loads quickly too.

I'm sure the site will evolve more quickly now with the new framework in place, in response to comments by visitors. A little more in the way of fancy graphics might be useful, maybe in the context of stories. Thank God you got rid of the notebook image and the animated gif.

There are two gripes, though.

1. Centering. Since you are using a fixed width page it should be centered in the browser. Currently everything is flush with the left edge and the title banner doesn't line up with the tables below. This is how it looks in the current Konqueror. Not quite right.

2. apps.kde.com. If you are going to link to this site, please get the webmaster there to fix the site. It's horrible. Yes, it does have the apps, but hangs up if you are using a proxy. Doesn't eveyone use junkbuster or something? The default view with 4 (count em) frames puts a strain on any browser, including Konqueror. Switching to the no-frames view usually crashes or hangs up Konqueror and Netscape, placing a recursive view of the entire page in the cetner frame, at least for me, and clicking on app links in the right hand frame often does the same.

I feel that Kde should have its own apps listing anyway and not rely on this commercial site. To me, it's a confict of interests. If you insist on using it for apps annoucements please at least make it usable for those of us who value our privacy and refuse to accept cookies or turn off our filtering proxies.

> 2. apps.kde.com. If you are going to link to this site, please get the
> webmaster there to fix the site. It's horrible.

Hi, I hope we can solve your problems.

> Yes, it does have the
> apps, but hangs up if you are using a proxy.

That shouldn't happen, I myself often use a proxy to access the site.
If somehow you are in the position where it tries to serve compressed
HTML to speed up downloading, many proxies are buggy and can't handle
it. However, the site has a mechanism to detect this and it should
not happen a second time. It would probably be more helpful if the
buggy proxies were fixed, though.

> Doesn't eveyone use
> junkbuster or something? The default view with 4 (count em) frames puts
> a strain on any browser, including Konqueror. Switching to the
> no-frames view usually crashes or hangs up Konqueror and Netscape,

I don't have that problem. Which Konqueror do you use and which Netscape
do you use? I've been to the site thousands of times and my browser has
never crashed.

May I suggest the text option for you? It's quite a bit lighter.

> placing a recursive view of the entire page in the cetner frame, at least
> for me, and clicking on app links in the right hand frame often does
> the same

That's a bug in your browser, hopefully that will get fixed. Once
the 2.0.1 version is out we can start thinking about dealing with
khtml quirks to make things work better, until now it's been improving
too quickly to make it worth it.

> I feel that Kde should have its own apps listing anyway and not rely
> on this commercial site. To me, it's a confict of interests. If you
> insist on using it for apps annoucements please at least make it usable
> for those of us who value our privacy and refuse to accept cookies or turn
> off our filtering proxies.

There is no need to accept cookies to use the site and there is no
need to turn off filtering proxies. It uses HTML just like every other
site, though if your browser says it accepts gzip'd data it may actually try to send it, since it can't know there is a buggy proxy in the way. If you have any particular problems that can't be resolved with
a reload please write me, we are always working to make the site better.

Perhaps the intension with apps.kde.com was to make it easy to navigate, but the 4 (four!) frames just clutters the screen. It would be much better with a unframed version of the app-index as the front page.

Also the listings of the software is too terse. To get a grip about what a software package is about you need to enter the page for that package. Look at freshmeat how to make a informative summary of a package.

Perhaps the intension with apps.kde.com was to make it easy to navigate, but the 4 (four!) frames just clutters the screen. It would be much better with a unframed version of the app-index as the front page.

You can bookmark it that way, if you like, just usehttp://apps.kde.com/indexnf.php as your entry point. Perhaps the kde.org front page can have a sub-link for the no-frames option.

Also the listings of the software is too terse. To get a grip about what a software package is about you need to enter the page for that package. Look at freshmeat how to
make a informative summary of a package.

The only thing freshmeat does is add a "changes" paragraph. IMHO that does not give you a better feel for the app but insted clutters the page. What apps.kde.com provides is the app's icon and the app's documentation, if it comes in the package; though you have to click to view the documentation, I find this information much more helpful in deciding if an app is for me. Which is why we use frames, it makes these clicks extremely fast (including to the screenshots, also not found at Freshmeat, and to the full ChangeLog).

To get back to the Changes paragraph, the way they do that is force developers to provide that information. Once developers start contributing more we'll be happy to include that information :-). We actually refer to it as a "Version Comment".

You can bookmark it that way, if you like, just usehttp://apps.kde.com/indexnf.php as your entry point. Perhaps the kde.org front page can have a sub-link for the no-frames option.

You're right. The non-frames version is much better. I would suggest that you make the non-frame version the default link.

The only thing freshmeat does is add a "changes" paragraph. IMHO that does not give you a better feel for the app but insted clutters the page.

I think the "changes" paragraph is fine, but YMMV. But it was not the "changes" paragraph I
was referring to. It was the descriptions of the packages. I know - by now - that its not your fault, but the developers. But take a lot at this random description taken from the first item at the freshmeat page to see how I think it should be done:

"SkinCat.pl is a Perl script that will decrypt and look up just about anything you can scan with a :Cue:Cat. If the barcode is an ISBN, it will print out the title and author, as listed at amazon.com. It also does lookups on DCNV's database. SkinCat does not send your CueCat serial number anywhere. It is very useful for command-line lookups, and can be used as part of a database-entry system".

...and compare it to this (extreme) example from apps.kde.com:

a radio card tool

Oh, and I almost forgot to tell you: I do like the new layout of www.kde.org. Congrats.

Looks alot better than the old site. However when I load it with Netscape on windows it does not render correctly. The text is too far to the left on top of the blue border area. Its about one capital letter too far left. Other than that it looks quite nice.

Some minor points. First, the color selection on the top links (FAQ | Download | Screenshots | news) when they been clicked on in less then optimal. Red or whatever the color is does *not* work well blue. The links are almost invisible.

Second, the top "cell" containing Conquer your... is not aligned with the rest of the page. It starts at position (0,0), hence it look out of place.

Some minor points. First, the color selection on the top links (FAQ | Download | Screenshots | news) when they been clicked on in less then optimal. Red or whatever the color is does *not* work well blue. The links are almost invisible.

It also seems that some of these links don't render properly in Internet Explorer. Only FAQ, Download, and Contact Us show up, whereas the others are invisible.

"However, we decided a long time ago that we wanted a web site that was quick to load, and that if there was choice between looking exciting and being a no-nonsense way to get to the information you wanted then we would go for the latter. "

You are quite right about that! I always liked the free bsd ( http://www.freebsd.org ) site for those qualities. However, I think the bsd site looks very good while the new KDE site is a bit dense. I like the free bsd colors better, but that is a question of taste - KDE choose blue, ok.

Some points:
- The new site could use some more white. The three blocks that start with KDE is... fill up the space. I keep it simpel, I compare with the bsd site: there the blocks have headers: What is ... Cutting edge ... , etc. Headers make for good reading as have been discovered ages ago :-) People do not read web pages, they scan them (As surveys show.). So give them headers... It solves the problem the site is dense, it makes the info more readable.

- Gis already remarked it could be more colorful. Yes, the blue links on a blue background look quite grey, dull. It is also hard for visually impaired people. This should be changed, if only for accessability.

- The box with the links at the left side takes 1/3 of the width. It does make the links prominent, very good. On the other hand, a 1/3 - 2/3 balance looks dull, not exciting. Changing colors in the links box makes the links better readable, so the width can be brought down. It does not take heavy graphics to make a page look more exciting.

While the free bsd and KDE sites seem to have the same goal (quick to load, no nonsense) the bsd one is very beautiful, the new KDE one is not attractive visually. More close to home: the KDE's iconfactory ( http://www.kde.org/artist/introduction.html ) , while using almost the same style is much better too... While the bsd site is almost provocative in it's use of colors, the iconfactory is within the "corporate look" KDE uses.

BTW, you can use bugs.kde.org to report bugs against our web page, too. The module (if you'
re using email) is called "www". Actually this wasn't used very much in the past, but I like the idea to handle web bugs just as software bugs.

I agree with you. I think I liked the old design better. The new design is boring, ugly and has no apparent structure. I'm soo sick and tired of boxes like the one on the new page, and the top logo looks like a banner.

As you say, the old page had a natural "entry-point" - the laptop. The new one is just an ugly mix of boxes and banners (hrm) that doesn't give me a clue of where I should start reading.

The three paragraphs at the top do not sound right to a native English speaker (the third is meaningless to the point of being embarassing). I know they are the same as with previous version of the site but I complained about them too ;-) Here's my rewrite (note the changed order which makes more sense):

KDE is a Open Source graphical desktop environment for Unix workstations. It combines ease of use and contemporary graphical design with the stability of the Unix operating system.

KDE provides a solid foundation for a growing number of applications. KDE includes a high quality development framework for Unix that makes developing software easier and faster, from simple applications to complex office suites and word processors.

KDE is an Internet project and is truly open in every sense. Development takes place on the Internet and is discussed on our mailing lists, USENET news groups, and IRC channels to which we invite and welcome everyone.

,p>There might be mistakes here too, but anything is an improvement over the current poorly worded version.

I like it, with one minor exception. The links at the top of the page are hard to read once you've already visited them (well, in IE anyways). Click on the FAQ, then go back to kde.org and look at the link.

I regularly check the KDE page to read the news. At first I was delighted to see that the news section is now in view with a "normal" browser window - no more scrolling to get to the point!

But - in the old version I could click into the news list from then first page and then read ALL the news with just the help of the scrollbar. Now I have to go forth and back between news-view and first page. And if there are more than five new items I also have to press "more" and get yet another view of the news, this time listing something like the first paragraph of the latest news (?).

I would really like a system that works like the old one - click in first page news list sends me to the right anchor in an all-news-full-text page (or all-news-since-30-days). If I want to comment something I won't bother having to click twice, but when I simply want to read the news it's too much work as it is now!

Well, we could add anchor hooks to the dot.kde.org frontpage and tweak rdfplus so that the KDE site points to anchors on the frontpage, but I'm not sure it's necessary or if we should even do that. I think you'll get used to the new system soon enough.

Or else we could have an enhanced version of http://dot.kde.org/articles that would also display the article text. 30 days is quite a lot though.