Rich Text Block Limitations & Bugs

In this course, we'll use RTB to indicate the Rich Text Block, and RTE to indicate an Rich Text Element such as paragraph or heading within that block.

But outside of those, there are limitations;

• ~No ability to add custom attributes or IDs to the content inside of your RTE~
• > This was recently added to static RTB's only. You can now class and ID individual RTE's within an RTB, but only on RTB's that are not CMS-bound.
• No tables support
• > Now added
• No support for nested lists

Static RTB's v. CMS-bound RTB's

The static RTB's and CMS-bound RTB do not have exactly the same feature set or editing experience. Similarly, RTB editing within the designer v. within the editor has some minor distinctions.

Editing RTB's

Designer - Static ( unbound ) RTB's can be edited directly on the canvas. CMS-bound RTB's can only be edited from within the CMS item dialog.

Designer ( Editor mode ) - Same experience however you can more easily go from seeing CMS-bound rich text content on a specific collection page, and access the correct CMS item dialog for editing that content. Still no WYSIWYG view.

Editor - Excellent support for RTB editing, in that it is currently the only place you can edit your CMS-bound rich text content in a WYSIWYG view where you can see your own styling and page context.

Styling RTB's

Designer - Static ( unbound ) RTB's can be styled directly on the canvas.

CMS-bound RTB's must be unbound first from the CMS, or you must create a new RTB with the same RTB class for styling purposes.

Designer ( Editor mode ) - no styling, this mode is for content-editing only.

Editor - no styling, designed for content-editing only.

RTE's and Feature set

The elements are pretty much identical, however occasionally new features are added which only work in the static RTB's.

? code block

17-Dec-2023 a new code block was mentioned, however it does not show in the editor.

12-Dec-2023 some form of Markdown support was added, which we're investigating.

Markdown Support

17-Dec-2023 Webflow made an exciting announcement regarding markdown support, however it was a bit vague.

We need to test the new feature thoroughly however this appears to be the current shape of things.

You can;

• Use Markdown-like entry within designer and editor, in either static RTB's or CMS-bound RTB's. For some people, it's more natural to type markdown e.g. **text** than it is to type "text", highlight it, and click the bold option on the menu.

You can not;

• Use any Markdown styling that is not already supported by Webflow's RTB, including...
• > Strikethrough

‍

Notes;

• Code blocks are not yet supported in the Editor, and are probably not supported in RTBs yet overall. However the _``` technique for identifying a code block doesn't work to generate either the code block or an embed RTE.
• If you put spaces between your content and your markdown it generally will not register as markdown.

```

fooo

```

Where is this useful?

• Quickly bold something by typing _**text**
• Quickly italicise something by typing _{_text_}

‍

‍

‍

‍

‍

‍