Navigation: 3 mega menus (Events, Eat & Drink, Explore) with 2/3 link pane + 1/3 editorial spotlight panel. 2 simple dropdowns (Parking & Safety, About) with icon + label + description per row. Donate CTA styled as distinct button. Per SNA_Navigation_Strategy_OSA: mega menus trigger on hover (200ms open / 300ms close delay in production); editorial panels are CMS-managed single post references with fallback defaults; Explore groups subpages by section (Art & Culture, Shopping, Experiences, Stay); Shopping nav shows only Fashion, Gifts, and All Shopping (analytics-informed — other categories accessible via landing page); Events editorial panel uses NAVY background; Eat & Drink and Explore editorial panels use white background. Mobile: all menus convert to accordion drawers, editorial panels omitted.

§1 — Confidence Statement. Replaces the aspirational editorial hero used on every other landing page. This is not a standard hero with a full-bleed photograph — it's a split treatment: stat block left, map illustration or utility image right. 'Getting Here Is the Easy Part' — the most confident framing, implies everything after arrival is worth it. Alternative: 'We've Thought of This' (warmest, most hospitality-oriented). Tone: Informational. The knowledgeable local friend, not the tourism board. Lead with the positive fact, not the procedure. Never use language that amplifies concern — avoid 'safe to visit,' 'don't worry,' 'despite what you may have heard.' Simply state the positive fact. Safety and parking statements carry equal visual weight. ★ Stat accuracy: verify 8,900+ figure is current before publishing. Confirm 'Every evening' Ambassador coverage against current deployment schedule. Confirm 'Free Sundays' against any policy changes.

§2 — Quick Answers Band. The highest-ROI section on this page. Four common visitor questions answered inline — no click, no accordion, no subpage navigation required. Serves the largest volume of users with the least friction. 4-up horizontal row on desktop; 2×2 grid on tablet; single-column stack on mobile. These four questions are a starting hypothesis based on the current site structure and user research for urban destination sites. Post-launch: check search queries bringing users here and on-site search terms to validate or replace. ★ Maintenance: parking rate figures ($1/hr, $2/hr) are the most operationally volatile content on this page — must be verified at minimum annually and immediately following any City of Columbus parking policy change. Assign a named owner.

§3 — ParkColumbus App Feature. A horizontal band treatment — not a full section. The single most useful tool for visitors managing parking. Positioned before the subpage cards: the planner (likely desktop, at home) sees this before navigating deeper. Include a rendered phone mockup or app store badge graphic if brand-approved assets are available from the City of Columbus or the ParkColumbus operator. Do not use the ParkColumbus logo unless SNA has confirmed permission. ★ Verify: app store links (iOS/Android) and any YouTube tutorial link from the current page must be confirmed as current before launch.

§4 — Subpage Navigation Cards. 3-up functional routing cards. Unlike other section landings, these cards lead with the functional outcome — what the user will find when they click — not an editorial tease. Card order: Parking Map (highest-priority destination) → Getting Here (non-drivers, transit users) → Safety Services (important but not the primary parking question). CTAs use functional verbs: 'Find Parking →', 'Plan Your Route →', 'Learn More →' — not 'Explore' or 'Discover' (those registers belong in the Explore section). Note: C-Pass (free COTA access for district workers/residents) is a subpage in this section but audience-specific — surfaced via the For Residents footer page, not on this landing page.

§5 — Ambassador Hotline Band. High-contrast (NAVY background, TEAL phone number) — visually distinct, cannot be missed. The phone number is large, clickable (tel: link), and the most visually prominent element. This information must never require a subpage click to find. The copy beneath the number makes the 911 vs. hotline distinction explicit — not a subtle distinction for users in a stressful moment. Secondary contacts in a compact row beneath: Non-Emergency Police, 311 City Services, SNA Admin Office. ★ Accuracy check: the current site shows hours as 'Sun–Weds, 7am–9pm / Thurs–Sun, 7am–11pm' — the Thursday–Sunday overlap is likely a typo. Wireframe uses 'Thu–Sat 7am–11pm' as a likely correction. Confirm exact schedule with SNA Safety Office before publishing. Verify all phone numbers are current.

§6 — Cross-Sell Strip. A minimal strip — not a full editorial cross-sell block. No images, no card tiles. One horizontal strip with two links. Primary: Events (knowing what's on this weekend helps plan arrival timing around peak parking). Secondary: Explore landing (for visitors who arrived at Parking & Safety before visiting the main site). Why a strip, not a block: (1) the user is in task-completion mode — a full editorial cross-sell is the wrong register; (2) the hotline band above already carries visual weight; (3) the most useful cross-sell (Events) can be communicated in one line. Tone: matter-of-fact, helpful, brief. The visitor is done with this section; the strip gives them a direction without overstaying its welcome.