Zendesk treats unsupported HTML elements as unknown and handles them differently based on the context.
For help center articles, unknown HTML tags are removed, and their content is placed within a paragraph element. For content blocks, unsupported content is wrapped in an HTML block, allowing you to edit it separately. This ensures that unsupported elements do not disrupt the rendering of your articles. For example, an unknown tag like<mytag>Hello world!</mytag>
would be rendered as<p>Hello world!</p>
in the help center.
To edit the source code of your Zendesk help center articles, you can use the source code editor. This tool allows you to customize and style your articles beyond the capabilities of the standard WYSIWYG editor. To get started, navigate to the help…
The 'Clean up styles' feature in Zendesk's source code editor helps you remove unwanted inline styles from your article's HTML. When you copy and paste content from an HTML page, it might bring along unnecessary styles that clutter your article. By…
In Zendesk help center articles, certain HTML elements are considered unsafe and are excluded from rendering. Unsafe elements include applet, button, embed, form, input, object, script, textarea, and style. These elements are not removed from the…
Styling HTML in Zendesk help center articles is best done using CSS classes defined in your help center theme. Zendesk recommends using the class attribute for styling, as it is more maintainable than inline styles. Avoid using nested selectors and…
When editing source code in Zendesk, there are several important considerations to keep in mind. Firstly, Zendesk automatically removes most empty container elements, like<i>
or<span>
, unless they contain content. However, empty<p>
tags…