insites-cms

Structure Insites CMS pages and partials by treating pages as controllers, using GraphQL as the data layer, and keeping HTML exclusively in partials. This separation enforces consistent architecture and prevents duplicated template logic across projects.

The recommended data access pattern for Insites CMS templates uses GraphQL as the standardized data layer across pages and components. This approach ensures explicit separation of concerns and prevents scattered data fetching logic.

Organize Insites layouts and assets by applying architecture-driven rules that standardize file structure, separate HTML into partials, and manage context exports and translation keys for scalable site development.

Liquid templating works with Insites CMS to enable clean component reuse through partials. Using Liquid alongside context exports and translation keys ensures HTML components remain modular and maintainable.

Use background jobs in Insites CMS architecture to handle asynchronous processing tasks across projects. They integrate with the standard file structure and adhere to the same separation of concerns governing pages, partials, and GraphQL data access.

Insites CMS architecture suffers from duplicated template logic when development lacks consistent rules for partials, GraphQL data access, and context exports. Applying standardized architecture rules eliminates scattered patterns and ensures maintainability.