Code view

**Code view lets you inspect and edit the underlying HTML of an article directly in the Advanced WYSIWYG editor, giving you control over markup the visual editor cannot expose.

When can you use Code view

• Inject custom HTML elements the visual toolbar doesn't support
• Apply inline styles to specific elements
• Embed FontAwesome or other icon snippets
• Fix unsupported tag errors flagged by the editor
• Add symbols or icons into table cells
• Search within HTML using Ctrl + F

Automatic HTML formatting

The editor automatically standardizes indentation and spacing each time you open Code view. This only runs on entry — not on save or publish — and does not affect custom HTML or script blocks.

Searching in Code view

Use the built-in search to locate specific HTML elements or text within the code.

Saving changes

Changes in Code view are not saved automatically. Press Ctrl + S before switching back to the visual editor or navigating away.

Unsupported HTML tags and attributes

The editor flags unsupported HTML tags and attributes instead of removing them, so you can review and correct them.

When does this happen?

• When switching an article from the WYSIWYG editor to the Advanced WYSIWYG editor — unsupported content is flagged automatically
• When you add unsupported tags or attributes directly in Code view — the editor flags them on parsing

What the editor does

• Detects unsupported tags (e.g., <marquee>, <blink>) and attributes (e.g., onmouseover, style="text-decoration:blink")
• Marks flagged elements with tooltips and block highlights without disrupting surrounding content
• Blocks visual editing of flagged elements until resolved in Code view

Supported tag categories

Text formatting

• Abbreviations (<abbr>)
• Blockquote (<blockquote>)
• Headings (<h1>–<h6>)
• Paragraph (<p>)
• Subscript / Superscript (<sub>, <sup>)
• Inline code (<code>)

Structure & media

• Images (<img>)
• Links (<a>)
• Tables (<table>, <tr>, <td>)
• Lists (<ul>, <ol>, <li>)
• Dividers (<hr>)
• Spans and divs with supported attributes

Best practices

• Use Code view only when the visual editor cannot accomplish the task. Direct HTML editing increases the risk of introducing unsupported tags or broken markup.
• Stick to supported tags when writing or pasting HTML. Unsupported tags trigger flags and block visual editing of that section until corrected.
• Use Shift + Tab to reformat code after making edits, keeping markup readable and easier to debug.
• Save frequently using Ctrl + S, especially before switching modes. There is no auto-save and no recovery for unsaved changes.
• Resolve flagged elements promptly. Leaving them unresolved prevents visual editing of the affected block and can cause unexpected rendering issues on publish.**