This reminds me of Atlassian's god-awful WYSIWYG editor.

In both cases, I get that some users can't or don't like to use a machine grammar/markup, however simple. For some people markup is bad UX. Give them a WYSIWYG; that's fine.

But don't remove the markup editor if your WYSIWYG editor is anything but a perfect one-two-one replacement for markup (and I have never seen one that satisfies that).

IIRC there was a time when Confluence axed their markup, and inevitably a table or a template would get completely screwed, and there was nothing you could do but recreate it. TERRIBLE design.

> This reminds me of Atlassian's god-awful WYSIWYG editor.

Oh my goodness: triggered.

I've barred the use of Confluence at our company specifically because of this.

"But, but, we used it at blah company."

"Yes, so did I at blahblah company, and it was unbelievably crappy and made me angry every time I had to edit a document: we're not using it."

I DO NOT want to have to use what amounts to an extremely buggy, capricious, and neutered version of Microsoft Word 6 to edit the contents of a web page.

I will become extremely displeased with you if you waste my time by trying to persuade me it's a good idea. It's not.

Because of this we've implemented a tool called `mark` [1], which allows to write articles in markdown and render them as native Confluence pages.

If you're interested in having self-hosted service for that, just drop us an e-mail here [2].

[1]: https://github.com/kovetskiy/mark/ [2]: https://mark.reconquest.io/