Overview
A century-old institution brought online
The Hellenic Community of Monaco is one of the Principality's most established cultural institutions, representing the Greek diaspora in one of Europe's most prestigious jurisdictions. Despite its long history and active membership, the organisation had no cohesive digital presence — events were communicated informally, institutional history was inaccessible, and there was no channel to engage the broader Greek community in Monaco.
The brief was clear: build a dignified, bilingual (Greek and French) digital home that reflects the institution's heritage while serving the practical needs of its members and the wider Monégasque society — event listings, community services, historical archive access, and a clear contact pathway.
I led the full engagement — from discovery and content architecture through to design, development, and launch — operating as both Technical Director and delivery partner.
Technology
Built to last on shared infrastructure
The organisation operates on a lean budget, so every technology decision prioritised longevity, ease of maintenance, and independence from expensive SaaS platforms. The stack was chosen to be fully self-hosted, editable by non-technical administrators, and performant without a CDN.
Outcomes
From invisible to institutional
The platform gave the Hellenic Community a dignified, maintainable digital presence that now serves as the primary touchpoint for the Monaco Greek community.
Approach
Dignity over complexity
The biggest challenge was not technical — it was editorial and cultural. A cultural institution's website must feel authoritative without feeling cold, and welcoming without feeling trivial. I worked closely with the community's board to shape the content architecture, ensuring that history, events, services, and membership were all surfaced clearly without competing for attention.
The admin interface was designed with non-technical users in mind: simple, bilingual forms for publishing events and news, with no HTML editing required. The goal was zero ongoing maintenance burden for the Technical Director role — the community needed to own it fully.
Bilinguality was built in from day one at the data layer, not added as an afterthought. Every content type stores Greek and French variants separately, and the language toggle is persistent across sessions via localStorage.