"Can you make a quick brochure for the family?"
It always starts the same way. It never ends there. Two family trips, two "quick brochures," two full interactive planning apps nobody set out to build. Both are embedded live below — this is what a question and twenty-seven follow-up prompts turns into.
"Just something simple."
A hotel request becomes a nice little travel guide. It gets looked at for about 4.2 seconds. "Can we add pictures?" Reasonable.
The Feature Creep Fairy Arrives
Walking distances. Dollar signs. Kid friendliness. Parking. Wheelchair friendliness. Maps. Hotel amenities. Cruise schedules. Weather backups. It is no longer a brochure. It has become a field manual.
HTML Enters the Chat
PDFs start to feel like cave paintings. What if every button actually worked? Now it is an interactive travel planner instead of a document.
The Link Crisis
It gets sent proudly. A reply comes back: "Why am I looking at code?" Cue thirty minutes discovering that cloud drives think HTML files are plain text.
"Fine, we'll outsmart the internet."
PDFs. Word docs. HTML. Cloud drives. Email. Mobile browsers. Every sharing method known to mankind, tested one at a time.
Scope? Never Heard of Her.
The Tahoe guide quietly evolves into a 19-page travel magazine — hotel photos, room layouts, marina restaurants, dessert diplomacy, cruises, accessibility notes, parking, a suggested itinerary. At no point does anyone stop and ask: didn’t this start as dinner suggestions?
Ireland Raised the Stakes
By the time Ireland came up, there was no pretending anymore. No "brochure." Straight to: "Let's build a trip planning website."
Interactive cards. Expandable sections. Buttons. Activities. Maps. Links. The HTML practically packed its own suitcase.
Neither trip ever set out to become something huge. It starts with a perfectly normal question, then the "what if"s take over: What if we added pictures? Could we make the buttons work? Wait — one more thing. Suddenly it's not a document anymore. It's an experience.
Ireland Family Trip Builder
Hotel selection, tappable activity cards, a suggested itinerary that reshapes itself, and a live cost estimate — all in one self-contained HTML file with no backend at all.
Lake Tahoe Family Meetup Guide
The one that started as "dinner suggestions" — hotel comparisons, room layouts, marina restaurants, cruise options, accessibility notes, and a full suggested itinerary, all mobile-friendly.
Built collaboratively over dozens of prompts, mostly to solve the very unglamorous problem of getting one HTML file onto one phone. Personal details — names, dates, specific travelers — have been left out of this write-up and out of the planners themselves. What's left is the part worth keeping: two working examples of a "quick favor" turning into a real, working piece of software, one "what if" at a time.