The UI/UX is really just not right for a technical documentation. Personally, I'd like to see new format along the lines of http://devdocs.io/
as a reference implementation (or possibly inclusion in devdocs.io). It's simple, very expandable, easy to search, and the UI makes sense (unlike the current documentation engine which I find very confusing).
With that said, someone needs to really look at the structure of Livecode's bits and pieces. There are bunch of API inconsistencies, unpredictability and general oddness with the structure of the documentation -- at least as presented in the current Documentation Engine.
What pray-tell am I talking about?
Do this. Open up the documentation in LC. Under "type:" (whatever the heck that means), click on Library. Now scroll through the items that are a "Library". There's 45 entries for Libraries and 32 of them start with merg?
Personally, I'd like to start by from the beginning coming up with standard definitions and a general organizing of the documentation from the top down. It really needs it.
What are the high level "Topics"? What are the sub-sections of each of these Topics? Do those get broken down to another level or not? Is the Community even able to drive the boat on this or does this have to come from LC Ltd.?
I'm on board to help as I can with any efforts. I'm glad this is taking place on the Forum and not the list BTW.