> Consistent with Payload's goal of making you learn as little of Payload as possible, customizing and using the Rich Text Editor does not involve learning how

> Consistent with Payload's goal of making you learn as little of Payload as possible, customizing and using the Rich Text Editor does not involve learning how to develop for a Payload rich text editor. Instead, you can invest your time and effort into learning Slate, an open-source tool that will allow you to apply your learnings elsewhere as well. I have to say, this callout from the JSON-based Rich Text Field docs [0] really resonated with me. Rather than build out something yourself that would further lock folks into your platform (and force them to customize yet another bespoke tool), you leaned on an existing, mature, and capable framework for rich text editors, Slate [1]. And your stated reason—to “allow you to apply your learnings elsewhere as well”—was really appreciated. It shows a lot of respect for time and resources of the individuals using Payload. I don’t have a specific need for a headless CMS right this second, but I can promise that Payload will be my first candidate to review when I do. Previously, it would’ve been Strapi, as I’ve used that tool already for several projects. But that one paragraph really struck me. [0]: https://payloadcms.com/docs/fields/rich-text https://payloadcms.com/docs/fields/rich-text [1]: https://docs.slatejs.org/ https://docs.slatejs.org/