Show HN: Edtr.io – Intuitive web editor, open source and fully adaptable
51–57 of 57 posts
Re: Show HN: Edtr.io – Intuitive web editor, open source and fully adaptable
#52This is really nice. One note: the landing page doesn’t mention the MIT license or commercial use. I had to go to the repo to figure it out. Would love to look into integrating this editor in our email client. Is there an easy way for us to chat?
If you're going to use it commercially, don't miss https://grapesjs.com/ It has a much more stable API, UIs and it has an MJML preset. Under a permissive BSD-3 license.
Re: Show HN: Edtr.io – Intuitive web editor, open source and fully adaptable
#53I was thinking of building something similar. Any other alternatives to similar solutions?
more of a complete CMS but has wysiwyg editing and UI blocks - https://webiny.com
Re: Show HN: Edtr.io – Intuitive web editor, open source and fully adaptable
#54I was thinking of building something similar. Any other alternatives to similar solutions?
more of a complete CMS but has wysiwyg editing and UI blocks - https://webiny.com
Re: Show HN: Edtr.io – Intuitive web editor, open source and fully adaptable
#55However when you go to add a hyperlink on mobile, it's not adding it where the cursor is, instead adding it at the start of the current line.
Am seeing this on latest Chrome on Android 10.
Re: Show HN: Edtr.io – Intuitive web editor, open source and fully adaptable
#56This looks really cool but I think maybe an image on the landing page might help
The entire page is editable and a live demo. It could probably be higher up, but it is mentioned on the page.
On my screen (1080p) I have to scroll to see this and it's in plain small body text, doesn't stand out at all.
Re: Show HN: Edtr.io – Intuitive web editor, open source and fully adaptable
#57Earlier quoted context omitted.
Yeah, but it only makes sense to do so on a page that already is using react. If you are using some other JS framework it will add 140kb dep on react+react-dom - which might be a problem (or not depending on your use case).
Definitely a good point. Just wanted to note that you could write a renderer in some server language that outputs static HTML. And only use the editor to make that static content editable (loaded asynchronously or on a different route). The serialized state is easy to parse by design.