Imported From: http://groups.google.com/group/in-portal-dev/browse_thread/thread/06c2c8594b29c6ca#
On the one hand, it is convenient when the HTML-code, is included in
...
the Content Block as simple as possible (do not have a lot of styles,
...
formatting) - then the user is easier to avoid mistakes in the
...
elements styling. On the other hand, it is desirable that when editing
...
a Content Block looks like on the page, that is, that its elements
...
have the same style as on the page.
In order to satisfy both above requirements, I suggest add to
ContentBlock tag optional "class" parameter. If this option is
specified, then in the CMS-editor window, the value of this parameter
is added to the "class" attribute of <body> tag. For example, if class
is not specified, <body> tag is the way it is now - <body contenteditable="true" spellcheck="false" class="cke_show_borders">.
If in the template is written <inp2:st_ContentBlock num="1" class="big-font"/>, then the "body"-tag will be the - <body contenteditable = "true" spellcheck = "false" class = "cke_show_borders big-font">
That is, we should not include in the CMS-content unit covering
element to apply all related styles in the CMS editor window. And the
content of CMS block may contain no "class" attributes, but have
adequate and powerful styling applied.
Related Tasks
| Jira Legacy | ||||
|---|---|---|---|---|
|