On Mon, Dec 15, 2008 at 09:31:37PM -0600, Paul Cutler wrote:
Last time we looked, localization remained the biggest issue for all
three, and disqualified Wordpress.

Drupal 6 has support built in. Translations of nodes are linked to a source node; when it is updated the translations are marked out of date.


On Wed, Dec 17, 2008 at 04:11:44PM -0600, Kevin Harriss wrote:
I have a few comments about this discussion.

First is SCOPE, what exactly are we looking for the software to accomplish.

Things I'd like from a CMS we don't currently have:
* Quick and easy updates
* Publishing control
* Better association of content - more than just "It's on the GNOME edition's page so it's about the GNOME edition"
* More content, more often. If nothing changes people will stop checking
* Feeds so people don't have to keep checking manually
* Search so people can find stuff without coming via Google
* A proper gallery with up to date images
* Easy to use navigation
* Lazy translations of content

I am under the impression that we should use the best tool for the task.
This would mean using a CMS/Software for the main site, wiki for the how-to
and wordpress for the blog.

Assuming you mean "developer blogs", I agree. I still wonder how many people who'd want a blog don't have one already though. Project News should absolutely be part of the main site. Maybe even have articles destined for the newsletter appear on the site to show there is more going on than just churning out releases. I'm also thinking that a small FAQ section for questions related to the site would be good rather than sending people to the Wiki for questions like "What do I do with this ISO?", "What is a SHA1 checksum?" or "Why is my browser saying the Certificate for the Wiki is invalid".

Second deals with Editors and Translators.
[...]

This needs more investigation into exactly what is possible. I can say that Drupal 6 will use short codes in the URL, so going to /sv/page would give you the Swedish page if there is one. Getting that to work for the frontpage seems to be a little more involved.

Regarding permissions, there is a separate permission to translate leading me to believe it doesn't imply you can create pages.

A related question is how tightly we restrict registrations (i.e. people able to comment but not create content)? Should it be considered a perk of being a member or is it enough to moderate comments? On the flip side someone contributing translations would be a good step at becoming a member.
--
Paul Scott-Wilson (pscott)

Attachment: pgpNJCySIblRM.pgp
Description: PGP signature

Reply via email to