I've used all the CMS/Bloggers mentioned above and Drupal would be my
pick for CMS, TextPattern for a blog.  IMHO Textpattern isn't as much of
a CMS as products like Drupal or *shudder* php-nuke as it doesn't offer
modules such as Forums, CRM, Event Calendars etc. that are needed to
create a true community site.  Also the Textpattern interface is geared
towards Web Developers who know a little bit about what they're doing.
Also it helps to be comfortable hacking the code a bit if you want to
extend it and get full use of the available extensions ppl make.  The
wiki-like Textile code used for formatting content can be a bit of a
hurdle for clients as well, in my experience they much prefer the idea
of a MS Word-like inline WYSIWYG editor.  That said, Textpattern rocks
for blogging, I use it myself ;)

Drupal on the other hand is fully compliant, a cinch to install and
configure, has a large and active developer community and countless
modules available for download.  Content administration is a breeze and
requires little knowledge of web design.  Creating themes is based on
the PHPTemplate standard which gives the designer full control over the
output.  I would choose it over any of the other products mentioned.

Mambo is a great CMS but still falling behind with *TML compliance.

I use Jahia CMS a lot in my day job.  It also gives full control over
output via its API and robust templating engine, but the admin interface
is far from standards-compliant.  Price can be high depending on
licensing requirements, but if scalability is a priority I highly
recommend it.

I don't know of any other Commercial standards-compliant CMS's but you'd
think there'd have to be a few out there?

That's my $0.02 worth...

Regards,

Miles.
 

> -----Original Message-----
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Andreas 
> Boehmer [Addictive Media]
> Sent: Tuesday, 17 May 2005 1:57 PM
> To: [email protected]
> Subject: [WSG CMS] Open source, accessible CMS?
> 
> Hi guys,
> 
> I am new to this newsgroup - have been around the WSG one so 
> far. I'm interested to see what's going on in this one...
> 
> What I am looking for is an open-source CMS that allows me to 
> create accessible websites. Is there something like that out there? 
> 
> A product I have used so far is called CM3 by Melbourne 
> company DDSN. Quite a nice product: it gives the developer 
> pretty much full control over the frontend - all I do is 
> insert a little placeholder function into my pages where I 
> want the dynamic content to appear. But the program also has 
> a range of bugs that I have been fighting with over the last months. 
> 
> So now I am searching for something new: PHP driven, if 
> possible. All our websites fulfil W3C AA or AAA, so I would 
> like to continue that with this CMS. Of course the best would 
> be if the admin could be accessible as well! 
> 
> Any recommendations?
> 
> Cheers,
> 
> Andreas.
> 
> 
> *********************************************************
> The CMS discussion list for http://webstandardsgroup.org/
> *********************************************************
> 
> 


IMPORTANT: This e-mail, including any attachments, may contain private or 
confidential information. If you think you may not be the intended recipient, 
or if you have received this e-mail in error, please contact the sender 
immediately and delete all copies of this e-mail. If you are not the intended 
recipient, you must not reproduce any part of this e-mail or disclose its 
contents to any other party.
This email represents the views of the individual sender, which do not 
necessarily reflect those of education.au limited except where the sender 
expressly states otherwise.
It is your responsibility to scan this email and any files transmitted with it 
for viruses or any other defects.
education.au limited will not be liable for any loss, damage or consequence 
caused directly or indirectly by this email. 
*********************************************************
The CMS discussion list for http://webstandardsgroup.org/
*********************************************************

Reply via email to