I actually went a step further there. I didn't find a browser based
wysiwyg editor that performed satisfactorily across platforms and
browsers so I decided to get the clients to save Word to (filtered)
html and then clean that up server side. That way they did not have to
get the hang of anything new except the workflow.
However, there were instances where Word would fail to translate, eg a
list to an html ordered list, so while dabbling I had one client use
Markdown dingus ( http://daringfireball.net/projects/markdown/dingus )
to quickly do bits and pieces. That was successful enough that as
mentioned in another post I integrated it into my cms and it is even
used where users are unaware of it's presence.
Ultimately there is no one solution since clients and circumstances
differ and I'm often surprised when I read so much certainty about what
clients want. Personally I'm often surprised by just how much clients
are willing to learn if it means they end up with a more appropriate
solution to their needs.
Nick
If you give your client a cheat sheet and some examples, are you
really
telling me this is harder to learn then using a WYSIWYG editor?
Yes, definitely. All our clients know how to use MS Word, our WYSIWYG
editor looks like MS Word, hence, there's virtually no learning curve
on
the WYSIWYG editor and this way, they feel comfortable with the
application right from the start - it's got nothing new to them.
Maybe your customers aren't familiar with MS Word or something, but
ours
are, and ours wouldn't care much for a cheat sheet when they can get an
interface they already know and like. :)
*********************************************************
The CMS discussion list for http://webstandardsgroup.org/
*********************************************************
