Tour packages your clients can edit. Enquiries that know the trip.
A travel website is a page with many items for packages, detail URLs for each trip, and forms that tag the lead with that package. Your frontend owns the design; mywebcms owns the words, prices and itineraries.
List. One Tour packages page. Every tour is an item with the same fields — title, price, duration, destination — and its own slug.
Without a packages model
Ten trips, ten piles of content.
Hard-coded package pages, prices in a sheet that never matches the site, and enquiry forms that forget which trip someone opened.
Copy-paste per package
Details rewritten by hand on every package page. One update means a deploy — or many manual edits.GoaKeralaManaliNo shared schema
Each package page drifts: different field names, missing media, filters the list page can't use.InconsistentLeads without a tour
Contact forms dump into one inbox. Nobody knows which package to follow up on.Which trip?Booking tool bolted on
A third-party form or sheet for enquiries while the CMS holds yesterday's prices. Two sources of truth.Two tools
One schema for every package
A page with many items — each item is a tour.
Create a Tour packages page once. Define fields (title, price, duration, destination, gallery). Every new trip is an item with its own slug, not a new site or a duplicated page.See how pages with many items work
Same fields everywhere
Title, price, duration, destination, featured — optional fields cover differences. No per-package schema drift.pricedurationdestinationDirectory from the list API
GET the page slug for every visible package. Your cards read JSON — never hard-coded packages.GET /v1/pages/tour-packagesFilter and sort
Mark destination or featured as filters; sort by price. Configured on the schema — not custom code per site.destination=sort=priceAdd a package in admin
New tour = new item. Fill the fields, Release, and the list API includes it. No deploy for content.+ New item
A page for every package
Each trip gets its own address and sections.
The item template defines Hero, Itinerary, Gallery and Enquiry once. Every package fills its own values. Rename a slug and the old one stays as a redirect.See how Releases ship changes
Stable detail URLs
Your site routes /tour-packages/goa-beach-escape. The API is GET /v1/pages/tour-packages/goa-beach-escape with every field./tour-packages/<slug>Item sections
Hero, itinerary, gallery, FAQ — the same section kinds as any page, scoped to the item. Design stays in your frontend.HeroItineraryEnquiryForm on the package
A form section on the item template shows the same form on every package page, with the item recorded on the lead.form · itemSlugSlug redirects
Rename a package URL and the old slug answers with the new one. Bookmarks and ads don't break.Old → new
Leads that know the package
Every enquiry is tagged with its trip.
Forms on item pages send the item with the submission. Filter leads by package, assign an owner, and export without guessing which trip they meant.See how forms and leads work
- Neha S.Goa Beach EscapePackage enquiryNew
- Omar K.Kerala BackwatersPackage enquiryContacted
- Priya R.Manali Snow TrailCallbackNew
Item on the lead
pagePath and itemSlug travel in the form context. Admin shows which package the visitor was on.itemSlug: goa-beach-escapeFilter by package
Work one package's queue separately from another's. Same statuses and owners as any other lead.GoaKeralaOne inbox, many packages
Still one website's Forms & Leads — not a CRM per package. Access stays per module for the team.One websiteExport the filter
CSV of the current package filter or selection. WhatsApp and CRM delivery aren't built yet..csv
Who updates the prices
The travel team edits. Design stays locked.
Give an editor Content access — they change price and itinerary in Development. A Release (with approval if you want) puts it live. They never touch API keys or the frontend.See how team access works
Edit one package
Items check out independently. Updating Goa never locks Kerala.Per-item checkoutRelease to publish
Production stays read-only until someone merges. Same flow as any page — not an industry-only publish button.v3v4Access per module
Content Editor for packages; Leads Viewer for enquiries; Developer settings nowhere in sight.ContentLeadsSame platform, travel schema
Nothing is hardcoded for travel agencies. Hotels and clinics use the same building blocks with different fields.Configurable
FAQ
Questions about travel sites.
Packages as items, enquiries, booking tools, and multi-branch agencies.
Get started
Build your next client site on mywebcms.
Start from a screenshot, give your client one simple place to run it, and ship it on any stack you like.
- Two steps to your first website:
- 1Create your workspace
- 2Add a client website
Everything that comes with mywebcms
Tap any feature to learn more.