RE: [WSG] Accessible Open Source CMS

2007-09-13 Thread John Horner
Oh I see, I hadn't considered that the back end was being evaluated as
well as the output. My mistake. 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Marghanita da Cruz
Sent: Thursday, 13 September 2007 3:04 PM
To: wsg@webstandardsgroup.org
Subject: Re: [WSG] Accessible Open Source CMS

John Horner wrote:
 I don't mean to be difficult, but I'm always baffled by this question.
 
 A CMS, presumably, outputs the code you tell it to output. Whether it
 serves up accessible/valid is completely up to you.
 
 To put it another way, a CMS which won't allow you to output
 standards-based code is by definition not a CMS although of course we
 might really be asking about degrees of difficulty. 

 From another perspective, could someone relying on assistive technology

contribute webpages?

 
 -Original Message-
 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
 On Behalf Of Web Dandy Design
 Sent: Wednesday, 12 September 2007 7:14 PM
 To: wsg@webstandardsgroup.org
 Subject: [WSG] Accessible Open Source CMS
 
 Hi,
 
 Can anyone advise on the most accessible, open-source CMS between
 Joomla,
 Drupal or Plone?
 
 Thanks,
 
 Elaine
 Web Designer
 http://www.webdandy.co.uk
 
 
 
 
 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: [EMAIL PROTECTED]
 ***
 
 
 
 


==
 The information contained in this email and any attachment is
confidential and
 may contain legally privileged or copyright material.   It is intended
only for
 the use of the addressee(s).  If you are not the intended recipient of
this
 email, you are not permitted to disseminate, distribute or copy this
email or
 any attachments.  If you have received this message in error, please
notify the
 sender immediately and delete this email from your system.  The ABC
does not
 represent or warrant that this transmission is secure or virus free.
Before
 opening any attachment you should check for viruses.  The ABC's
liability is
 limited to resupplying any email and attachments


==
 
 
 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: [EMAIL PROTECTED]
 ***
 
 


-- 
Marghanita da Cruz
http://www.ramin.com.au
Phone: (+61)0414 869202


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***




==
The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments
==


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-13 Thread XStandard
Tee wrote:
 [XStandard] Mac version finally came out - a very long wait,
 must be at least 2 year
It wasn't a straight port - we were pioneering new accessible UI and few 
features such as authoring definition lists at the same time as we were writing 
the OS X code. Whenever you're first to do something, it's always going to take 
longer. For example, it took us 2 months to build support for authoring 
definition lists (dl). Initially we thought dl should be authored in a similar 
way to ol/ul so we spent a month building the authoring interface that way. 
Then we realized that the user will have a much better experience if dl was 
treated more like tables from an authoring perspective, so we spent a month 
re-writing authoring interface. And that's how 2 years go by.

Here is more info:
http://www.accessifyforum.com/viewtopic.php?t=4931
http://www.accessifyforum.com/viewtopic.php?t=7607

Tee wrote:
 thread regarding XStandard porting to Modx and you and the
 developers were going to see if possible. That seems went dead?
We make a special version of XStandard with most of the Pro features available 
to open source CMS vendors free of charge. Here are the details:
http://xstandard.com/en/programs/xstandard-lite-for-partner-cms/
MODx developers started to integrate XStandard into their CMS but we don't know 
what the current status of that project is.

Regards,
-Vlad
http://xstandard.com
XStandard XHTML WYSIWYG Editor



 Original Message 
From: Tee G. Peng
Date: 2007-09-12 11:02 PM
 
 On Sep 12, 2007, at 5:43 PM, Vlad Alexander (XStandard) wrote:
 
 Tee wrote:
 Personally I don't think there is a fully accessible
 WYSIWYG Editor existed that delivers pure clean code.
 It all depends on how you define fully. XStandard has a keyboard 
 accessible interface and most definitely delivers clean, accessible 
 markup.

 
 
 Well, yesterday I finally learned that the Mac version finally came out 
 - a very long wait, must be at least 2 year; after 6 months of waiting, 
 I gave up and completely forgotten as if it never existed. Haven't try 
 the lite version so I will take your word and give a benefit of doubt, 
 but until then I will reserve my insignificant 2 cents :)
 
 I remember there was a thread regarding XStandard porting to Modx and 
 you and the developers were going to see if possible. That seems went dead?
 
 
 tee
 
 
 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: [EMAIL PROTECTED]
 ***
 
 




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-13 Thread JonMarc Wright
Anyone here try out exponent cms?
I've found it extremely to use, and administer, very simple to convert
designs as well.  It uses smarty for the view output, and pretty much only
uses code in the actually files that control the design and layout for data
pulling from the database, not for the actual design/style/layout bits.
VERY easy to customize, etc.

