Back to Docs

How PageHub Works

Know exactly where to make changes and where to verify results so you can publish with confidence.

Quick links

FeaturesSchema Browser

Where you build vs what visitors see

This saves the most time when debugging.

  1. Build pages in `/build` (editor mode).
  2. Publish, then review the same page in `/static` (live visitor output).
  3. If it looks different, compare the same section across those two routes first.
  • Editor controls only exist in `/build`.
  • Published visitors only see `/static` output.

Where settings live

Change settings once in the right place instead of patching page by page.

  • Section/component styling is primarily controlled through node class settings.
  • Site-wide settings (theme, integrations, redirects) live under site settings.
  • If a setting is site-wide, change it once at the root instead of patching every section.
  • If a page behaves unexpectedly, check settings first before rebuilding blocks.

A simple debug flow

Run this sequence before you rebuild anything.

  1. Check the issue on `/static` first (real output).
  2. Open `/build` and confirm the same section + settings.
  3. Verify integrations/redirects/site settings if the issue is behavior-based.
  4. Re-publish and test again in a fresh browser tab.

Common examples

Use this to go from symptom to first fix quickly.

  • Layout looks off after publish -> compare the same block in `/build` and `/static`.
  • Tracking not firing -> check integration IDs in site settings first.
  • Wrong URL behavior -> check redirect rules before touching page content.
  • Theme inconsistency -> verify the active site theme at root settings.