Now that one can provide module configuration by YAML file, many useful configurartions are possible with light development that were not possible in the past.

We should clearly document this new best-practice.

In particular we should update these two sections:

(What you can and cannot do with LD)

https://docs.magnolia-cms.com/product-docs/Developing/Light-development-in-Magnolia.html#_what_is_not_supported_in_light_modules

https://docs.magnolia-cms.com/product-docs/Developing/Light-development-in-Magnolia.html#_what_can_you_do_with_light_development_now

Probably we need to generally explain how to use the new config.yaml

ANd then we should mention the common key use cases. These would include at least:

• Sites
• CORS (on sites)
• App launcher (I think!)
• ... browse other module config to see what else would make sense...

Content from Maxime in this ticket may be useful:

https://jira.magnolia-cms.com/browse/MAGNOLIA-8057