Next.js, React and TypeScript
The responsive public experience, multilingual interface and dashboard prototype.
All work
Multilingual parish experience
All Souls
A public website and future publishing system shaped around welcome, history and everyday parish life.
Project status
Client website concept (private preview) · 2026 · Public site built; staff dashboard is a working prototype.
Project boundary. This is a client case study — not a claim of commissioned, built, tested, or approved work beyond what this page documents. The public site is built; the staff dashboard is a prototype that keeps sample data only in the browser.
My contribution
Research and information architecture, three-direction identity framework, responsive website, scroll-led opening experience and staff/community dashboard prototype.
01 / Design decisions
Start with the parish people need to understand.
The first phase organizes Mass information, parish history, sacraments and community resources around real visitor questions. A sourced nine-chapter history gives the story depth without inventing institutional facts.
02 / Design decisions
Create one identity with room for choice.
Three palette directions, independent type pairings and supplied church and Marian artwork form a client-facing branding system. The directions can be reviewed without changing the content structure underneath them.
03 / Design decisions
Welcome visitors in English, Italian and Spanish — with or without motion.
English, Italian and Spanish navigation, readable controls and a scroll-led church film make the opening experience feel ceremonial while leaving essential information available without motion.
04 / Design decisions
Prototype the work behind the public website.
The dashboard models drafting, review, archiving, events and room-overlap checks. Its sample data is stored only in the current browser; it is not authentication, a shared CMS or a live booking system.
05 / Design decisions
Hand off what is ready—and name what is not.
The editing map and readiness notes separate the working public routes from future services. Real staff accounts, shared publishing, email delivery, newsletters, payments and livestream connections still require parish-owned providers.
What came out of it
The outcome.
A responsive multilingual parish experience, a client-facing identity guide, a sourced history and an operational dashboard prototype with clearly documented boundaries.
What I would develop next
Next step: finalize photo and font licensing for public launch, then connect parish-owned authentication, content storage and delivery services before presenting the dashboard as operational.
Explore all 2 curated project assets
Additional views and the assets discussed above. Open images for their full composition; videos use native playback controls.
Tools with a purpose.
Content and research system
A sourced parish history, page architecture, editing map and readiness documentation.
HTML, CSS and browser storage
Scroll-led motion, accessible controls and clearly labelled same-browser dashboard behavior.
Where AI enters the process.
No AI tools were used on this project.