50

Frankly, the problems on userbase come down to the fact that we have no sysadmins available to make deep-rooted changes - and the general kde sysadmins have enough work without taking this on. I've been fighting this problem since we started userbase, and unless we solve it there simply is no way we can make any changes that might be required by this initiative. We have had volunteers to give some time to specific projects, but it needs a sysadmin to oversee them.

I do think it's important - but practicably, I don't see what we can do to improve matters as things stand.

I would like to see, as a first step, a meeting of all concerned, purely to make each other aware of all the issues that concern us. We can then sort out where there are overlaps, and where the needs are totally separate, hopefully leading to an action plan that we all can follow as best we can.

annew, you have my vote

neverendingo wrote:
Well, it is not THAT easy... just think of different needs of every website. A forum needs different buttons than e.g. news.kde.org (think of the date buttons).
But mostly i agree.

Yep, its not that easy, but mostly style is represented by a header. Headers on the server is usually kept in something like header.tpl, so it is possible to change only header.cp content with something +- default (with some changes, like title etc)

neverendingo wrote:
That raises another problem. I can't speak for mediawiki, but the forum software is not able to load templates from a different server. Not all kde sites are hosted on the same server. There are several kde servers.
Of course, hosting it on svn and putting a cron job up could solve this.

You didn't got the point. In short, templates are files, used by *server*, to generate html, css,js,png,etc are files, user by the *client*. *Any* templateing system/engine can use files from another server. What you need it to put full path (with domain) in header template. like ="/files/styles/style.css" becomes ="http://static.kde.or/global/styles/style.css"

Neverendingo was talking about the actual *.html template files, which phpBB parses to output the HTML you see everywhere here. These files must be accessible by phpBB directly on the filesystem.

CSS is of course externally loadable.

That is one thing that always bothered me about KDE Web sites, the fact that so few of them are anything like each other! It really makes the whole project seem hodge-podge.

And then there are stand-alone sites like the developers of Digikam and K3B.

If there's a need for a wiki, then the whole team should try to agree on wiki software and a style, same thing for blogs, etc. Not easy of course.