The Sitecore is working towards making guidelines/Principles to make Sitecore product robust. And for this Sitecore defined a set of recommended practices /design principles so that Sitecore project can be easily maintainable and extensible.
With respect to above, Helix principles defined the guidelines for template field’s that, it’s good to create the base template (interface template) for fields which being used by more than one module. With this it will work as a Interface template and modules can inherit it or extend the functionality.
In the project where many developers are working on their own module then it’s good to have discussion with Team members to identify the modules/templates which can be utilized before creating new classes/templates, and it will help to come up with base template which can be inherited in the module.
Sometimes lack of interaction between team members or strict deadline will not allow for discussion then it will directly impact the Content Tree with redundant fields in the templates and it’s difficult to review the templates when number increases at a later stage, which leads the project to inconsistent mode.
For finding the redundant fields in Templates, I have created a SQL Scripts which needs to be run against Sitecore Master DB.
File Path: https://github.com/AmitKumar-AK/CT.SC/blob/master/src/Foundation/Utilities/SQLScripts/GetRedundantFields/GetRedundantFields.sql
The step-by-step details for using this SQL script present at https://github.com/AmitKumar-AK/CT.SC/blob/master/src/Foundation/Utilities/SQLScripts/GetRedundantFields/README.md
Ping back/Issues:
- why sitecore helix
- what is sitecore helix
- sitecore helix and habitat
- Sitecore Helix Recommendation and Conventions - Helix 2.0
- sitecore helix advantages
- sitecore helix best practices
- sitecore helix certification
- sitecore helix documentation
- sitecore helix dependencies
- sitecore helix foundation layer
- sitecore helix jss
- sitecore helix multisite
- sitecore helix pattern
- sitecore helix structure