As you have eventually found out what you needed, here are my 2 cents on this:
This was done.
I am not sure what is not complete, and where you couldn’t find examples. Every page has a few examples of the subject at hand. If there aren’t, we will be happy to add.
It is always easy to forget that this is an open source project. COntributions are welcomed, and I can’t remember the last time I rejected a PR to the docs page.
Download a playground and you will have everything you need to get started. There are also many examples on the playground about code structure and how to get started.
We are very strict about that, and this shouldn’t happen. There are some cases where an external engine/framework is needed (like physics engines), but anything that is not included in our playground is not supported by us anyhow. So - not sure what you refer to, maybe provide an example instead.
createScene() is just one way of starting your scene. this is what the playground does. This is not the only way.
It seems to me like you jumped into “diving deeper” before you read the getting started guide. WebXR is just a part of this framework. there are a few other aspects to it that you will need to understand in order to get everything to work. If you understand babylon, the camera system, user input, observables, you will have no problem dealing with webxr using babylon.js. If, on the other hand you will only read the webxr documentation, you will have a lot of open questions that need to be answered.
If you are referring to the WebXR documentation, that would be on me. I will forward that to my high school English teacher. I am sure she won’t be happy about it.
Once again, we are fully open-sourced. We hide nothing. Everything - source code, examples, PRs. We have one source of truth, and that is our source code. It is fully documented though it does contain a few spelling mistakes! But some great person (thanks Jason!) started correcting them, and we were really happy about it.
We are certainly not perfect, and are always eager to learn from our users. If you have any specific question, we will be more than happy to answer it.