GRN Urban
An independent, bilingual guide to Granada, evolved from its 2025 beginnings into a static Astro product for events, routes, researched guides and practical trip planning.
Studio product PRODUCT 2025
Context
GRN URBAN began in 2025 as an independent FRN.Q guide to Granada. By 2026 it had grown into a maintained editorial product: the original city-guide idea now connects cultural events, walks, researched guides and a trip planner in Spanish and English. The year in this case marks that origin, not a claim that the current system or stack dates from 2025.
- GRN Urban
- Culture & tourism
- Product
- Studio product
- Live
- 2025
Problem & objective
Useful city information is scattered across event calendars, venue pages, tourism sources and editorial articles. These sources change at different speeds and often provide uneven detail or conflicting records. Visitors need one dependable route from discovery to practical planning; the product also needs a way to keep dated information accurate without making every content page depend on a live API.
- Spanish and English routes and content must stay aligned without relying on Astro's built-in locale routing
- Event data comes from external sources with different formats, reliability and update schedules
- Time-sensitive pages need editorial review, safe fallbacks and deliberate indexation as events pass
- Content pages should remain usable and indexable without client-side rendering
Turn a city guide into a maintainable product: publish useful content quickly as static pages, make source changes and editorial decisions traceable, and reserve client-side behaviour for tasks such as building an itinerary.
(03) Plates
Solution & decisions
A static-first Astro product organised around Events, Routes, Guides and Planifica. A local publishing pipeline gathers and resolves event data before the build; editorial tools add factual depth and preserve reviewed copy. The resulting pages ship as static HTML, while small vanilla TypeScript interactions handle filtering, sharing and itinerary planning.
Architecture
Astro's static output is the default: pages are assembled at build time from local TypeScript data and generated event records, then published as HTML. A separate Bun/TypeScript pipeline queries source adapters, stores snapshots, normalises and deduplicates records, applies editorial decisions and writes the publishable dataset; the site build does not fetch event sources. Spanish is the unprefixed default and English has its own /en/ route tree, joined by typed translation helpers rather than automatic locale routing. The planner and discovery filters add focused browser-side behaviour without turning the guide into a client-rendered app.
Design
The visual direction draws on print cartography and editorial design. Vertical 'GRANADA' lettering, coordinates and section labels frame the guide as a city volume. Editorial hierarchy and real photographs establish place and context; filters, route durations, clear price states and a shareable planner help people move from browsing to a usable plan. Responsive layouts keep that experience coherent across mobile, tablet and desktop.
-
Static-first architecture
Content pages are generated statically with considered imagery, and richer interaction is isolated in the itinerary planner.
-
Editorial and cartographic identity
Vertical type, coordinate references and section labels frame the guide as a contemporary city volume rather than a listings app.
-
Four-pillar structure
Events, Routes, Guides and Planifica organise the product and cross-link instead of living as isolated sections.
-
Build from snapshots, not live APIs
Fetching and publishing are separate from the Astro build. A failed upstream request can be investigated without making a deployment depend on external availability or silently replacing a good local snapshot.
-
Preserve editorial judgement
Generated event copy is deterministic and constrained to source facts; handcrafted and researched overrides take precedence. Automation supplies consistent factual structure, not invented reporting or AI-authored claims.
-
Treat SEO as page lifecycle
Structured data, indexation rules, aliases and retirement behaviour are tested alongside metadata, so a past event is not kept indexable merely because its page once existed.
-
Design for the operating cost
For an editorial product, keeping information trustworthy is ongoing work. Investing in visible source health, reviewable exceptions and repeatable publishing reduces dependence on ad hoc fixes and makes maintenance part of the product, not an afterthought.
-
Client-rendered single-page app
A single-page app could power the itinerary tool, but it would make the whole guide depend on client JavaScript. Static generation keeps editorial pages directly renderable and indexable while allowing focused planner and filter interactions.
-
One live source of truth for events
Depending on one provider would simplify ingestion but leave the agenda exposed to gaps, format changes and outages. Independent adapters and local snapshots make source health visible and allow editorial resolution before publication.
The current codebase uses Astro 7 static output, strict TypeScript, Tailwind CSS 3, Bun scripts and Sharp for image processing. It has no GSAP dependency: interactions and motion use vanilla TypeScript and CSS. Event adapters collect source data into durable snapshots; a resolver applies identity and field-level decisions, and a deterministic editorial generator derives descriptions and practical highlights only from available record facts. Handwritten, researched and refined copy is kept separate and protected from regeneration. Technical SEO includes canonical and hreflang metadata, sitemap and robots controls, lifecycle-aware redirects and indexation, plus Schema.org JSON-LD for events, trips, articles, breadcrumbs, the organisation and the planner. The publishing flow validates local data and images, regenerates aliases, runs TypeScript and automated tests, checks Astro and audits generated HTML, sitemap, metadata, structured data, internal links and deployment headers. Ongoing maintenance includes reviewing failed or stale sources, resolving exceptions, refreshing dated content, checking redirects and indexation, and updating owned-photo variants.
Implemented scope
- Spanish and English static pages and route structure
- Multi-source event ingestion, snapshots, resolution and local publication
- Editorial event descriptions, researched overrides and review queue
- Event and route discovery, filters and time-based walking itineraries
- Long-form guides with cross-links to relevant events and routes
- Client-side itinerary planning and sharing
- Technical SEO, structured data and lifecycle controls
- Owned Granada photography with responsive image variants
Verification & outcomes
The 2025 city-guide concept has evolved into a maintained product whose content can be published and checked without depending on live source APIs at build time. Search Console provides a bounded, page-level signal: its Web performance export for 28 May–28 August 2026 recorded 3,302 impressions and 59 clicks for the Spanish Granada Sound guide, and 61 impressions and 3 clicks for its English counterpart. These are GSC impressions and clicks for those two URLs, not site-wide visits, users or sessions. No comparable GA4 users/sessions export or verified commercial outcome is included, so neither is claimed.
- The live product is linked at https://granadaurban.com/
- Events, routes, guides and Planifica have public Spanish and English routes
- The published guide includes event filters, route and guide pages, and a shareable itinerary planner
- 3,302
- 59
- 61
- 3
- Astro 7
- TypeScript
- Tailwind CSS 3
- Bun
- Sharp