Audit: align the test site schema with Tailored Travel

[deanleigh]

Why

The test site is the proving ground for the real Tailored Travel build. Every divergence between the two is somewhere a mapping feature can look correct locally and fail on the client site.

Features like #109 (map source file to a media picker), #34 (non-text destination fields) and #44 (typed destination mapping) all need realistic destination shapes to be tested honestly.

Audit result (completed 2 Aug 2026)

	Test site	Tailored Travel
Content types	65	119
Data types	60	90

Key alignment is excellent. All 61 shared content types have identical keys. The test site was built from Tailored Travel's uSync and keys were preserved. The Itinerary typo (#111) is the only divergence.

58 content types missing from the test site

Mostly feature* and layoutSettings* components:

• Rich text editors: Itinerary, Extras, More Features, Sights More, Accommodation More
• CTAs: Call Us, Contact Organiser, Tailor Your Tour
• Forms: Form, Pay Final Balance, Tailored Tour Login/Logout, Component Form
• Media: Image Rotator, Image Slideshow (component and feature variants)
• Navigation: Breadcrumb, Table of Contents, Back to Destinations, Internal Links, Pagination
• Settings components: border colour/width, items layout, level, sticky, hide/display
• Layout settings: 6 numbered variants plus area colour/border/sticky components
• Doc types: individualTour, individualTours, destinations
• Compositions: tourBrochure, tourDestinations, tourOrganisers

4 types exist only in the test site

• tourProperties — bundles Organisers. Live splits into tourOrganisers, tourBrochure, tourDestinations. This is the bundled-vs-granular divergence
• featureRichTextEditorItinery — the typo, see Rename featureRichTextEditorItinery to Itinerary (typo, diverges from Tailored Travel) #111
• featurePageOrganisers
• layoutSettings

8 shared types with differing property sets

Type	Difference
tourOrganiser	live has organiserMobile
featureComponentImage	property image locally vs featurePropertyFeatureImage live
featureSettingsComponentColorPicker	featureColour vs colour
featureSettingsComponentHideDisplay	live adds a display/hide group
featureSettingsComponentStickyNav	live adds display/position
layoutSettingsComponentColorPicker	test site has extra areas-colour properties
contentHeadingDefault1	live has redirects
siteSettings	live far richer: accreditations, company address, contact details

32 data types missing

Including Tour Properties - Brochure PDF - Media Picker (77cc8285-0c15-4bed-8b20-80cf93d84543), which blocks #109. Also Block Grid variants, list views, colour pickers, image croppers and several component-specific pickers.

Suggested order

1. Rename featureRichTextEditorItinery to Itinerary (typo, diverges from Tailored Travel) #111 — resolve the Itinerary typo (blocks everything else)
2. tourBrochure + its data type — unblocks Map the source file itself to a media picker field on the destination #109
3. Resolve tourProperties bundling vs live's granular split
4. Features and layout settings, grouped sensibly
5. individualTour / individualTours last, whole page types

Each becomes its own issue: one composition or type per branch, per uSync import, verified in the running site before the next.

Not in this issue

No uSync imports, no schema edits. Those follow as separate work.

[deanleigh]

@-

[deanleigh]

Premise weakened by the test site strategy decision (3 Aug 2026)

See planning/TEST_SITE_STRATEGY.md and #117.

This audit assumed the test site should converge on Tailored Travel's schema. That premise no longer holds in the same way: #117 brings in a full local copy of Tailored Travel as a second host site, so there is no longer a reason to reconstruct its schema piecemeal here.

What still stands:

• The audit itself is accurate and worth keeping as reference
• The method note matters: compare by key, never by alias
• Alignment is still worth doing where UpDoc actually maps, which is a small fraction of the 58 missing content types. Most are feature* and layoutSettings* components UpDoc will never touch

What is no longer wanted:

• Working through the 58 content types and 32 data types wholesale
• Treating full convergence as a goal

Leaving this open as a reference document rather than a work queue. The tourBrochure import from #116 already landed and still earns its place, since it unblocks #109.