What should be avoided to maintain adherence to the Helix guidelines in your Sitecore project?

Maintaining adherence to the Helix guidelines in a Sitecore project emphasizes the importance of architectural integrity, and one of the fundamental principles is the avoidance of cyclical dependencies.

Cyclical dependencies occur when two or more components depend on each other directly or indirectly, which can lead to a tangled architecture that is difficult to manage, test, and maintain. Such dependencies can complicate the build process and hinder the modularity that Helix promotes. By avoiding cyclical dependencies, developers can ensure that modules remain independent, making them easier to work on in isolation and more reusable across different projects. This modularity aligns with the Helix principles of feature orientation and independent modules, which facilitate the clear separation of concerns and enhance the overall solution architecture.

In contrast, adhering to a modular structure, focusing on feature orientation, and ensuring the independence of modules are encouraged practices within Helix. These approaches promote a clean, maintainable, and scalable architecture that can adapt to changing business needs without introducing unnecessary complexity.