Garden Lodge
Back to Projects

Garden Lodge: Community Garden Content Platform

→ Introduction

Garden Lodge is a community garden initiative in Hamburg built around a simple operating principle: learn by doing, document the process, and leave the land better than it was found.

The project needed more than a basic online presence. It needed a digital product that could:

  • Explain the mission clearly to supporters, volunteers, and local community members.
  • Document real garden progress over time instead of relying on scattered updates.
  • Turn practical gardening knowledge into reusable learning content.
  • Support maintainers with a lightweight internal workflow for content and progress updates.

My role covered product strategy, UX direction, frontend development, and content system design. The result was a responsive Astro website that combines public storytelling, sprint-based progress documentation, a learning library with EN/ES/DE content, and a private admin studio connected to InsForge.

✕ Challenge

The main challenge was to make Garden Lodge feel credible, warm, and distinctive without turning it into a generic sustainability website.

On the product side:

  • Visitors needed to understand the garden's purpose quickly.
  • The project needed visible evidence of progress and real work.
  • Supporters needed simple ways to contribute advice, materials, or financial support.
  • The content model had to stay easy to expand as the garden evolved.

On the technical and operational side:

  • Progress had to be documented through sprints, backlog items, photos, goals, lessons, and next steps.
  • The Learn section needed structured educational entries available in English, Spanish, and German.
  • Public pages had to remain fast and static-friendly.
  • The private admin layer had to support updates without making the system too heavy for a small initiative.

This created the need for a product that balanced storytelling, content architecture, and operational clarity.

✓ Solution

I designed and built a content-driven platform around the garden's real working rhythm: set a goal, learn what is needed, apply it in the garden, and document what changed.

The solution is built around three core components:

🌱 Public Storytelling and Progress System

The public website explains what Garden Lodge is, why it exists, and how the work happens over time. It provides:

  • A crafted homepage with a stained-glass inspired visual direction.
  • Mission, vision, process, and support sections for clear first-time understanding.
  • A progress log that turns garden work into documented sprint entries with goals, learnings, actions, photos, and next steps.

📚 Structured Learn Section

The Learn section was designed as a practical knowledge library rather than a blog. It enables:

  • Structured entries for vegetables, tools, flowers, and garden fauna.
  • Educational content available in English, Spanish, and German within the Learn experience.
  • Category filters and reusable content fields so the library can grow without redesigning the site.

⚙️ Static-First Architecture with Admin Workflow

The technical implementation keeps the public experience fast while giving maintainers a way to manage content. This setup includes:

  • Astro, TypeScript, Tailwind CSS, and Zod for a typed, fast, content-driven frontend.
  • Markdown and JSON fallback data so the site can still build without backend credentials.
  • InsForge integration for epics, backlog items, admin auth, media storage, and content management workflows.

★ Business Results

Garden Lodge gained a professional digital presence that reflects how the initiative actually works: transparent, practical, and community-oriented.

Results for Visitors and Supporters

The site gives first-time visitors a clear path from understanding the project to following its progress.

  • Clear public narrative: Garden Lodge now has a focused identity and a credible explanation of its mission.
  • Visible proof of work: Sprint-based progress entries show real garden activity instead of vague updates.
  • Accessible learning content: The Learn section makes practical gardening knowledge reusable across English, Spanish, and German entries.

Results for Maintainers

The project also created a maintainable operating layer for future updates.

  • 3 documented garden sprint entries showing goals, research, applied work, and outcomes.
  • 29 active learning-library entries structured across vegetables, tools, flowers, and fauna.
  • Public pages plus a private admin workflow for managing epics, backlog items, learning cards, and media uploads.

The most important product outcome was that a small physical initiative became easier to understand, support, and document over time.

↻ Project Timeline

From initial concept to launch-ready implementation, the project moved through product definition, content architecture, design, development, and deployment preparation.

Phase 1 - Discovery

Defined the initiative's audience, mission, content needs, and need for public storytelling plus internal organization.

Phase 2 - Content Architecture

Structured progress entries, backlog data, sprint logic, and learning-library fields for long-term maintainability.

Phase 3 - Design and Build

Developed the Astro site, responsive layouts, stained-glass inspired visual system, reusable components, and Learn/Progress experiences.

Phase 4 - Launch Preparation

Connected InsForge workflows, validated fallback data, tested build behavior, and prepared the project for static deployment.

Ian Paniagua

Ready to transform your product?

Let's discuss how we can achieve similar results for your business. Contact me at paniagua.ian.de@gmail.com or book a call below.