plate
plate copied to clipboard
udecode
[Discussion] Who is using Plate in production?
Plate is being adopted by a lot of companies right now, we would love to list some of them on https://plate.udecode.io/
If you are using plate, and you don't mind sharing this fact with the world, please post your company name with a link in the comment below. We appreciate it a lot.
We recently revamped our entire editing experience in Avion. There's a lot of RTE libraries out there, but we ended up choosing Plate to use as our foundation:
Under the hood, we are storing everything in Markdown and converting to/from Slate syntax when editing/saving. We're pretty happy with the end result 😄
We recently revamped our entire editing experience in Avion. There's a lot of RTE libraries out there, but we ended up choosing Plate to use as our foundation:
Under the hood, we are storing everything in Markdown and converting to/from Slate syntax when editing/saving. We're pretty happy with the end result 😄
Nice work @tjramage.
I am also looking to implement plate in a similar fashion. What method are using to convert to/from Slate syntax when editing/saving?
Good question @rjlg. That was definitely one of the trickier parts for us. In a nutshell:
-
When saving, we serialize Plate/Slate --> HTML, and then convert HTML --> Markdown. I know that sounds wasteful on the face of it, but this was the easiest and most robust option for us (plus there are some really mature HTML / Markdown conversion libraries out there).
-
When loading the editor, we convert Markdown --> HTML, and then feed that to our instance of Plate (which already has HTML deserialization support).
Worth noting that we hit roadblocks with the HTML serializer within Plate. So we ended up forking the code to add proper support for encoded entities and URI encoding within content (and a few other tweaks). I'm planning on contributing these enhancements back into the Plate repo at some point soon...
Good luck! 👍
Good question @rjlg. That was definitely one of the trickier parts for us. In a nutshell:
- When saving, we serialize Plate/Slate --> HTML, and then convert HTML --> Markdown. I know that sounds wasteful on the face of it, but this was the easiest and most robust option for us (plus there are some really mature HTML / Markdown conversion libraries out there).
- When loading the editor, we convert Markdown --> HTML, and then feed that to our instance of Plate (which already has HTML deserialization support).
Worth noting that we hit roadblocks with the HTML serializer within Plate. So we ended up forking the code to add proper support for encoded entities and URI encoding within content (and a few other tweaks). I'm planning on contributing these enhancements back into the Plate repo at some point soon...
Good luck! 👍
Thanks @tjramage!
Look forward to seeing your enhancements.
We're very happy Plate users at https://dropdeck.com, designing slides based on text input. Happy for you to add our name and logo on your list! 😃
Tiddlywiki：Main framework https://github.com/Jermolene/TiddlyWiki5
Use plate in a plugin: https://github.com/tiddly-gittly/slate-write
Demo: https://tiddly-gittly.github.io/slate-write/
