Refactor Unicorn serialized content to follow Sitecore Helix structure #24
Description
Do you want to request a feature or report a bug?
Bug/Change
What is the current behavior?
The current Unicorn serialized content doesn't follow the practices described in Helix. Currently, the serialized content lives under a single project named Conjunction.Foundation.Content, which should be separated out into the respective projects. This means that content (settings, templates, etc) related to the Core part of the project, goes into a 'serialization' folder under the Core project.
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem
N/A
What is the expected behavior?
The serialized items should live under their respective domains, rather then being placed into a single Content project.
What is the motivation / use case for changing the behavior?
The project should adhere to the principles and practices of Helix.
Which versions of Conjunction is affected by this issue? Did this work in previous versions of Conjunction?
Development, has not yet been released.
Other information (e.g. stacktraces, related issues, suggestions how to fix)
The answer provided here should be used as a basis for the restructuring.