1
0
mirror of https://github.com/ianstormtaylor/slate.git synced 2025-08-18 05:01:17 +02:00

update readme

This commit is contained in:
Ian Storm Taylor
2016-07-13 14:30:15 -07:00
parent f741a47ee8
commit d9eb6a380e

View File

@@ -18,13 +18,9 @@ _**Slate is currently in beta**. It's useable now, but you might need to pull re
<br/>
### Why?
Why create Slate? Well...
Why create Slate? Well... _(Beware: this section has a few of [my](https://github.com/ianstormtaylor) opinions!)_
(Beware: this section has a few of [my](https://github.com/ianstormtaylor) opinions on the existing rich text editor landscape!)
Before creating Slate, I tried a lot of the other rich text libraries out there. None of them were simple enough to use, but well-designed enough to handle complex use cases.
What I found was that while getting simple examples to work might be possible, once you started trying to build something like [Medium](), [Dropbox Paper](), or [Canvas]()[Medium](https://medium.com/), [Dropbox Paper](https://www.dropbox.com/paper) or [Canvas](https://usecanvas.com/)credibly hacky things to get the user experience you wanted. And some experiences were just impossible.
Before creating Slate, I tried a lot of the other rich text libraries out there. What I found was that while getting simple examples to work might be possible, once you started trying to build something like [Medium](), [Dropbox Paper](), or [Canvas]()[Medium](https://medium.com/), [Dropbox Paper](https://www.dropbox.com/paper) or [Canvas](https://usecanvas.com/), you have to resort to very hacky code to get the user experience you wanted. And some experiences were just impossible.
Here's how Slate compares to some of the existing editors out there: