Yes, developer documentation is in need of a major overhaul. It is so incomplete and missing so much, it makes it hard to develop correctly.

There should be good documentation on the bx_alert system, exactly how it interacts and what can be intercepted and what all creates alerts. Since this is a major way to create modifications without core changes. It needs amazing documentation.

I'm a pretty smart, yet simple guy. If I read something, and it is docs from say UNA staff, or your website, it should include every step. You must write documentation as if the person who is reading knows nothing about what you are doing, and if he follows the steps from point a to point b, it should work. Not take hours to figure out a step wasn't included or "assumed".

UNA is buggy, it will take a lot to hold you to the well tested release of UNA 14 stable. But I think differently than most, and my grey hat hacker side has me poking things. We will see what all I find I can break. 😎👍

Things have come a long way since my Dolphin 5 days. Its been nearly two decades. But documentation has been a issue since then. If you really mean it, do it. And do it well.