One File the Owner Can Edit

Lesson 10 of 10 · Tourism Tech · built from Nora Travels, Nora Labs, Mahesh Travellers and my hospitality sites

After launch, the person editing a tourism site is usually the owner, not a developer. Give them one file with every fact they might change.

Example — the resort's company record

export interface CompanyInfo {
  name: string;
  tagline: string;
  whatsappNumber: string;          // used to build wa.me links
  whatsappNumberDisplay: string;   // how it's shown to guests
  phoneDisplay: string;
  email: string;
  address: string;
  social: { facebook: string; instagram: string; youtube: string };
  hours: { office: string; afterHours: string };
  logo: string;
}

• Two versions of the phone number — one for links, one for display — so formatting never breaks the link.
• Rooms, dining packages and event pricing live beside it as typed records, so there's no database to pay for.
• Types mean a missing field fails the build instead of showing undefined to a guest.

The same rule across my tourism and hospitality sites

Exercise

List every fact on a resort homepage that could change in a year. Which belong in CompanyInfo, and which need their own record type?

Keep going: ← Lesson 9 · See the live tourism sites →