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

[ksorv]

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!

[friksa]

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

[ksorv]

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.

🙌

[literakl]

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]

Hey Leos,

We can try that. But after 2017 project had almost no updates.

We need to re-write to whole API, might also need to move from Content-Editable to custom wrappers and stuff.

It is too much work...

We can try for open collective, But i dont think anybody will even donate because project cant be used right now as they want to.

If we can raise somewhere around 2 then, I think I'll be able to go all in and start writing the project from scratch.

That makes it, $10/month, 200 People.

And i dont think That's reachable...

What you think? Is that possible?

On Sat, Aug 15, 2020, 7:21 PM Leoš Literák notifications@github.com wrote:

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.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/yabwe/medium-editor/issues/1547#issuecomment-674398703, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIE2X26NZCCFNTZX6IZWJELSA2HFTANCNFSM4OP4ZYSA .

[literakl]

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]

Ohhh not like that, I just think it's about time we move on to TS. That will help alot... As to using latest JS features!

And content editable is going down with every new update to browsers too! We've to think about that too!

But again it's all on the community, How they want the project to be? And currently we don't even have enough people to give us opinions! It's getting harder everyday to come back and work on this.

On Sun, Aug 16, 2020, 10:58 AM Leoš Literák notifications@github.com wrote:

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.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/yabwe/medium-editor/issues/1547#issuecomment-674481437, or unsubscribe https://github.com/notifications/unsubscribe-auth/AIE2X26YVB7XINCIE4APTN3SA5U7PANCNFSM4OP4ZYSA .

[literakl]

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.

[literakl]

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.

[literakl]

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.

[LDubya]

@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.