@sarimarcus/content-sites-tourism

The city-tourism vertical: city-entity components (monuments, restaurants, hotels, events…), trip-planner pieces, tourism page templates and their utilities. Used by the Córdoba and Granada sites.

Named entry points: cards, sections, templates, schema and types (src/internal is never exported). schema holds the city-entity JSON-LD builders (monument, museum, restaurant, bar, dish, neighborhood, guide item list) on core schema, and the TourismCity address policy they share. Page templates are rendered by thin route files in each site: NeighborhoodFacetPage, ProximityFacetPage, TierFacetPage and CategoryFacetPage. The route keeps the filtering, URLs, the MIN_INDEXABLE_ITEMS noindex threshold, Layout and schema; the template gets props (copy, FacetNav chips, tone) and slots (breadcrumb, cards, empty, footer). sections also holds TourismNavigation, the tourism header (Explore, Articles, Eat & Drink, Plan with a month strip, Itineraries, Events and the mobile accordion) on the ui navigation shells. The site's Navigation.astro passes every link, label and count as props (TourismNavigationProps) and its logo through the logo slot, so the hrefs stay in the site where the link gate reads them.

Depends on @sarimarcus/content-sites-core and @sarimarcus/content-sites-ui (exact lockstep peers). Nothing may depend on it. Sites import @sarimarcus/content-sites-tourism/tailwind.css the same way as ui's.