So, I agree let's focus on revamping the widget catalog as a first step. Let me know if you need any help with this.
As for the project organization, I'm not going to push hard to change this if you're happy with it, I just wanted to point out the tradeoff that is being made there. Basically we are opting for ease of ingesting a widget into Nebula at the expense of effectively maintaining it. This is not so much of an issue if there is no real activity for the widget, but if you do, then your build status, issues, feedback, etc is all muddled together with everything and it is a problem to constantly disentangle what is relevant for your widget from everything else. This organization (or lack of) makes Nebula a pretty effective dumping ground for widgets, but I think gets in the way of managing active development. It's true that we do have different models now tho (NatTable as a subproject, everything else in Nebula itself), so I guess I'd just encourage other widgets to split into subprojects if they are encountering any of the pain I just mentioned.
Cheers,
Edwin