Hi @btopro, thanks for starting this thread. It’s clear already that different people want very different things out of an editor.
I like Markdown, personally. Though I think it depends somewhat on what you are trying to do. Most of what I write is text with lists and links.
If I were making more image-heavy landing pages, I’d probably want something that knows how to deal with components or blocks.
Ok, I suppose now is as good a time as any to unpack this quote a bit
We’ll definitely keep TinyMCE for our initial long-term-support release series, v1.x. The goal there is to provide a stable, predictable option for people to build websites on, and what better platform than the classic editor with TinyMCE? This is stable, proven technology that has been used for millions of sites and billions of conent edits.
Which editor ClassicPress uses by default in future versions is up to the committee. We’ve already set the direction for the v2 release series, which is around building a ClassicPress plugin directory and moving some less-used features of the core software out into plugins.
Having our own plugin directory will also allow us to provide and recommend plugins like an alternative editing experience. This would be opt-in by default, and I could definitely see HAX fitting into that kind of role in the ClassicPress ecosystem.
In order to change from TinyMCE to another default editor in a future version of ClassicPress, we’d have to get lots of testing via a plugin, and wide agreement among the community that this is a change we want to make.
So far the way we collect and measure this agreement is via votes on our petitions site, but I’m happy to discuss future plans and HAX in general here too.
Thank you for using web components!
I will make some time to try out HAX soon, in the meantime I have a few questions:
I’ve shared a bit of my perspective here, but what do you think HAX’s role could be in the ClassicPress ecosystem?
How does the HAX editor behave in terms of backwards and forwards compatibility with TinyMCE? If I make a complicated post in TinyMCE, how does it translate over to the HAX editor? If I make a complicated post in HAX, and then disable it and edit it via TinyMCE, what happens?
I’ve thought for a while that it could be interesting to leave
post_contentas rich text using TinyMCE, but start to think of a post as a list of one or more custom fields, of which
post_contentis just one. This could avoid some of the pitfalls of storing a blob of structured content inside the unstructured not-quite-HTML
post_contentfield, and it could also be a way around many potential backwards compatibility issues. Is storing each component as a custom field a direction that you considered for HAX?