No tutorial, no, I agree that it deserves to be a bit better documented
The documentation is super important if people are to propose changes.
It’s a real necessity (even though there is already a written and video base), there should be written documentation on the general structure of Gladys, both frontend and backend (directories, config files, interaction), even brief at first and that can be expanded in the same way as for compatible hardware. For someone who comes to the project and would like to help with development it’s a bit complicated to get an overview or know where to start; on an open-source project the community is the main force to help development both in terms of software and deployment!
I’m talking about documentation for the Gladys part, the one that is necessary to develop integrations or improve the frontend; in my view it’s not necessary for the Gladys Plus part.
About time!!! You’ll be able to put away the tanning cream!
Since the start of your vacation there were still 53 nervous breakdowns and 12 missing-person reports filed!!!
More seriously, I hope they were worthwhile and that you came back full of energy and ideas for Gladys! And like a friend says about health, you always have to take good care of yourself because "If you want to go far, spare
A vacuum cleaner is still a vacuum cleaner! In Gladys we standardize how it works: we describe functionally what the device can do, regardless of its brand.
You’ll be able to put away the tanning cream! 
and 12 missing-person reports filed!!! 
Robot vacuum cleaners are a classic in the connected home, and I think a native type makes perfect sense.
