The new article editor may work in a different way when you paste or edit content from tools such as Google Docs, Notion, or Microsoft Word. You may see unwanted styles or uneditable HTML or code blocks.

This article includes these topics:

  • Why HTML issues happen
  • Paste without unwanted styles
  • Avoid and edit HTML blocks
  • Limitations and best practices

Why HTML issues happen

HTML block issues happen because the old and new article editors use different systems that handle HTML. The new editor creates cleaner, more structured HTML, so it does not always support custom HTML from older articles.

If your article has custom HTML that the new editor cannot support, the editor puts the content in an HTML block. This helps the new editor read and show your code the right way. Without this block, the editor might display your article with layout or format problems.

This image shows what you see when you open an affected article in the new editor. The content stays in an HTML block, but you can still preview and publish the article.

Paste without unwanted styles

To paste content from sources such as Google Docs, Notion, or Microsoft Word without unwanted styles:

  1. Use your browser's Paste as plain text feature:
    • In Microsoft Edge, right-click in the editor and select Paste as plain text
    • In Google Chrome, right-click and select Paste and match style
  2. If you already pasted content with styles, select Source code from the toolbar
  3. Click Actions > Clean up styles to remove inline styles. Note that some basic styles, such as bold, may remain.
  4. Reapply the styles you want. Use the toolbar to apply bold or italic, set a header level, or add bullets as needed.
  5. If you migrate content often, paste it into a plain text app, such as Notepad, before you move it into the new article editor to remove all styles

Avoid and edit HTML blocks

After you migrate or paste, some tables or formatted blocks may be editable only as HTML or code blocks. This can occur when content includes unsupported HTML or deprecated attributes. For example, the height attribute in <td> tags. The new article editor enforces stricter HTML support than previous editors, which can isolate some blocks as HTML or code blocks.

To avoid a <zd-html-block> wrapper:

  • Before you copy from Notion or similar tools, make sure the content does not include unsupported HTML or code elements
  • Paste as plain text to avoid unsupported code that triggers automatic isolation
  • Use the new article editor's built-in tools after you paste to apply styles as needed

To convert HTML blocks for visual editor use:

  1. Click the HTML block in the new article editor
  2. Select Unlink to remove unsupported markup. The editor shows which markup it will remove.
  3. Review and confirm the changes. You can then edit the block in the visual editor.

If you apply bold or other styles to text in a formatted text block, the block can turn into an HTML or code block. Use Unlink to return it to visual editor mode.

Attention: After you save, the block may revert to a code block. This is a known limitation.

Edit the source code in the HTML block

If you know HTML and need to make minor edits to an affected article, such as text edits, you can use the HTML block editor.

You can edit code within an HTML block to change the content and keep the protective HTML block in the article. When you use this option to edit content and apply your changes within the HTML block editor, your updates are saved and visible in all articles and content blocks that contain the HTML block. You do not need to republish the articles for the changes to appear.

Attention: You must be familiar with HTML code to use this option, since you will make all edits in the source code editor. Remember that when you update content in an HTML block and apply your changes, it automatically appears in all published articles.

Limitations and best practices

  • Complex formats, such as accordions or tabs that use custom HTML or JavaScript, may not be fully supported in the visual editor and may require HTML mode or simpler content
  • Use only supported HTML and styles. Prefer inline styles, for example, style="height: 50px;", over deprecated attributes.
  • Review pasted content for unwanted styles or HTML blocks every time before you publish
  • Use the editor's preview feature to check how your article looks to end users

If you encounter persistent issues or the Unlink feature is missing, contact Zendesk Customer Support for further help.

For more information, see Transitioning to the new article editor.

Powered by Zendesk