A couple things, mostly random thoughts: On Wed, Dec 17, 2008 at 7:13 PM, Paul Scott-Wilson <[email protected]> wrote: > 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. >
This is *huge*. It seems the blocker we always have when we get close is localization. > 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 will start a high level scoping document this weekend, including a sitemap. I don't think it will be much different than what we have now, with the exception of of fleshing out our other flavors pages (XFCE, KDE, etc) > 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". > Drupal can handle blogging right within it. When I was managing a a Drupal site with about 100 users, a good percentage of them used Drupal's blogging engine. One thing I liked about it, is that if we had some kind of community news page, it is very simple to promote a blog post to that page as news, similar to how Slashdot promotes stories to their main page or DailyKos does. I'd also like to second something pscott said in a later email, regarding news. Content needs to be added and refreshed to keep people coming back. Some kind of news or community news page - whether it's links to recent articles about us, an "official" blog with what is going on in Foresight, a newsletter, etc. I had started a Wordpress appliance a few months back, but Lance and I got hung up trying to build it with a specific error we were never able to overcome. I have a lot of passion in making sure we have timely news from the developer community to our users with first looks at what's coming, etc. Paul --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Foresight Linux Marketing" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/foresight-mktg?hl=en -~----------~----~----~----~------~----~------~--~---
