I just started using Vapor 4 seriously and noticed that the style guide which was part of the Vapor 3 documentation is no longer part of the Vapor 4 docs. Having a background in Ruby on Rails myself, I really like how such a style guide can help simplify naming & base structuring processes by providing sensible & flexible-enough suggestions for typical use cases. This can not only help unexperienced developers just starting with backend development to follow the separation of concerns principle, it also makes it easier for experienced developers to switch projects.
While Ruby on Rails strictly follows the Convention over Configuration principle, we don't have to go as far as auto-generating the structure for every "blank" project. But I think having a suggestion for a base structure liek in the old docs and maybe even an optional template which can automatically creat it is a good idea.
In my project, I am now following the architecture style guide from Vapor 3 (due to the lack of an updated one), but I'm missing guidance on the
Tests subfolder, it only provides tips for the
App folder. But maybe that's because testing is lacking documentation and tips overall in the entire documentation, but that's probably a separate topic.