for instance I didn't really want to use your LiveData/MvvM stuff at the moment so the first thing I had to do was strip all of that out. The #1 thing missing from the K/N community is detailed, up-to-date documentation on how things are setup and why. I feel like you guys have the expertise and manpower to fill that gap if you chose to

if you didn't want use moko-mvvm - you can not use it 🙂 you have problem with removing this dependency? And why you didn't want use it?

I just meant the template is set up with that this adding a step to remove it. Just goes back to my comment on maybe having a few sample projects per library. I didn't want to use it because my library was just simple business logic that didn't require that architecture

we had two ways - to make the template empty so that there was only a configuration. Or make a template right away with an example. By discussion, they came to the conclusion that the example will help to figure out what is arranged and disable it easily - just turn off unnecessary gradle modules with features. maybe later we separate config and sample...