I am not a CMS expert, but I've played around with quite a few and played
around with theming/styling templates, validating pages, etc. and *emphasis
on the words --* SO FAR it is my favorite.  I LOVE the fact that it doesn't
have what is essentially a separate site where you handle all of the
administration, most of it is done right on the pages you want to modify.

So I would recommend that... exponentcms.org

But I'm always on the lookout for a good CMS so I'll take a look at some of
the other ones mentioned in these e-mails.


On 9/13/07, XStandard Vlad Alexander [EMAIL PROTECTED] wrote:

 Tee wrote:
  [XStandard] Mac version finally came out - a very long wait,
  must be at least 2 year
 It wasn't a straight port - we were pioneering new accessible UI and few
 features such as authoring definition lists at the same time as we were
 writing the OS X code. Whenever you're first to do something, it's always
 going to take longer. For example, it took us 2 months to build support for
 authoring definition lists (dl). Initially we thought dl should be authored
 in a similar way to ol/ul so we spent a month building the authoring
 interface that way. Then we realized that the user will have a much better
 experience if dl was treated more like tables from an authoring perspective,
 so we spent a month re-writing authoring interface. And that's how 2 years
 go by.

 Here is more info:
 http://www.accessifyforum.com/viewtopic.php?t=4931
 http://www.accessifyforum.com/viewtopic.php?t=7607

 Tee wrote:
  thread regarding XStandard porting to Modx and you and the
  developers were going to see if possible. That seems went dead?
 We make a special version of XStandard with most of the Pro features
 available to open source CMS vendors free of charge. Here are the details:
 http://xstandard.com/en/programs/xstandard-lite-for-partner-cms/
 MODx developers started to integrate XStandard into their CMS but we don't
 know what the current status of that project is.

 Regards,
 -Vlad
 http://xstandard.com
 XStandard XHTML WYSIWYG Editor



  Original Message 
 From: Tee G. Peng
 Date: 2007-09-12 11:02 PM
 
  On Sep 12, 2007, at 5:43 PM, Vlad Alexander (XStandard) wrote:
 
  Tee wrote:
  Personally I don't think there is a fully accessible
  WYSIWYG Editor existed that delivers pure clean code.
  It all depends on how you define fully. XStandard has a keyboard
  accessible interface and most definitely delivers clean, accessible
  markup.
 
 
 
  Well, yesterday I finally learned that the Mac version finally came out
  - a very long wait, must be at least 2 year; after 6 months of waiting,
  I gave up and completely forgotten as if it never existed. Haven't try
  the lite version so I will take your word and give a benefit of doubt,
  but until then I will reserve my insignificant 2 cents :)
 
  I remember there was a thread regarding XStandard porting to Modx and
  you and the developers were going to see if possible. That seems went
 dead?
 
 
  tee
 
 
  ***
  List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
  Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
  Help: [EMAIL PROTECTED]
  ***
 
 




 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: [EMAIL PROTECTED]
 ***




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***

Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread Tee G. Peng


On Sep 12, 2007, at 2:13 AM, Web Dandy Design wrote:


Hi,

Can anyone advise on the most accessible, open-source CMS between  
Joomla,

Drupal or Plone?


Modx cms

tee


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread Marghanita da Cruz

Tee G. Peng wrote:


On Sep 12, 2007, at 2:13 AM, Web Dandy Design wrote:


Hi,

Can anyone advise on the most accessible, open-source CMS between Joomla,
Drupal or Plone?


Modx cms


snip
Does anyone have any thoughts on Text Pattern?
http://www.textpattern.com/

Marghanita
--
Marghanita da Cruz
http://www.ramin.com.au
Phone: (+61)0414 869202


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread Barney Carroll

Web Dandy Design wrote:

Hi,

Can anyone advise on the most accessible, open-source CMS between Joomla,
Drupal or Plone?


No takers? I'll answer the question: Plone.

You'll need Python (pretty rare on servers as a whole) as opposed to the 
far more widespread PHP to run the shebang, but I find it to be far more 
customisable with far more power. Plus, Python Tal and Metal are 
extremely easy to understand and manipulate in the templates (should you 
ever need to).


