[MAGNOLIA-8058] DOC: Update 'What is possible in LD' based on newish 'config' decoration Created: 13/Apr/21  Updated: 10/May/21

Status: Open
Project: Magnolia
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Martin Drápela
Resolution: Unresolved Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Relates
relates to MGNLSITE-102 DOC: Yaml-based site definition howto... Closed
relation
is related to MAGNOLIA-8057 DOC: Configure CORS using decoration Selected
Template:
Acceptance criteria:
Empty
Task DoR:
Empty

 Description   

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

 


Generated at Mon Feb 12 04:29:16 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.