Block-theme design can come from theme files and from customisations saved through the Site Editor. Knowing which layer supplies a value explains why a file update may not appear publicly or why a reset changes the design unexpectedly.
IN THIS ARTICLE
01 Identify the two sources
The theme supplies default templates, parts and settings, including values described through its theme configuration. Site Editor changes can create saved overrides for templates and styles. Local block settings can add another more specific choice on an individual page or component.
This allows a site owner to customise a theme without directly editing its files, but it also means a developer cannot assume that changing a file will replace every saved customisation.
Why does a theme-file change not appear on the website?
- Identify the affected page and whether the issue is content, template structure, global styling or a local block setting.
- Inspect the selected template and any saved customisation indicator in the Site Editor.
- Review global Styles and the affected block's local settings.
- Compare with the relevant theme defaults in a safe development environment.
- Change or reset only the layer responsible, preserving useful overrides before removing them.
02 Coordinate developer and editor work
Agree whether the maintained design should live primarily in versioned theme files or in approved Site Editor customisations. Export and document changes when handing them between teams. Direct edits to a parent theme can be overwritten by theme updates, so use an appropriate development workflow for code changes.
Do not use repeated CSS overrides to mask a misunderstood template relationship. A structural problem, such as a missing Content block, requires a structural correction.
03 Verify after an update or reset
Check representative templates, mobile layouts and interactive elements. A reset may expose newer defaults from the currently installed theme, while a file update may leave an older saved template override active.
If staging and production differ, compare both theme files and database-stored customisations rather than only the theme version number. Keep caches out of the comparison by verifying the saved state first and purging relevant layers afterward. A clear source of truth makes future updates safer and reduces the risk of one team unintentionally undoing another team's design work.