Skip to main content
replaced http://stackoverflow.com/ with https://stackoverflow.com/
Source Link

I'd argue the best place for referencing a style sheet is at the page level (or its template), regardless of CMS approach. Consider approaching the "embed an internal style sheet" requirement with page metadata or as an external link for components. I describe other RTF approaches in this post.

If the HTML is maintained elsewhere and is simply copy/pasted into components, consider a text box instead of RTF. I wouldn't say it's ideal, but it'll save headaches as you work through three or four layers when forcing RTF to act like HTML:

  1. Allowed nodes
  2. Per-field XSLT filter
  3. Stored XML and any differences in APIs accessing it
  4. Template logic

This being said, if this really needs to be in the RTF, look at TcmXhtml.ConfigTcmXhtml.Config for adjusting the allowed nodes as well as the RTF's XSLT filter.

The rich text format area is not an HTML editor, there will be pain when forcing it to act like one and again when changing styles, system, and/or approach. :-)

I'd argue the best place for referencing a style sheet is at the page level (or its template), regardless of CMS approach. Consider approaching the "embed an internal style sheet" requirement with page metadata or as an external link for components. I describe other RTF approaches in this post.

If the HTML is maintained elsewhere and is simply copy/pasted into components, consider a text box instead of RTF. I wouldn't say it's ideal, but it'll save headaches as you work through three or four layers when forcing RTF to act like HTML:

  1. Allowed nodes
  2. Per-field XSLT filter
  3. Stored XML and any differences in APIs accessing it
  4. Template logic

This being said, if this really needs to be in the RTF, look at TcmXhtml.Config for adjusting the allowed nodes as well as the RTF's XSLT filter.

The rich text format area is not an HTML editor, there will be pain when forcing it to act like one and again when changing styles, system, and/or approach. :-)

I'd argue the best place for referencing a style sheet is at the page level (or its template), regardless of CMS approach. Consider approaching the "embed an internal style sheet" requirement with page metadata or as an external link for components. I describe other RTF approaches in this post.

If the HTML is maintained elsewhere and is simply copy/pasted into components, consider a text box instead of RTF. I wouldn't say it's ideal, but it'll save headaches as you work through three or four layers when forcing RTF to act like HTML:

  1. Allowed nodes
  2. Per-field XSLT filter
  3. Stored XML and any differences in APIs accessing it
  4. Template logic

This being said, if this really needs to be in the RTF, look at TcmXhtml.Config for adjusting the allowed nodes as well as the RTF's XSLT filter.

The rich text format area is not an HTML editor, there will be pain when forcing it to act like one and again when changing styles, system, and/or approach. :-)

Source Link
Alvin Reyes
  • 12.8k
  • 4
  • 23
  • 62

I'd argue the best place for referencing a style sheet is at the page level (or its template), regardless of CMS approach. Consider approaching the "embed an internal style sheet" requirement with page metadata or as an external link for components. I describe other RTF approaches in this post.

If the HTML is maintained elsewhere and is simply copy/pasted into components, consider a text box instead of RTF. I wouldn't say it's ideal, but it'll save headaches as you work through three or four layers when forcing RTF to act like HTML:

  1. Allowed nodes
  2. Per-field XSLT filter
  3. Stored XML and any differences in APIs accessing it
  4. Template logic

This being said, if this really needs to be in the RTF, look at TcmXhtml.Config for adjusting the allowed nodes as well as the RTF's XSLT filter.

The rich text format area is not an HTML editor, there will be pain when forcing it to act like one and again when changing styles, system, and/or approach. :-)