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. 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); Mobile: editorial panels omitted.

§2 — Core Event Info Block. Two-column CSS grid: left content area (fluid) + action sidebar (right, 280px fixed). The left area contains two rows: (1) image + event details side by side (flex), and (2) the truncated description text below. The description sits to the right of the sidebar — not under it — keeping it visually connected to the event identity.

Event image: Displays the event's featured image from WordPress. If no image is available, a standard placeholder graphic is shown (styled via the .placeholder class). No complex fallback chain — just image or placeholder.

Primary column: Category tag (links back to filtered calendar), H1 event name, date/time row (with calendar icon), venue row (links to business profile when available — a high-value cross-link), and contextual badges. Badges are drawn from WordPress post metadata: Free, Tonight, Sold Out, Recurring, age restrictions, indoor/outdoor.

Action card (sidebar): Price (or "Free"), primary CTA (Get Tickets / RSVP / Visit Website — varies by post data), Save Event (stores to browser/session — no account required), quick-reference details, share buttons. The "Source" field is a transparency marker — tells users where the data originated (e.g., "WordPress · via Eventbrite import"). This builds trust since much of the data may be auto-ingested from external sources.

Content handling: (1) Text is clamped to ~3 lines by default with "Read More" toggle. (2) HTML from external sources is sanitized but basic formatting preserved. (3) If no description exists, this area is hidden — don't show empty space. (4) Very short descriptions (under 20 characters) should also be hidden — these are often junk data like "TBD" or "Click for details."

★ WordPress data quality considerations: Not all events will have pricing, door times, or age restrictions. Each field must degrade gracefully — if price is missing, show "See Details" instead of $0. If no ticket link exists, the primary CTA becomes "Visit Website" or "Learn More" linking to the organizer's page. Venue link is only active if the venue has a business profile in the CMS — otherwise, display as plain text with address only.

§4 — Venue Card. Compact venue reference with embedded map thumbnail and address. "View Venue Profile" links to the business profile page (when the venue is in SNA directory — this is a high-value internal link). "Get Directions" opens native maps app on mobile / Google Maps on desktop.

WordPress data considerations: Venue name and address are the most reliably available fields in event posts. Map embed uses the address to generate a static map thumbnail (Google Static Maps API or similar). If the venue is not a recognized SNA member, the "View Venue Profile" link is omitted — only the address and directions link remain. Some event posts may list "Short North" or "TBD" as venue — in those cases, show the Short North district map instead of a venue-specific pin.

★ The venue card should be suppressed entirely for virtual/online events.

§5 — Similar Events. Auto-populated from WordPress using the current event's primary category as the filter. Shows up to 3 upcoming events in the same category, sorted by date (nearest first). H2 updates dynamically based on the event's category: "More Live Music + Performing Arts", "More Food + Drink Events", etc.

Image handling: Card 3 demonstrates the no-image fallback — a standard placeholder graphic replaces the event photo. The card remains fully functional without an image.

Fallback logic: If fewer than 3 events exist in the same category, backfill with events from related categories (e.g., if "Live Music" has only 1 upcoming event, pull from "Visual Arts" or "Performing Arts" to fill the row). If no upcoming events exist at all, hide this section entirely rather than showing an empty grid.

★ Exclude the current event from results. Exclude past events. Exclude events more than 30 days out (to keep recommendations timely). ★ A "See All [Category] Events" link could follow this grid, linking to the full calendar filtered by category.

§6 — Contextual Cross-Links: "Make a Night of It." Category-dependent recommendations that frame the event as part of a larger district visit. The section title and cards change based on the event's WordPress category:

Rules by event category:
• Live Music / Performing Arts → "Dinner Before" + "After the Show" (bars/nightlife)
• Visual Arts / Gallery Hop → "Eat + Drink" + "Explore Art + Culture"
• Food + Drink events → "More to Explore" + "Drinks After"
• Markets / Shopping events → "Browse Nearby Shops" + "Coffee + Lunch"
• Community / Family events → "Family-Friendly Dining" + "Things to Do Nearby"

This is the trip-planning section — framing the event as the anchor for a broader visit. Similar to the "While You're in the Short North" section on business profile pages, but action-oriented rather than editorial. Links go to directory/landing pages, not individual businesses (keeping it maintainable without curation).

§7 — Plan Your Visit. Reuses the same "Getting Here" pattern from the business profile page — compact, practical, addresses the documented friction point where suburban and out-of-town visitors express hesitation around parking and navigation. Meeting them on the event detail page is more effective than expecting them to find the Parking section independently.

Nearest parking, transit stop, rideshare drop-off, and bike share station. If the venue has a known address, parking proximity can be calculated. Otherwise, defaults to district-level information (the general Short North parking resources).

★ This is a shared component — same data structure as the business profile "Getting Here" module. Should be componentized in the CMS/template system to avoid duplication. ★ For large events (Gallery Hop, special events with 1000+ expected), consider a contextual override that shows special parking/transit information (e.g., "Street parking suspended — use garages on Vine St").