CRAFT CMS REDACTOR FREE

But our long-time gripe has always been mixing plain-text (formatted) content and the rest of what Craft has to offer. So the above ticked-off our desire for a better WYSIWYG. More importantly, the extensibility of these frameworks is what drove our decision, where we've used it on Formie to handle picking variables in text fields, and a basic rich text editor. Tiptap itself is also built on top of ProseMirror (opens new window) which is used on some pretty notable sites such as Atlassian and the New York Times. We certainly didn't want to build yet another editor to an already overgrown space, which is why we looked to tiptap (opens new window) which has been amazing to work with.

CRAFT CMS REDACTOR FREE

With content stored as blocks, we're free to iterate over those blocks and output it just how we like. richtext class and setup custom CSS for any elements inside that class. To get around this, we've wrapped rich text content in a. This gets a whole lot more work when introducing other HTML elements - Headings being another great example. For a Redactor field, we'd have to parse the HTML and add in those classes. Say, we want to add mb-4 to the bottom of every tag, because Tailwind is un-opinionated about paragraph tags. It's a neater and cleaner way of storing content, so you're not bound to raw HTML.įor a practical example, we use Tailwind (opens new window) extensively, but this poses a problem for the HTML in a WYSIWYG field.

We love the modern approach of a block-based WYSIWYG field. Great question - does the world really need another WYSIWYG? Well, yes and no.įirstly, for Craft, there's historically only been a few options - Redactor (opens new window) and more recently CKEditor (opens new window), which both do a fine job, but produce raw HTML for use in your templates.

Craft cms redactor