Manage Content

Manage Content

Use this guide when your team needs to update website content regularly without damaging structure, consistency, or shared assets.

The Main Rule

Update content in the place that actually owns it.

Most content problems in growing sites come from editing repeated content in the wrong place or duplicating shared content instead of reusing it properly.

Content Ownership Model

  • update local page content in Pages
  • reuse shared snippets through Variables
  • update reusable sections through Components
  • use Lists for growing content collections
  • review Users when ownership changes between people or teams
  1. Identify whether the change is local or shared
  2. Update the correct FaceFlow object
  3. Preview all affected pages if the content is shared
  4. Check linked CTAs, proof, and supporting copy
  5. Publish only after the impact is clear

When Content Should Be Shared

Share the content when:

  • the same message appears in many places
  • the same section is reused across several pages
  • a page family should stay aligned
  • several editors should not have to update the same thing manually

Keep the content local when:

  • it belongs to one specific page
  • the message is unique to one offer or campaign
  • reusing it would create confusion

Best Practices

  • avoid duplicate copy across many pages
  • update shared assets in the right place
  • keep section ownership clear between teams
  • review live pages after major shared changes
  • use Lists when content is expected to keep growing

Common Mistakes

  • editing repeated content manually in many places
  • changing a shared Component without checking impact
  • storing list-style content in static page sections
  • using one page to hold content that should become reusable
  • forgetting to confirm ownership after team changes

Final Check Before Publishing Changes

  • Did you edit the correct object?
  • Is the change local or shared?
  • If shared, which pages are affected?
  • Has the content been previewed where it appears?
  • Does the update still support the intended page goals?