Hi Shades, maybe you've already thought about it, I'm not familiar with AsciiDoc but I would recommend editing in markdown (but I may be biased since I do everything in markdown these days) and converting to AsciiDoc using pandoc, see here for examples.
Don't worry, not many people are. Which is also why AsciiDoc software is in the state it is. And if you would ask me, Markdown would have been fitting the documentation bill just fine. Heck, even a wiki would have been sufficient. But not my call. Actually, there is one person at the company receiving the documentation, who made a ruckus about AsciiDoc and now we are all stuck with it.
Before this, I had never heard of AsciiDoc. Gaining this knowledge did not improve my career or life in any way. And continuing with this honesty, it feels like a person or group of persons thought about making a standard better than the 10 earlier attempts of making the standard for documentation. Result? AsciiDoc is now the 11th standard.
While I am put in charge of converting existing documentation to AsciiDoc, those that need/want to make new documentation are not willing to give up their Word GUI habits/mindset to go back 20 years GUI concept-wise. For myself and my work-flow, the current AsciiDoc editors are adequate. As a proponent of wanting to separate content from layout, I don't use Office much anymore. Instead, I use PanDoc to generate the same document in whatever format the receiver wants.
Knowing full well that I am weird this way (and probably many other ways too) I can't expect everyone to work like this. Actually, it is my opinion that most people would not be able to create documentation without an Office suite anymore. Or even want to, for that matter.
To get a better/quicker adoption of AsciiDoc, it would be a big benefit to have software that enables people with "Office"-mindset to work as they are more or less used to. Hence my request for a new place where to look for AsciiDoc editors that look like Word/WordPad. Asking those same people to work with PanDoc, a command-line tool, to convert MarkDown to AsciiDoc, I think that would be too much. For myself though, your idea has merit.
It would seem better just to wait patiently until AsciiDoc software improves before pushing it onto others. In the mean time I'll make scripts to handle the conversion of existing documentation "automagically", reducing that headache for myself.