No, bro. I'm afraid I don't 🤷‍♂️

Thanks for reading 🙇‍♂️

Thanks for reading!

Hi! I haven't had a chance yet since we're busy working on some big features for the editor currently. But I there will be more coming!

I fully agree that the editor is a long term investment and I'd be VERY hesitant to switch if I was you. I am not aware of any system for easily switching your document representation to slate from draft. If I were in your shoes, I'd make a very small proof of concept with slate and only target those things which are causing you a lot of pain in draft. Only if those things turned out to be much easier in slate would I even consider the change. Avoid the rewrite if you can.

Good question! It can be quite a feat - one thing to look into is if there's any frameworks available that fit into the other tools you're already using. For example, if you use the Apollo framework for GraphQL, a lot of work has been done to make it possible to get your application to work offline. Or you could look at a library like Automerge and see if that can help you deal with those pesky conflicts. Either way, you should expect to invest some significant time. What we did at Kitemaker was to incrementally improve pieces to get ready to move to offline-first before we took the plunge and tackled the really big pieces.

Glad you liked it! Thanks very much for reading 🙌 Follow us here or on Twitter if you want more content like this going forward.

Glad you found it helpful! Follow us on Twitter or here on hashnode to get more articles on Slate in the future 🙌

Really nice article! Just a small "bug": You say "For example, the purest form of red, green, and blue colors is as follows." but your blue is purple

Thanks for reading! 🙌