Rendering solutions editor content #2799
leedia-tech
started this conversation in
General
Replies: 1 comment 4 replies
-
I recommend rendering the editor content at the point of use, rather than storing HTML in the database if you can avoid it, since that cuts down the risk of stored XSS and makes it easier for you to deploy fixes to your Slate -> HTML conversion. For rendering a Slate value to HTML, if you don't want to use Plate's (not at all lightweight) |
Beta Was this translation helpful? Give feedback.
4 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My application involves rendering the JSON content of the editor in a different codebase from where the editor is actually integrated. To maintain the efficiency and lightweight nature of this application, I would prefer not to integrate the entire editor in display mode.
In this context, I have two main questions:
Any tips or code snippets that could guide me in achieving this would be greatly appreciated.
Thank you in advance for any assistance or suggestions you can provide.
Beta Was this translation helpful? Give feedback.
All reactions