Commerce · Component · destination-knowledge-story-models
Evidence-based destination storytelling
What it does
Turn imported city claims and hotel facts into localized country/city/theme/collection pages and experience read models.
Core pattern
Accepted facts to themed pages + localized content models
- Input
- Accepted knowledge claims and hotel inventory
- Output
- Story models, cultural landing pages and sitemap candidates
Key parameters
| Name | Type | Default | Values |
|---|---|---|---|
| locale | — | — | — |
| city_country_theme | — | — | — |
| source_claims | — | — | — |
| publication_status | — | — | — |
Maturity and limits
Story and public sitemap tests; provenance-aware contracts. Static source inspection only; no runtime, provider, deployment or test-pass claim.
Private baseline without a root license; verify reuse rights. Provider credentials, customer data, supplier terms and explicit execution gates require preservation.
Used in pipelines
Not part of a pipeline yet; available as a standalone component.
Industry tags
- Travel & hotelsSource-supported industry
For work involving destinations, room rates and bookings, use accepted facts to themed pages followed by localized content models.
- Government & public servicesTransferable use
For reviewing and publishing service guides and public explanations, use accepted facts to themed pages followed by localized content models.
Skills pack
Contract scaffold and deterministic mock
Download · 10KBSHA-256 ef04057df0980f89b0af808764722980896d178afe6743536d0c46176f8989f3
Related components
-
AI travel copy editing and SEO analysis
Draft language quality checks + search copy suggestions
Working not yet in a pipeline -
Bilingual enterprise product-site shell
Bilingual content and navigation composition + page rendering
Working 1 pipeline -
Structured case-study publishing
Structured case content + reusable detail pages
Working not yet in a pipeline