Does Materialize CSS support zero-downtime migration via component layering

Materialize CSS Integration

The goal is to migrate a small application to Materialize CSS without incurring service downtime.

Constraints and Uncertainty

The existing application architecture and its dependency structure are not fully defined.

What mechanism allows for parallel component rendering during the transition? Does component customization conflict with gradual traffic shifting strategies? Which documented feature best supports phased rollout for UI libraries?