Hello Everybody,
I am not really sure where to put this question, but I guess post install is the place. (Actually where does one discuss best practices about implementing Drupal?)
I have been using Drupal for more than 2 years now and implemented it more that a dozen websites, each time I promise clients easy to update website (It’s just like Word is what my marketing person says, don’t we all say that?), but anybody who has tried creating complex “beautiful” pages with Drupal knows that it’s not really “that” easy.
“WYSIWYG” solutions (I have used TinyMCE and FCKEditor) work best for simpler data formats like blogs (Some paragraphs of text, 2-3 images), but when we try to create complex pages “WYSIWYG” doesn’t seem to adequate. So my page designers end up disabling “WYSIWYG” solutions while they are creating pages for the client as they place lots of inline CSS. But then client can’t really edit them after words with the Editor UI because they can’t simply match CSS skills of a professional coder.
Also Tables is one thorny issue. Since most of the time base themes (I tend to use Garland, I know I should be using something like Zen, but I know Garland so well now that just putting an effort to learn Zen seems lot of work. Is it really worth it?) put some styles on default table elements so if the client inserts a table using “WYSIWYG” editor naturally it will inherit the themes CSS which overrides what client it trying to do with the “WYSIWYG” HTML editor. In this case I generally end up restyling all basic table elements to give then basic grid look and by using template.php I use separate CSS class for admin pages and non-admin pages and style tables differently for each of them.
Also inline CSS was another thing I wanted to discuss, as it makes cod messy. Generally the static websites my team creates are “really clean” (we put it all in external style sheets) when it comes to Drupal inline CSS seems to unavoidable.
How do you tackle these issues? I think properly training the client about how to use the “WYSIWYG” optimally is really important. How much time and effort do you put in training the client to use his/her Drupal system?
I request experienced Drupalers to please share their experience regarding these issues.
Thanks in advance.
Pritam.
Comments
Inline CSS should not be needed.
Inline CSS for the most part should not be needed. Drupal assigns so many useful classes, I can't even begin to imagine why you would ever need (or want) inline css unless it's a special case like a JQuery slider that shows / hides various items in a view for example but that would be done outside of the WYSIWYG editor anyway.
I am using the new CKeditor for my client and so far its great. You haven't provided an actual example of why you need inline CSS either. Also if you have a custom theme, are you taking full advantage of classes / ids? I create custom sub themes based on zen and that provides the perfect array of custom body classes that are extremely granular and specific.
And note -- if you are relying on your clients to use custom inline CSS in the WYSIWYG editor (which in the long run won't work as you have realized) something is not right with the way your theme is coded. The WYSIWYG editor is really meant for an editor / author to put in content, images, video etc.. but it should not be up to them to style the way the website looks. Just my 2 cents.
Danny Englander | Twitter | Instagram
I agree with you totally. For
I agree with you totally. For creating complex layout content body, WYSIWYG editor is mess. Users cannot creating content like experience in desktop word processor like ms word, open office.