Introduction

Two Taps is a franchise‑focused headless content and relationship platform. It lets central teams define reusable, nested content structures (“schemas”) once and safely roll them out across every brand, site and local page while preserving design standards and governance.

👋

These docs help external integrators, partner developers and technical stakeholders understand how to consume published content and interact with public endpoints.

What makes Two Taps different

Hierarchical model (Organisation → Brand → Site → Page) built for multi‑location & franchise scale.
Reusable schemas with controlled recursion (nested blocks up to 10 levels) enabling rich, composable layouts.
Granular permission engine that cascades administrative authority while preserving local autonomy.
Lightweight site utility packages (@twotaps/site-utils-*) for rapid React/Next.js (pages or app router) integration.
Visual Editor preview flow for safe draft iteration before publish.

Core concepts (high level)

Concept	Summary
Schema	A reusable content block definition (e.g. `HeroBlock`, `LocationDetails`).
Field	A typed property inside a schema (`text`, `image`, `schema` (nested), etc.).
Page revision	Snapshot of a page’s ordered schema blocks plus their field values.
Template	A reusable layout grouping schemas; pages reference a template revision.
Properties	Field values captured for a specific schema instance in a revision.
Permission hierarchy	Roles cascade down (org admin ⇒ site admin); viewer rights bubble up.

Dive deeper in the Schemas overview guide once you’ve skimmed this page.

How to use this documentation

Start here for context and terminology.
Read the Schemas overview for data flow and flattening logic.
Generate TypeScript types for your schemas using the Generating schema types guide.
Bootstrap a new site in minutes with the bootstrap:site CLI command.
Jump to integration sections for Next.js pages/app router usage.
Reference dynamic listing & filtering docs when building page directories.
Consult forms & submissions when embedding interaction surfaces.

🧭

Use the left navigation or the search bar to jump directly to topics (e.g. “publicPages”, “forms”, “resolveUrl”).

Audience

External site developers (custom frontends consuming Two Taps)
Partner agencies implementing franchise templates
Technical decision makers evaluating platform fit

Quick data flow snapshot

Next steps

Read the Schemas overview
Bootstrap a new site with the CLI in one command
Set environment variables in your public site (NEXT_PUBLIC_GRAPHQL_URL, NEXT_PUBLIC_HOST)
Implement a catch‑all route and call resolveUrl or resolveUrlCached

❓

Questions or feedback? Email support@twotaps.io.