Theme Sync
Best for code, theme, template, and front-end presentation changes where live data must stay untouched.
Trust
Full Sync vs Theme Sync
These two modes exist so the release path matches the actual change risk. The rule is there to protect live data and keep the publish conversation honest.
The simple comparison
A side-by-side view is the fastest way to understand the difference.
| Mode | Best fit | What changes | Why it exists |
|---|---|---|---|
| Theme Sync | Code-led presentation and theme work | Theme or code assets only | Keeps protected live data out of risky sync paths |
| Full Sync | Validated flows that need broader sync behaviour | Broader site state with stricter controls | Used only when the site setup genuinely requires it |
What changes on live vs staging
The mode changes what WPFlow must consider before publish.
Full Sync
Only used when broader sync behaviour is required and validated against the site setup.
Why the rule exists
Without an explicit sync rule, release language gets dangerously vague.
- The wrong sync path can overwrite protected live state.
- A named release mode forces the publish conversation into the open.
- The client gets a clearer explanation of what publish actually means.
Related proof
The sample release shows how the mode appears inside public proof.
Next step
Need to know which mode your site would need?
Sign up with your site details and WPFlow will tell you what the safer path looks like.