Theme Sync
Best when live operational data stays authoritative and WPFlow releases scoped approved work through governed coverage.
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 | Best FitLive-data sites where operational records stay live-authoritative | What ChangesApproved code and selected governed content/configuration changes | Why It ExistsKeeps protected live data out of risky overwrite paths |
| Full Sync | Best FitBrochure, lead-generation, and non-live-data sites | What ChangesApproved presentation, content, and configuration changes | Why It ExistsLets staging be the authority while protected live operational data is preserved |
What Changes On Live Vs Staging
The mode changes what WPFlow must consider before publish.
Full Sync
Best when staging can be the authority for approved presentation, content, and configuration changes.
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.