Drupal and Joomla seem to be far easier to install and get running, but 
after that you're stuck in absolute hell if you want anything other than 
an elaborate blog (granted, that is all people seem to want these days): 
Crucially, there are no link libraries.


Plone (indeed, the Zope beneath it) simulates folders perfectly so you 
basically have a file system logic – and keeps a catalogue of all files, 
pages and sub-elements that can easily be mashed, concatenated or 
referenced from anywhere else.


Plus the number of incredibly advanced products (including such 
wonderful things as TextIndexNG, which can index MS office files and 
make them searchable)... It's hands down to me.


I'd recommend setting up a virginal Plone and installing the 
DIYPloneStyle product to get on your way.



Regards,
Barney


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread David Little
Hi,

 No takers? I'll answer the question: Plone.

I'll second that. We've been using Zope for some time in my current
workplace and are now moving to Plone.

Plone comes out of the box with good standards support, although you'll
naturally want to customise the look and feel -- you can give a site its own
skin without too much trouble. Plone's templating language uses custom
name-spaced attributes (tal: and metal:) embedded within html tags. Python
is very powerful, and due to its syntax can be relatively easy to pick up.

Plone's very extensible -- you can either write your own add-ons
(Products) or install any of the freely available ones from the
plone.orgwebsite. There's a very active community behind Plone, so
there are always
new products being released.

However, I would stress that there is a steep learning curve with Plone when
you first come to it, especially if you've been used to using PHP/MySQL etc.
solutions but it's worth sticking with. The plone.org site has got a lot of
useful tutorials, so you should check that out.

From an end user's point of view, Plone is very easy to use. The inbuilt
text editor (Kupu) is also XHTML compliant, so your users are going to be
creating good, clean, standards-compliant code.

So, I'd definitely recommend Plone, but would stress you do need to spend
some time getting up to speed with it.

Thanks,
David

On 12/09/2007, Barney Carroll [EMAIL PROTECTED] wrote:

 Web Dandy Design wrote:
  Hi,
 
  Can anyone advise on the most accessible, open-source CMS between
 Joomla,
  Drupal or Plone?

 No takers? I'll answer the question: Plone.

 You'll need Python (pretty rare on servers as a whole) as opposed to the
 far more widespread PHP to run the shebang, but I find it to be far more
 customisable with far more power. Plus, Python Tal and Metal are
 extremely easy to understand and manipulate in the templates (should you
 ever need to).

 Drupal and Joomla seem to be far easier to install and get running, but
 after that you're stuck in absolute hell if you want anything other than
 an elaborate blog (granted, that is all people seem to want these days):
 Crucially, there are no link libraries.

 Plone (indeed, the Zope beneath it) simulates folders perfectly so you
 basically have a file system logic – and keeps a catalogue of all files,
 pages and sub-elements that can easily be mashed, concatenated or
 referenced from anywhere else.

 Plus the number of incredibly advanced products (including such
 wonderful things as TextIndexNG, which can index MS office files and
 make them searchable)... It's hands down to me.

 I'd recommend setting up a virginal Plone and installing the
 DIYPloneStyle product to get on your way.


 Regards,
 Barney


 ***
 List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
 Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
 Help: [EMAIL PROTECTED]
 ***




-- 
David Little

-e: [EMAIL PROTECTED]
-w: www.littled.net


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***


Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread Christian Montoya
On 9/12/07, Marghanita da Cruz [EMAIL PROTECTED] wrote:
 Tee G. Peng wrote:
 
  On Sep 12, 2007, at 2:13 AM, Web Dandy Design wrote:
 
  Hi,
 
  Can anyone advise on the most accessible, open-source CMS between Joomla,
  Drupal or Plone?
 
  Modx cms
 
 snip
 Does anyone have any thoughts on Text Pattern?
 http://www.textpattern.com/

I do: use Wordpress http://www.wordpress.org/


-- 
--
Christian Montoya
christianmontoya.net


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread Bruce
 Can anyone advise on the most accessible, open-source CMS between 
 Joomla,

 Drupal or Plone?


These and related are as accessible as their programmers make them. I find 
them all difficult to configure for the reason that one is limited my 
mambots, modules, plugins, etc which are made to add functions and wysiwyg 
editors. All the code in the templates (if they can be found even) is 
integrated into the core and is difficult at best to edit. I find even 
wordpress editing out code I add to templates and becoming increasingly 
unusable.


