Skip to main content
Landing pages live as data in Synscribe; to make them real pages, open the landing-page pillar, set up the export, and map it onto your site. Export JSON for a code-based frontend (e.g. Next.js) or CSV for a CMS (Webflow / WordPress / Framer / Wisp.blog). Publish the spoke pages (/uses/<slug>) and top pages first, then make sure they’re in sitemap.xml and reachable from the homepage via the hub before you index them.

​
Choose the format

Your siteExport
Code-based frontend (e.g. a Next.js site)JSON
CMS (Webflow / WordPress / Framer / Wisp.blog)CSV
❓ [needs Raymond] There’s no built-in “code/GitHub” publishing platform (the Platforms list is Webflow/WordPress/Framer/Wisp.blog), so code-based sites consume the JSON export directly. Confirm the canonical hand-off for code sites (repo import? build step?). See the gap register.

​
Steps

  1. In the landing-page pillar, set up the export (JSON or CSV per the table above).
  2. Export the pillar data.
  3. Set up the page template on your site to map to the data. Start with the /uses/<slug> spoke pages before the hub page.
  4. Publish the top pages first, then work through the rest.
  5. Make sure the pages are in sitemap.xml and reachable from the homepage via the hub (§1.8), then index them.

​
Small things worth knowing

On a landing page you can edit the slug directly (useful when slugs conflict; conflicts show a warning icon), set the category, and mark a page published or not, so you can export only the published ones. Related: 2.3.2 Generate landing pages · SOP: 3.1 Month-1 (Week 2)