PROJECT 03 — FULL STACK

TripCraft

A travel planning application — trips, destinations, itineraries, activities and budgets — with a proper React frontend backed by a Django API.

Mockup screenshot of the TripCraft trip timeline

OVERVIEW

TripCraft is a travel planning application built with a React frontend and a Django backend, rather than a static UI — the intent from the start was a real frontend talking to a real API and database, not a mockup of a travel app.

It's built around the parts of trip planning that actually take time: laying out destinations across days, keeping activities and notes attached to the right day, and tracking a budget alongside the plan.

THE IDEA

Trip planning tends to live across notes apps, spreadsheets and group chats. TripCraft keeps trips, destinations, itineraries, activities, dates, notes and budgets in one structured place, with the frontend and backend built and deployed separately.

FEATURES

→Trip creation with date ranges

→Destinations attached to a trip

→Day-by-day itinerary planning

→Activities and notes per day

→Budget tracking alongside the plan

→React frontend built with Vite, talking to a Django API

TECHNOLOGY

REACT VITE DJANGO POSTGRESQL SQLITE

ARCHITECTURE

The frontend is a React app built with Vite, calling a Django backend that exposes trips, destinations, itineraries and budgets as API resources rather than rendering everything server-side.

Keeping the frontend and backend as separate layers meant thinking through deployment for both — a production React build served alongside a Django API rather than one combined app.

CHALLENGES

Getting a separately built React frontend to call the correct Django API in production — rather than a localhost URL left over from development — is a detail that's easy to get wrong once the app leaves a local machine, and one this project deals with directly.

WHAT I LEARNED

Building a real frontend/backend split, instead of a Django-templates-only app, clarified how much deployment changes when there are two things to serve instead of one — and how much clearer the API boundary makes the rest of the code.

TripCraft's source is on GitHub, frontend and backend included.

VIEW ON GITHUB ↗