# Trip-planner starter prompt

Adapted from this project; not yet tested end-to-end.

Copy the prompt below into your preferred coding assistant. Replace the example destination and traveler details with your own.

---

Build a mobile-friendly trip-planning website that serves as a practical reference before and during a trip. Use a Disney World trip as the initial example, with clearly fictional sample data. Ask me a few focused questions about the destination, dates, travelers, accessibility and height requirements, interests, pace, budget, and which features I want. Do not invent preferences or treat plans as completed experiences.

Start with two sample days. Give each day a concise card with transport, a short sequence of priorities, meal options, an optional break, and alternatives. Keep completed activities in a separate experience log or collapsed archive. Use neutral, factual reference-document language. Recommend only nonalcoholic drinks for this example. Clearly label sample schedules as illustrative rather than current operating information.

Make interactive maps the centerpiece. Provide a photographic map and a simplified illustrated map where appropriate, with aligned markers for attractions and food. Highlight the selected day's priorities and distinguish optional stops. Tapping a marker should show its name, a concise description, useful constraints, and an optional ride-through or preview link. Support touch screens, keyboard navigation, visible focus, Escape to close, and restoring focus when a map closes. Respect reduced-motion preferences. The demo’s bare map downloads are available at https://disney-2026-plans.pages.dev/#map-assets as JPG base maps and simplified SVGs, without the interactive waypoint overlay. For these maps, keep each SVG viewBox matched to the listed canvas dimensions so custom waypoints align with both styles. For other destinations, use map assets I supply or assets you are authorized to use.

Include a compact booking reference with unmistakably fake identifiers such as DEMO-HOTEL-0001 and DEMO-DINING-0002. For a public demo, use fictional bookings and traveler data throughout, including scripts, downloads, and hidden content.

Ask whether I want packing and to-do lists, an attraction completion checklist, pre-trip rankings, a movie watchlist, post-trip reviews, and a printable folio. Keep pre-trip preferences separate from experience reviews. Record completions only when explicitly confirmed. In the public demo, any editable lists should save only in the visitor's browser, explain that behavior, and offer a reset. If I request shared private lists, implement a separate authenticated service rather than connecting public visitors to private trip data.

Use a responsive layout with readable typography, clear day headings, useful color distinctions, and generous touch targets. Keep the main itinerary concise. Put supporting detail behind links or expandable sections. Provide a print layout if selected. Avoid requiring an account to explore the sample site.

Keep public sample content separate from private trip files. Build the public output into a dedicated directory with an explicit asset allowlist. Check that it contains no real booking identifiers, traveler names, private hostnames, private API calls, or unintended supporting files. Verify internal links, both map styles, marker selection, keyboard and mobile behavior, and persistence/reset for any selected interactive lists. Publish only that reviewed output using my chosen hosting provider.

Include a visible “Starter prompt” link to a readable, copyable prompt explaining the finished site's features and how to build a personalized version. Deliver the working site and briefly explain how to update sample days, map markers, and deployment.
