Case Study · Laravel · Content Platform

CollectorWWII

A Laravel-based content platform designed to manage and present a structured WWII collection, combining data modelling, media handling, and advanced filtering into a usable system.

Visit live site Back to projects

collectorwwii.eu/books

Laravel

Application framework

CRUD

Books and items management

Filtering

Content browsing and discovery

Production

Live deployment with Nginx and Cloudflare

Context

The problem

Managing a growing collection of WWII books and items through static pages or loosely organised content quickly becomes difficult. The project needed a system that could organise entries consistently, support media-rich records, and make discovery easier for visitors.

Role

My contribution

I worked on the application structure, backend logic, filtering, admin workflows, media handling, deployment, and production hardening. The focus was not only on getting content online, but on building something maintainable and usable over time.

Implementation

What I built

Structured CRUD flows for books and collection items in the admin area.
Dynamic filtering for categories, nationality, origin, and organisation.
Media handling for images and documents, including main-image selection logic.
Frontend browsing patterns focused on content clarity and usability.
Laravel deployment on a Hetzner VPS with Nginx, PHP-FPM, MySQL, Redis, SSL, backups, and Cloudflare.

Challenges

What had to be solved

Balancing flexible data structure with simple admin usability.
Handling media consistently across different content types.
Keeping filtering performant while scaling content.

Laravel PHP MySQL Tailwind Vite Cloudflare Nginx

Technical focus

Why this project matters

This project represents my current direction best: moving from classic PHP and operational support work toward structured Laravel development, cleaner architecture, and systems that solve a real content-management problem.

Learning

What it demonstrates

Backend thinking beyond single pages or isolated features.
Comfort with deployment, infrastructure, and production concerns.
Ability to design around maintainability, not only initial delivery.
Bridging practical user needs with a more modern application stack.