[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [libreoffice-website] CMS requirements / suitability testing
- Subject: Re: [libreoffice-website] CMS requirements / suitability testing
- From: "jzacsh" <firstname.lastname@example.org>
- Date: Thu, 7 Oct 2010 11:17:45 +0000
- To: email@example.com
Do you really want "static" html files? Or do you mean caching? I think serving static content out of memory is _really_ the fastest way, none the less.
Drupal is known for being scaled to acommodate a lot of traffic (you can google about that yourself). Drupal has awesome friendly URL features, out-of-the-box caching, and every other feature you've mentioned.
I'm not sure why you want to see a demo installation of any one CMS, (just to poke around the interfaces?) - you need to know a CMS in order to know what you're looking at, otherwise you're left to simply be impressed with nice themes (which, I'm sure is not how you want to decide).
I've asked one of the more involved Drupal developers to come pitch in here :)
From: Christian Lohmaier <firstname.lastname@example.org>
Date: Thu, 7 Oct 2010 08:38:56
Subject: [libreoffice-website] CMS requirements / suitability testing
as the question "what cms to choose" now comes up more often, I think
it's best to just setup some demo-sites to compare them.
I'm currently evaluating silverstripe, and so far it seems to be good enogh:
Major points any CMS must fulfill:
* Create static pages
In the past, on the OpenOffice.org website with SourceCast (now named
CEE) we often had the problem of the site going down because of the
amount of requests. A pure php driven site, even with php-accelerators
very likely will put too much load on the server.
* User-Firendly URLs
People want to be able to guess what a link is about. Pointing someone
to http:://example.com/<randomnumber> is bad, better point to
Also important for search-engines and the like
* Support for Translations
Key pages should be available in multiple languages, the CMS should
support managing those (without having the editor keep the list of
translations in sync, wihout the editor needing to update all
translations with a new link)
* Support for subsites
As LO is a huge project, with lots of different areas where work is
being done, the CMS should support multiple subsites. (like for
example on OOo the various native-lang projects, the marketing,
distribution, etc. projects, that have different focus and needs)
* sufficiently sophisticated user-rights system
Not every user should have the possibility to change every aspect on the site.
Some parts are reserved to be edited by admins, some areas are free to
be messed-around by community members.
Specifically, it should support a review/approval workflow.
* user friendly editor
Probably not so much of a concern, as many will use the same tinyMCE,
but nevertheless an important topic
Those are the basic requirements that come to my mind, now to stuff it
doesn't need to provide:
* an own wiki
Specialized wiki-software is always superior
* own Forum
* random other addition (blog, whatever)
see wiki / we have dedicated planet
The only drawback of silverstripe I found sofar is user account
By default the email is not verified by sending a probe, thus a user
can create an account with an email-address that he/she doesn't own.
Only burden is a captcha. This puts a little burden on the
administrators to double check
I can provide access to a staging installation soon, to check things out.
I'd be happy if someone else could do this for drupal or whatever
other CMS you think should be in the closer choice.
The static sites requirements is considered a hard requirement, no
"but it is fast without" arguments please. To quickly get an idea how
your site performs, use the apache benchmark utility, request a site
1000 times with concurrency of 5. That can be used as a measure to
compare cached/static vs dynamic performance.
To unsubscribe, send an empty e-mail to email@example.com
List archives are available at http://www.libreoffice.org/lists/website/
All messages you send to this list will be publicly archived and cannot be deleted.
|Re: [libreoffice-website] CMS requirements / suitability testing||Christian Lohmaier <firstname.lastname@example.org>|
|Re: [libreoffice-website] CMS requirements / suitability testing||Benjamin Horst <email@example.com>|
|[libreoffice-website] CMS requirements / suitability testing||Christian Lohmaier <firstname.lastname@example.org>|
- Prev by Date: Re: [libreoffice-website] CMS requirements / suitability testing
- Next by Date: Re: [libreoffice-website] CMS requirements / suitability testing
- Previous by thread: Re: [libreoffice-website] CMS requirements / suitability testing
- Next by thread: Re: [libreoffice-website] CMS requirements / suitability testing