AI Interfaces & Vibe Coding
Sherpa's Stories
Digital Tourism Think Tank
Six tools, grouped by how you use them.
Three are conversational tools your team likely already uses for writing and research. Three are purpose-built builders that deploy a working tool from a brief. The right choice depends on what you are making and where it needs to run. Links open in a new tab.
Builds React and HTML artefacts directly in the conversation. Strong on strategy and complex briefs. The best starting point for teams already using Claude for content and research.
The strategic Gemini interface, not the consumer chatbot. Gives access to system prompts and model configuration. The right choice for teams in the Google ecosystem.
OpenAI's coding agent, runs autonomously in a sandboxed environment, writes and tests code without step-by-step prompting. Suited to complex builds with a well-defined brief.
Full-stack app builder from a plain language brief. Generates a hosted URL immediately, no deployment step required. The fastest path from idea to something you can share.
Builds internal tools and dashboards from a brief. Strong for data-connected DMO tools, visitor dashboards, content calendars, reporting interfaces. Less suited to consumer-facing tools.
Builds agents that live inside Microsoft 365, Teams, SharePoint, Outlook. The right choice if your organisation runs on Microsoft. Most governed and enterprise-ready option.
Lovable or Claude · deploy via Netlify or Vercel
Base44 or Copilot Studio if on Microsoft 365
Google AI Studio · test the logic before building the UI
Watch the same brief built two ways.
Both facilitators are running the same destination brief simultaneously, one on Claude, one on Lovable and Base44. The brief is identical. The process, the speed and the output will differ. Follow along on this screen.
Choose a build. Run the prompt. See what comes back.
Each scenario includes a copy-paste brief pre-tagged for the most suitable tools. Pick the one most relevant to your destination and run it on your device now, or save all of them to try after the session.
Itinerary builder
A tool that generates personalised itineraries based on travel style, duration and season. The most commonly needed destination tool and the best first vibe coding project.
Event and seasonal guide
A searchable, filterable guide to events and seasonal highlights. Answers the most common visitor question, what is on when I am there, without requiring a CMS or database.
Accessible travel planner
A planning tool specifically for visitors with accessibility needs. Addresses one of the most underserved content gaps in destination marketing and one where AI can add genuine value over static pages.
Content brief generator
A tool for your content team that generates structured briefs from a destination, topic and audience. Encodes your brand guidelines and voice so every brief produced is on-brand without manual checking.
Partner intelligence dashboard
A dashboard that aggregates and summarises partner news, campaign activity and performance signals. Replaces manual monitoring and gives the team a weekly intelligence digest they can act on.
AI destination knowledge base
A Claude Project or Google AI Studio system prompt that encodes your destination's knowledge, voice, facts, experiences, FAQs, so any team member can generate on-brand content without a briefing document.
Every prompt works better when it carries your brand.
Every scenario above includes a placeholder for brand voice, colour or tone. This is not optional, it is what separates a generic AI output from something that sounds like your destination. Before you run any of these prompts for real, feed in two to three sentences of your actual voice and one or two specific destination facts. The difference in output quality is significant.
Getting it live is the easy part.
Once Claude, Google AI Studio or any other tool has produced your HTML or React output, you need somewhere to host it. All six options below are free to start and require no server management.
NetlifyRecommended
open_in_newnetlify.comDrag your HTML file onto the Netlify dashboard. Live URL in under 60 seconds. Custom domain available on the free tier. The fastest path from Claude export to a shareable link.
Vercel
open_in_newvercel.comClosest alternative to Netlify. Particularly well-suited for React outputs from Lovable. Connects to GitHub for automatic deploys on every code change.
Cloudflare Pages
open_in_newpages.cloudflare.comUnlimited requests on the free tier. Fast global CDN included. Good choice for tools expected to receive significant visitor traffic once live.
GitHub Pages
open_in_newpages.github.comFree hosting directly from a GitHub repository. Requires a GitHub account. Best for teams comfortable with version control or working with a developer on longer-term maintenance.
Render
open_in_newrender.comStrong free tier with automatic SSL. Better than Netlify for tools that need a backend, for example a trip planner that saves user preferences or connects to a data source.
Railway
open_in_newrailway.appMost capable free-tier option for full-stack applications. Good choice when the tool built with Codex or Base44 needs a persistent database or API connections.
Once it is live, connect it to your data.
Model Context Protocol lets your vibe-coded tools pull live data from external sources, your CMS, your events calendar, your partner directory. Instead of hardcoded content, the tool stays current automatically. GNTB is building MCP servers for exactly this reason. It is the difference between a static prototype and a real operational tool.
Pull live events, attraction listings and editorial content without manual updates
Surface live performance data inside your team dashboard without a developer
Real-time availability, pricing and reviews from accommodation and experience partners
This is powerful. It is also not magic.
Vibe coding opens real capability for destination teams who could not previously build tools independently. These five points are what keep the approach strategic rather than experimental.
What visitor problem does your destination have right now that a tool could solve?
Write one sentence. That sentence is your brief. Bring it to your team next week and run one of the scenarios from the previous slide against it.
The brief is the product.
A vague brief produces a generic tool. A brief carrying your voice, audience and purpose produces something that sounds like your team.
Brand guidelines are the system.
Build one brand prompt block with voice, palette and content rules. Reuse it across every project so AI cannot contradict your positioning.
A prototype is not a product.
A 30-minute build is a proof of concept. The gap to a maintained, accessible, GDPR-compliant tool is real. Plan for it.
It works inside an AI-first workflow.
Vibe coding needs a team already using AI daily for knowledge, briefing and review. Otherwise the tool you build will not be maintained.
Start with the problem, not the tool.
The right starting question is which visitor problem your destination has, not which tool is most exciting. The tool is downstream of the problem.