Expression Engine on the other hand is as accessible and Standards based as 
YOU make it. The templates are in the open and stand alone in the sense they 
aren't wrapped around the core programming and they will output anything put 
in them. All the xhtml code is right there and not dependent on other core 
programming or functions.


Bruce Prochnau
bkdesign solutions

- Original Message - 
From: Christian Montoya [EMAIL PROTECTED]

To: wsg@webstandardsgroup.org
Sent: Wednesday, September 12, 2007 9:44 AM
Subject: Re: [WSG] Accessible Open Source CMS



On 9/12/07, Marghanita da Cruz [EMAIL PROTECTED] wrote:

Tee G. Peng wrote:

 On Sep 12, 2007, at 2:13 AM, Web Dandy Design wrote:

 Hi,

 Can anyone advise on the most accessible, open-source CMS between 
 Joomla,

 Drupal or Plone?

 Modx cms

snip
Does anyone have any thoughts on Text Pattern?
http://www.textpattern.com/


I do: use Wordpress http://www.wordpress.org/


--
--
Christian Montoya
christianmontoya.net


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***








***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread Rick Lecoat
On 12/9/07 (14:55) Bruce said:

These and related are as accessible as their programmers make them. I find 
them all difficult to configure for the reason that one is limited my 
mambots, modules, plugins, etc which are made to add functions and wysiwyg 
editors. All the code in the templates (if they can be found even) is 
integrated into the core and is difficult at best to edit. I find even 
wordpress editing out code I add to templates and becoming increasingly 
unusable.

Expression Engine on the other hand is as accessible and Standards based as 
YOU make it. The templates are in the open and stand alone in the sense they 
aren't wrapped around the core programming and they will output anything put 
in them. All the xhtml code is right there and not dependent on other core 
programming or functions.

Of course, Expression Engine isn't a freely available Open Source
solution, you need to stump up the readies for it. But I recently did a
bit of reading in order to find a CMS that could handle (initially) a
basic blog and (later) whatever I wanted to throw at it, whilst being
both web standards-friendly and design-malleable, and I also decided to
opt for Expression Engine. I've barely had a chance to scratch the
surface yet (other projects keep getting in the way -- curse those fee-
paying clients!) but so far I've not seen anything that makes me regret
my choice. And there is a free cut-down version available for those
who's budgets are tighter.

-- 
Rick Lecoat



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread XStandard
This article may be useful:

http://juicystudio.com/article/choosing-an-accessible-cms.php

Regards,
-Vlad
http://xstandard.com
XStandard XHTML WYSIWYG Editor for CMS



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread John Faulds
I use both Wordpress and Expression Engine and don't find WP any less  
capable of outputting exactly what you put into it than EE. The only time  
I find you ever have to edit core WP files is if you're using the inbuilt  
sidebar widgets functionality; otherwise it's not an issue.


On Wed, 12 Sep 2007 23:55:34 +1000, Bruce [EMAIL PROTECTED] wrote:

snip


These and related are as accessible as their programmers make them. I  
find them all difficult to configure for the reason that one is limited  
my mambots, modules, plugins, etc which are made to add functions and  
wysiwyg editors. All the code in the templates (if they can be found  
even) is integrated into the core and is difficult at best to edit. I  
find even wordpress editing out code I add to templates and becoming  
increasingly unusable.


Expression Engine on the other hand is as accessible and Standards based  
as YOU make it. The templates are in the open and stand alone in the  
sense they aren't wrapped around the core programming and they will  
output anything put in them. All the xhtml code is right there and not  
dependent on other core programming or functions.


Bruce Prochnau
bkdesign solutions

- Original Message - From: Christian Montoya  
[EMAIL PROTECTED]

To: wsg@webstandardsgroup.org
Sent: Wednesday, September 12, 2007 9:44 AM
Subject: Re: [WSG] Accessible Open Source CMS



On 9/12/07, Marghanita da Cruz [EMAIL PROTECTED] wrote:

snip


I do: use Wordpress http://www.wordpress.org/


-- --
Christian Montoya
christianmontoya.net


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***








***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***





--
Tyssen Design
www.tyssendesign.com.au
Ph: (07) 3300 3303
Mb: 0405 678 590


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread Tee G. Peng


