This overview gives my XStandard module a very unfavourable review, but it seems the author hasn't understood any of the merits (or indeed even some of the main shortcomings) of the XStandard editor.
The main bullet points should've been:

Good: It's the only WYSIWYG available to Drupal that meets certain accessibility requirements. It enforces semantic XHTML.
Bad: It requires a browser plugin and there is no Linux support. It's not open source and the pro version isn't free.

I realise that XStandard might not be everyone's cup of tea, but I think it's unfair to have my module so harshly dismissed in the official documentation by someone who clearly hasn't bothered to do his homework.

I also think the article reads more like a sloppy blog post than official documentation and it seems to be in the wrong section since it has nothing to do with troubleshooting.

Here's the link: http://drupal.org/node/208456

Comments

dvessel’s picture

I would pull that page just for the writing style. Definitely reads like a blog. Goes against the guidelines on writing for the handbooks.

keith.smith’s picture

Just for more information (and without expressing an opinion on this book page because I haven't read it in some time), this was created as part of this GHOP task: http://drupal.org/node/200332.

henrrrik’s picture

I can't understand how it got approved as documentation. I mean, my personal beef aside, it it's basically a table of Coder module results followed by an opinion piece. How is it even supposed to be maintained, is someone else going to update the author's opinions?

webchick’s picture

Feel free to make suggestions to the text. The comparison table is a starting point, and could be expanded to include other features such as image support, etc.

henrrrik’s picture

I would scrap the text entirely and replace it with a feature comparison table. Standards Schmandards has a good (albeit accessibility focused) example here: http://www.standards-schmandards.com/exhibits/wysiwyg/2007/wysiwyg.htm

A comparison table would be maintainable, objective and give a much better overview. Perhaps a DROP task could serve as the foundation?

webchick’s picture

Sure. Feel free to create one and offer to mentor it. http://drop.cwgordon.com/node/add/task

henrrrik’s picture

sepeck’s picture

@3 - for clarification purposes, anyone can contribute pages to the handbook. There is not a central committee reviewing these pages before publication.

Barry Madore’s picture

Component: Admin Guide » Correction/Clarification

changing component

heather’s picture

Status: Active » Closed (duplicate)

Since henrrick created a new topic for this, http://drupal.org/node/224143
- this thread is essentially a duplicate.