yabwe/medium-editor

It's sad to say but Medium Editor might have lost it's way, but We're coming back up soon!

ksorv opened this issue · 10 comments

ksorv commented

As anyone can see that we don't currently have enough maintainers that are active to do work on this project. Some of us are trying hard to get things movings but our project was written with execCommand which is now obsolete.

I'd redirect you guys to Trix.

Take a look at the home page and you'll find some things you need to understand why Medium editor might not work everywhere.

Have a great time ahead guys and gals.

This is NOT Official announcement of shutting this project down.

But it's just my perspective by looking at other editors(maintained) andour editor(Almost gone!)
: (

Know We're working to get this up!

Thanks for sharing. It looks amazing. Do you know how it compares to ProseMirror ?

ksorv commented

I've not used Prose Mirror and found Trix when searching for some alternative to execCommand. That is how I found Trix.

But after a quick look I can say Trix is just a editor like medium editor with no bigger API standing over it.

Where as Prose is something different, It's made for markdown, as most editor works only on HTML. And it also provides much more stuff like collaboration out of the box.

Prose is really cool indeed.

And there are many others:

TipTap
DraftJS
QuillJS(probably the one used by Medium)

I've used these somewhere sometime.

You can take a look on these.

🙌

I found this editor and it looked soo nice and perfect fit. But I looked at the commity history, PR and issues and I worry to start using it.

Have you considered joining https://opencollective.com/? I send few bucks each month to several projects to their maintainers. Such a huge product used by thousands of developers has a potential to back up a full time developer.

ksorv commented

Why a complete rewrite? Demo is working on a desktop. Starting from scratch is very risky project and people would be doubtful to support it.

ksorv commented

Chance? It depends on a number of actively used installations. If the project is in bad situation and developers need help and switching to different library would be costly, then people may favor to send some bucks. Count with less than one percent conversion ratio.

But I would recommend you to send emails to the companies first. Some are noted on project pages. Describe what you want to achieve, how long it will take and how much it will cost.

Create a big fat red banner at top of GitHub and project website leading to new discussion about the project future. You may release new version that will display this message in npm output. I have seen a library asking for help when I installed it.

I think that one time goal would be more attractive than regular payments. E.g. define a scope, budget and ask for help on project/github web. Release minor fix (for example for mobile phones - the menu above cursor is colliding with Android keyboard) and ask for help there too. If there would be a security fix, you could get bigger attraction.

@literakl I would highly recommend installing github's Stale bot plugin (https://probot.github.io/apps/stale/). It would automate the process of clearing out the older issues that have not been closed, yet are so old that may no longer be of active concern. Basically it would ensure that the only issues that are open are active ones. That's probably going to give this project a better starting point than having 300 daunting open issues that can't possibly all be addressed.