On Sep 12, 2007, at 7:57 AM, Vlad Alexander (XStandard) wrote:


This article may be useful:

http://juicystudio.com/article/choosing-an-accessible-cms.php

Hmm, I wonder why they didn't include Modx. The survey was done in  
May, maybe Modx (v 0.9.5) wasn't quite ready yet! The v.9.6 has  
improved a lot and we are promised something even sweeter in the next  
release.


That said, if you pay attention and practice web standards, it will  
be a fooled to not  pay attention to certain things from certain  
people in the web standards groups. The same goes with Modx CMS, if  
you are looking for a scalable, accessible and web standards  
compliant CMS that offers many flexible and powerful features through  
plugins and snippets, it will be a fool that you don't even spend a  
few minutes to take a look simply because you already have a favorite  
ones.


Dive into Modx and make a template (or convert one of your static CSS/ 
XHTML layout) isn't difficult at all. Modx is very user-friendly for  
web designer however the learning curve is a bit higher (but not more  
than WP, Joomla, Textpattern,  EE, Plone of the sort in my opinion (I  
have tested them all)) if one PHP knowledge's is a bit weak (someone  
like me). Currently Modx lacks a good documentation and the admin  
interface have room to improved (again! we are promised that they  
will be changed in the next release);  Many tips and tutorials are  
hidden in the Forum that need a bit of digging and dedication.


Modx doesn't control/limit what you want as far as code and  
functionality concerned; it gives you what you want to have, the way  
you wanted it.


Personally I don't think there is a fully accessible  WYSIWYG Editor  
existed that delivers pure clean code. TINY MCE is the default plugin  
for Modx which I find difficult to use and a memory eater; I prefer  
something like textile from Textpattern; someone was making Markdown  
integration I think. It has a QuickEdit front-end content editor  
which I like very much.


Ditto, Jot and Reflect snippets make Modx a wonderful Blog CMS (if  
you only want a blog). Ditto aggregates articles (aka documents)  
(this snippet can do a lot more tasks); Jot takes care of comments   
and Reflect handles the archives. There is a plugin called PHx  
(Placeholders Xtended), enable, can add the capability of output  
modifiers using placeholders, template variables (A very powerful  
feature of Modx - you no longer limited to Content area) and settings  
tags. Jot + PHx, you get: moderate, edit, delete comments at front- 
end. As for the ping and trackback features that bloggers concern  
about, there is a Trackback snippet, and a Japanese developer wrote a  
SendPing module :


[quote]:
What does this plugin do?
This plugin is supposed to send pings to various (editable) websites  
using the XML-RCP library and ping protocol. The goal of this is to  
update these services that there has been added new content to your  
website, which will make sure these services crawl your website. This  
feature is mainly interesting for those who use MODx to blog, but the  
usage of pings is growing all the time as it's an comfortable way to  
instantly get updated data for search engines.
In addition to this it'll also notify Google that your site has new  
content and your sitemap.xml should be spidered again (exact filename  
also configurable).
Also, according to ZeRo's email this currently supports multi  
domains, which could be useful for the heavy users.


What doesn't it do?
It wont make you coffee nor breakfast, sadly, in addition to that it  
doesn't automatically notify these services as of now; you'll have to  
run the module manually, ZeRo has planned a plugin to handle this  
with his next version.


Trackback allows blogger to send/receive pings to other blogs whereas  
SendPing will notify blog search engines/social networking sites


[/quote]


Many interesting and powerful snippets/plugins/modules that can  
enhance features, functions and make your live sweeter,  can be found  
in 'forum  In Development'.


Lastly, I almost hate to mention my site as it hasn't completed yet -  
it's powered by Modx using just a few snippets/plugin with a nothing- 
to-show-blog. This is not a good example to demonstrate how flexible  
and scalable and accessible Modx can give you, but I hope it's a good  
example of 'artisan's work' (borrowed Partrick's word) made by Modx.  
In the blog individual article page, I even managed to score WCAG AAA.

http://tinyurl.com/3deh87

tee


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread Tate Johnson

On 12/09/2007, at 7:13 PM, Web Dandy Design wrote:


Hi,

Can anyone advise on the most accessible, open-source CMS between  
Joomla,

Drupal or Plone?

Thanks,



