How to Customize a Template Safely
Rules for making visual changes without breaking theme, language, or framework behavior.
Visual freedom is useful only when the framework contract stays intact
Template customization should stay inside template directories and should not quietly alter framework rules. A visual redesign is fine. Hidden routing logic, theme priority hacks, or language-specific branching inside a template are not.
The safest workflow is to change only what the template actually owns: markup structure, presentational CSS, and template-local components. If a desired change affects persistence, route structure, or cross-template behavior, it probably belongs in the framework layer instead.
This distinction keeps templates expressive without making them unpredictable.