This blog post is a part of a collection of posts about Information Architecture within Sitecore. The blog can be categorized as a “How we do it”, and gives our view about the setup of a flexible information architecture that can be reused in multiple projects.
Within a previous posts I introduced a Content module. This module contains fields that are used in pages. The definition of the content module is:
| Name | Base templates | Fields |
|---|---|---|
| IContent | Standard template | – |
| _ContentTitle | Standard template, IContent | ContentTitle |
| _ContentAbstract | Standard template, IContent | ContentAbstract |
| _ContentImage | Standard template, IContent | ContentImage |
Pages that are constructed in the project scope, inherit one or more of the _ContentTitle, _ContentAbstract and _ContentImage templates. When we focus on the _ContentImage template, containing a Sitecore image field type, we are confronted with an interesting challenge. The Source value for the image field type has to be set to a certain value from where the editors can select images. Because images are most likely project or even site scoped we have to find a way that images from other projects or sites are not accessible in the image selector.
Continue reading “Information Architecture in a Helix Era – Part 4 – Media access in foundation and feature modules”
MY THOUGHTS ABOUT... 