Turismo Urbano

The problem

A Tenerife real-estate agency needed a fast platform to list rental and sale properties, handle heavy galleries and publish from a simple back-office. The previous WordPress stack fell short: SEO constrained by rigid templates, slow gallery loading due to the absence of a media pipeline, and zero flexibility to evolve into advanced filters or third-party portal integrations.

The sales team publishes 20–30 properties a month and needed the site to withstand traffic spikes from local campaigns without collapsing.

Architecture decisions

I split the frontend and backend with clear responsibility boundaries:

• React 19 SPA + Laravel API: lightweight public frontend with server components only where SEO requires them. Backend with Sanctum auth for the agent back-office.
• Cloudinary for on-demand image transforms (WebP/AVIF thumbnails, smart crops). Removes image processing from our own server and scales without infrastructure work.
• PostgreSQL with a relational model properties ↔ location ↔ media, indexed by city, type and price range.
• Render ↔ GitHub CI/CD: every push to main deploys in minutes, with PR preview environments for QA before prod.

I discarded Next.js alone because the administrative team already knew Laravel (one of the technical partners was a PHP developer) and because Laravel Filament gave a professional back-office in days, not weeks.

What I did

• Data modeling with owner-property-media relations
• REST API with public endpoints and protected admin endpoints
• React 19 SPA with router, advanced filters and optimized galleries
• Cloudinary integration with signed uploads from the frontend
• Deployment on Render with custom domains and automatic SSL
• Content migration from the previous site

Outcome

Under 1.5s initial load on 4G, a back-office non-technical users operate without friction, and a media pipeline that scales hands-off. The agency publishes new properties in minutes, with gallery previews before going live.