@johnnyboy wouldn’t the visualization of how modules are place be equally as good with the sample config file that is included in the MM package?
It shows you what the format is, but yes a thorough explanation of why it looks like it does would probably help new users to avoid many configuration mistakes. But then again, showing others many different config files wouldn’t really help if they don’t understand why others config files work and theirs don’t.
I think there will be more issues copying and pasting other configurations if there is a lot of 3rd party modules in there. For an example all 3rd party modules that require other dependencies and need the user to do a npm install in the module folder. They might just to a git pull like the other modules and then they are confused why it didn’t work because they missed the read me file for the module.
I think it’s better if there was a educative way to explain the basics of why the config files look like they do, maybe someone can do a video explaining why. I think it was @strawberry-3-141 that perfectly explained the use of commas in lines with the shopping list reference.
Stuff like that would be great for the non-experienced users out there that wants to build their own mirrors!