Timeline for How to handle alternative presentation for a helix Feature module
Current License: CC BY-SA 3.0
3 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 19, 2017 at 10:22 | comment | added | Eldblom | @MatthewDresser I don't agree. This provides two simple solutions to one business problem without overcomplicating things. The renderings belongs to one business domain and should therefore remain in a single module - there is not necessarily a dependency from rendering 2 to site B - just as there would be no dependency from rendering 1 to Site A. Keep in mind: One entire Helix solution cover requirements of a business - even if the business is split into multiple entities. E.g. The Navigation Feature would still be covering navigation even if it cover two business entities. | |
| Jan 18, 2017 at 16:56 | comment | added | Matthew Dresser | This approach violates one of the Helix dependency principles by adding a dependency to the module on both of the sites which would be in the project layer. | |
| Jan 18, 2017 at 14:02 | history | answered | Ken McAndrew | CC BY-SA 3.0 |