[META] Proposal for Changes

This issue is a meta-discussion about how to increase collaboration from others, and push the library forwards. While we usually want to avoid breaking changes, it can hinder innovation. What I'm proposing is...

- Further adopt [Semantic Versioning](https://semver.org/) so that breaking changes are clearer
- Yes that means more frequent major versions, but it will be clear when a breaking change happens
- Document semantic versioning usage
- Build out the CI to build nuklear.h for us, so that git conflicts don't happen
- Further adoption of Doxygen
- Make a emscripten web-demo embedded as part of the doxygen github pages
- Automated unit testing. While we do build out the demos, would be good to have a simple script that unit tests some of the functionality
- Add another maintainer? Any volunteers?

cc @rswinkle @sleeptightAnsiC

No specific files, tests, or entry points are named. Start by reviewing the current release, documentation, CI, demo, and testing setup, then split the proposal into scoped issues; done requires maintainers to select and define an actionable change.

Written by the indexing model from the issue text.