XY Grid Class Adoption Threshold for Multi-Developer Projects

Teams building on Foundation for Sites often face a choice between the class-based XY Grid markup introduced in version 6.4 and the older mixin-based semantic grid approach. Both systems generate comparable CSS output, but their markup patterns differ significantly. The goal of this inquiry is to establish a consistent grid implementation strategy across a codebase that includes multiple developers, varying familiarity with Sass, and a need for predictable responsive behavior across the $breakpoints map. Mixing XY Grid class markup with semantic mixin approaches across a codebase complicates maintenance and onboarding, particularly when breakpoint overrides are required. The decision hinges on trade-offs between markup verbosity, design-system cohesion, and long-term maintenance overhead.

• What criteria should govern the selection of XY Grid classes versus semantic mixins for new component development?
• How can breakpoint configuration in _settings.scss be synchronized across both grid paradigms without duplicating variable overrides?
• What is the minimum team-wide Sass proficiency required to maintain either approach as the project scales?