I'd encourage you to take a look at Silverstripe. It's flexible --  
you have *full* control of the markup that it outputs and it's  
surprisingly easy to implement. All the content (including files and  
newsletters) are managed through a WYSIWG administration interface.  
It utilises TinyMCE. It's under active development with the full  
backing of a New Zealand based company. More importantly,  
Silverstripe is open source (BSD licence).


Here's an online demo that you can take a look at:
http://demo.silverstripe.com/

I find Silverstripe a pleasure to work wtih, especially after using  
Drupal.


Cheers,
Tate



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread XStandard
Tee wrote:
 Personally I don't think there is a fully accessible
 WYSIWYG Editor existed that delivers pure clean code.
It all depends on how you define fully. XStandard has a keyboard accessible 
interface and most definitely delivers clean, accessible markup.

Regards,
-Vlad
http://xstandard.com




 Original Message 
From: Tee G. Peng
Date: 2007-09-12 7:46 PM
 
 On Sep 12, 2007, at 7:57 AM, Vlad Alexander (XStandard) wrote:
 
 This article may be useful:

 http://juicystudio.com/article/choosing-an-accessible-cms.php

 Hmm, I wonder why they didn't include Modx. The survey was done in May, 
 maybe Modx (v 0.9.5) wasn't quite ready yet! The v.9.6 has improved a 
 lot and we are promised something even sweeter in the next release.
 
 That said, if you pay attention and practice web standards, it will be a 
 fooled to not  pay attention to certain things from certain people in 
 the web standards groups. The same goes with Modx CMS, if you are 
 looking for a scalable, accessible and web standards compliant CMS that 
 offers many flexible and powerful features through plugins and snippets, 
 it will be a fool that you don't even spend a few minutes to take a look 
 simply because you already have a favorite ones.
 
 Dive into Modx and make a template (or convert one of your static 
 CSS/XHTML layout) isn't difficult at all. Modx is very user-friendly for 
 web designer however the learning curve is a bit higher (but not more 
 than WP, Joomla, Textpattern,  EE, Plone of the sort in my opinion (I 
 have tested them all)) if one PHP knowledge's is a bit weak (someone 
 like me). Currently Modx lacks a good documentation and the admin 
 interface have room to improved (again! we are promised that they will 
 be changed in the next release);  Many tips and tutorials are hidden in 
 the Forum that need a bit of digging and dedication.
 
 Modx doesn't control/limit what you want as far as code and 
 functionality concerned; it gives you what you want to have, the way you 
 wanted it.
 
 Personally I don't think there is a fully accessible  WYSIWYG Editor 
 existed that delivers pure clean code. TINY MCE is the default plugin 
 for Modx which I find difficult to use and a memory eater; I prefer 
 something like textile from Textpattern; someone was making Markdown 
 integration I think. It has a QuickEdit front-end content editor which I 
 like very much.
 
 Ditto, Jot and Reflect snippets make Modx a wonderful Blog CMS (if you 
 only want a blog). Ditto aggregates articles (aka documents) (this 
 snippet can do a lot more tasks); Jot takes care of comments  and 
 Reflect handles the archives. There is a plugin called PHx (Placeholders 
 Xtended), enable, can add the capability of output modifiers using 
 placeholders, template variables (A very powerful feature of Modx - you 
 no longer limited to Content area) and settings tags. Jot + PHx, you 
 get: moderate, edit, delete comments at front-end. As for the ping and 
 trackback features that bloggers concern about, there is a Trackback 
 snippet, and a Japanese developer wrote a SendPing module :
 
 [quote]:
 What does this plugin do?
 This plugin is supposed to send pings to various (editable) websites 
 using the XML-RCP library and ping protocol. The goal of this is to 
 update these services that there has been added new content to your 
 website, which will make sure these services crawl your website. This 
 feature is mainly interesting for those who use MODx to blog, but the 
 usage of pings is growing all the time as it's an comfortable way to 
 instantly get updated data for search engines.
 In addition to this it'll also notify Google that your site has new 
 content and your sitemap.xml should be spidered again (exact filename 
 also configurable).
 Also, according to ZeRo's email this currently supports multi domains, 
 which could be useful for the heavy users.
 
 What doesn't it do?
 It wont make you coffee nor breakfast, sadly, in addition to that it 
 doesn't automatically notify these services as of now; you'll have to 
 run the module manually, ZeRo has planned a plugin to handle this with 
 his next version.
 
 Trackback allows blogger to send/receive pings to other blogs whereas 
 SendPing will notify blog search engines/social networking sites
 
 [/quote]
 
 
 Many interesting and powerful snippets/plugins/modules that can enhance 
 features, functions and make your live sweeter,  can be found in 'forum 
   In Development'.
 
 Lastly, I almost hate to mention my site as it hasn't completed yet - 
 it's powered by Modx using just a few snippets/plugin with a 
 nothing-to-show-blog. This is not a good example to demonstrate how 
 flexible and scalable and accessible Modx can give you, but I hope it's 
 a good example of 'artisan's work' (borrowed Partrick's word) made by 
 Modx. In the blog individual article page, I even managed to score WCAG 
 AAA.
 http://tinyurl.com/3deh87
 
 tee
 
 
 

Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread Tee G. Peng


