When working with SXA, which templates are allowed to exist within the Feature layer, contrary to Helix recommendations?

The Feature layer in the Helix architecture promotes the use of specific templates that encapsulate functionality. However, when it comes to SXA (Sitecore JSS or Sitecore Experience Accelerator), it permits certain templates, notably datasource templates, to exist within the Feature layer.

Datasource templates are integral in defining the content structure for reusable renderings. In SXA, you often create renderings that pull in data from these datasource templates, allowing for a modular approach where multiple components can utilize the same data structure. This flexibility is in line with how SXA is designed to work, emphasizing content-first experiences.

In contrast, renderings such as view rendering templates or ASP.NET Core rendering templates are typically not meant to be placed within the Feature layer according to Helix. These types of renderings align more with the Presentation layer, where they denote how data should be displayed rather than the underlying content structure. Thus, their existence in the Feature layer would contradict the Helix guidelines.

Similarly, the concept of feature templates within the Helix architecture typically focuses on encapsulating functionality rather than defining data structures or content types, which is why they are also not allowed in that layer.

Understanding these distinctions is crucial for maintaining a clean and organized architecture in Sitecore,