craft-twig-guidelines

Standardize Twig templates in Craft CMS 5 by enforcing consistent variable naming, robust null handling using the ?? operator, and strict include isolation to ensure predictable rendering and maintainable components across teams.

Include isolation in Twig requires passing variables using the 'only' keyword, preventing unintended variable leakage into components and ensuring predictable, defect-free rendering across your Craft CMS templates.

Handle null values safely in Craft CMS Twig templates by using the ?? operator for fallbacks, optionally leveraging the ??? plugin if present, to prevent unpredictable rendering and template defects.

Yes, these Twig coding standards apply to atomic components, views, and layouts, enforcing frontmatter-driven metadata and requiring comment headers for clarity and maintainable template architecture.

Use collect() for props and class collections in Craft CMS Twig templates to standardize data handling, avoid hardcoded colors, and enable scalable, maintainable component architecture without relying on macros.

Using macros for Twig components in Craft CMS is discouraged as it leads to inconsistent template architecture; standardizing on includes with strict isolation and frontmatter-driven metadata ensures more maintainable and predictable results.