On Sep 12, 2007, at 5:43 PM, Vlad Alexander (XStandard) wrote:


Tee wrote:

Personally I don't think there is a fully accessible
WYSIWYG Editor existed that delivers pure clean code.
It all depends on how you define fully. XStandard has a keyboard  
accessible interface and most definitely delivers clean, accessible  
markup.





Well, yesterday I finally learned that the Mac version finally came  
out - a very long wait, must be at least 2 year; after 6 months of  
waiting, I gave up and completely forgotten as if it never existed.  
Haven't try the lite version so I will take your word and give a  
benefit of doubt, but until then I will reserve my insignificant 2  
cents :)


I remember there was a thread regarding XStandard porting to Modx and  
you and the developers were going to see if possible. That seems went  
dead?



tee


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



RE: [WSG] Accessible Open Source CMS

2007-09-12 Thread John Horner
I don't mean to be difficult, but I'm always baffled by this question.

A CMS, presumably, outputs the code you tell it to output. Whether it
serves up accessible/valid is completely up to you.

To put it another way, a CMS which won't allow you to output
standards-based code is by definition not a CMS although of course we
might really be asking about degrees of difficulty. 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Web Dandy Design
Sent: Wednesday, 12 September 2007 7:14 PM
To: wsg@webstandardsgroup.org
Subject: [WSG] Accessible Open Source CMS

Hi,

Can anyone advise on the most accessible, open-source CMS between
Joomla,
Drupal or Plone?

Thanks,

Elaine
Web Designer
http://www.webdandy.co.uk




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***




==
The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments
==


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread Marghanita da Cruz

John Horner wrote:

I don't mean to be difficult, but I'm always baffled by this question.

A CMS, presumably, outputs the code you tell it to output. Whether it
serves up accessible/valid is completely up to you.

To put it another way, a CMS which won't allow you to output
standards-based code is by definition not a CMS although of course we
might really be asking about degrees of difficulty. 


From another perspective, could someone relying on assistive technology 
contribute webpages?




-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On Behalf Of Web Dandy Design
Sent: Wednesday, 12 September 2007 7:14 PM
To: wsg@webstandardsgroup.org
Subject: [WSG] Accessible Open Source CMS

Hi,

Can anyone advise on the most accessible, open-source CMS between
Joomla,
Drupal or Plone?

Thanks,

Elaine
Web Designer
http://www.webdandy.co.uk




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***




==
The information contained in this email and any attachment is confidential and
may contain legally privileged or copyright material.   It is intended only for
the use of the addressee(s).  If you are not the intended recipient of this
email, you are not permitted to disseminate, distribute or copy this email or
any attachments.  If you have received this message in error, please notify the
sender immediately and delete this email from your system.  The ABC does not
represent or warrant that this transmission is secure or virus free.   Before
opening any attachment you should check for viruses.  The ABC's liability is
limited to resupplying any email and attachments
==


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***





--
Marghanita da Cruz
http://www.ramin.com.au
Phone: (+61)0414 869202


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***



Re: [WSG] Accessible Open Source CMS

2007-09-12 Thread Raena Jackson Armitage
On 9/13/07, Marghanita da Cruz [EMAIL PROTECTED] wrote:


 From another perspective, could someone relying on assistive technology
 contribute webpages?



This is what i always wonder with these questions, too. I can think of a lot
of examples where the administration/editing interface is hopeless.

Most CMS can be told to spit out valid and accessible code providing you get
off your bum and tell it to, but they're not all accessible to use as an
editor.

-- 
Raena Jackson Armitage
www.raena.net


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: [EMAIL PROTECTED]
***