Tulio Solorzano — About
About This Blog
This is my personal blog about growing vegetables in my home garden during the summer — a practical record of what I grow, how I care for plants, and the seasonal recipes that follow.
It's written for fellow gardeners and curious readers: clear, down-to-earth notes about plants, pests, and harvesting.
It's also a living portfolio: I used this project to upgrade my web development skills, applying modern Next.js patterns, localization, performance tuning, and resilient media handling.
The recent upgrade leaned on programmatic helpers and AI-assisted automation for repetitive migration tasks — a pragmatic, agentic approach that sped the migration while keeping me in control.
For hiring managers: this site demonstrates production-grade decisions around performance, accessibility, i18n, and automated tooling — showing both technical leadership and hands-on execution.
Features That Drive This Project
This site is driven by practical features: a content-first authoring workflow, robust localization, fast page performance, and resilient media handling (Supabase storage + CDN-friendly images).
Search and discoverability are core — the header search, category navigation, and structured post metadata make content easy to find.
Developer ergonomics and reproducibility matter: the codebase includes migration and utility scripts, declarative routing, and server components to keep server/edge behavior predictable.
The migration itself leaned on automation and programmatic tooling (scripted migrations, small codemods, and repeatable scripts) — in other words, an agentic development approach where scripted/automated helpers reduced manual steps and ensured consistency.
Operational concerns — simple deploys, fewer moving parts, and clear upgrade paths — also shaped architecture choices when moving to Supabase and the latest Next.js patterns.
Project Migration & What Stands Out
This project was migrated from an earlier stack based on Next.js 13 and Directus running on Railway to a modern stack using the latest Next.js and Supabase.
Why I migrated: Directus/Railway served well initially, but moving to Supabase simplified hosting, storage, and realtime features while keeping serverless deployment straightforward.
What stands out: the site now benefits from Supabase's built-in Postgres, edge-friendly APIs, and storage for images — improving performance and maintainability.
The frontend was upgraded to the latest Next.js app-router patterns, embracing server components, streaming, and simplified routing for a more resilient, SEO-friendly site.
Practically, this migration reduced operational complexity (fewer moving parts), improved local development parity, and unlocked better integration for content, auth, and media storage.
Current Stack (What This Project Uses Today)
Framework: Next.js (app router, server components, SEO-first metadata).
Data & auth: Supabase (Postgres, auth, admin workflows, and data helpers).
Media: S3 + CloudFront for garden_images, with signed CloudFront access via OAC.
Performance: image optimization disabled for upstream reliability; CDN delivery handles caching.
i18n: language-aware routing with JSON dictionaries and dynamic locale loading.