un-hopital-autrement
I built a complete website and admin back-office for a French medical humanitarian association — designed so a two-person volunteer team can run everything without ever touching code. A promise kept since day one.
A medical humanitarian association needed to publish updates and collect donations regularly, without a tech team and without touching any code.
Next.js 16 front-end + TipTap rich-text admin: two volunteers publish articles and newsletters directly, with role isolation, drafts, and a publication workflow.
Shipped in 4 weeks, the team has been publishing autonomously since day one.
Un Hôpital Autrement
Association médicale humanitaire au service des plus pauvres au Congo Brazzaville
Avec 1 médecin pour 7 000 habitants, le Congo manque cruellement de soignants qualifiés. Ensemble, changeons cela.
Former, accompagner, autonomiser
Au Congo Brazzaville, un médecin pour sept mille habitants. La télémédecine nous permet de briser cet isolement : des cardiologues français accompagnent en direct les soignants congolais, jour après jour, sur des cas réels.
L'objectif n'est pas de remplacer, mais de transmettre. Chaque échographie partagée, chaque diagnostic discuté construit peu à peu une équipe locale autonome, capable de continuer quand nous ne serons plus là.
Actualités
Écrivez-nous
Pour devenir bénévole, proposer un partenariat, ou simplement en savoir plus sur notre action au Congo Brazzaville.
Un Hôpital Autrement
Medical humanitarian association serving the poorest in Congo Brazzaville.
With 1 doctor per 7,000 inhabitants, Congo is in critical need of qualified caregivers.
A site that works, not a brochure
When the association came to me, they didn't need one more brochure. They wanted a news blog to tell the project's story, a monthly newsletter for the community, a contact form that lands in a real inbox. And above all: the ability to publish an article on a Sunday evening, from a couch, without calling me.
Public site + admin back-office
- Public pages — homepage, "Notre projet", news with dynamic per-article routes, contact form.
- Newsletter — public signup, admin compose & history, auto-generated monthly HTML template from published articles.
- Rich text editor — TipTap with images, bubble menu, formatting. The team writes the way they would in Notion.
- User management — Firebase auth, roles, protected admin routes.
- Inbox — contact form submissions land in Firestore and are read from the back-office with a read / unread state.
Next.js 16 App Router + Firebase
Clean App Router structure: src/app/ for public site + /admin, src/lib/ for the Firebase layer, src/components/ for UI. Firestore and Storage rules do the heavy lifting on security: public read on published articles, write restricted to authenticated admins.
Deploys on Vercel, separate Firebase project, secrets in environment variables; the public repo ships a .env.local.example and a .firebaserc.example as templates. In short: the kind of mission I love. The association imagined a tool they could drive without a developer — I coded it, put it online, then stepped out of the way. That, to me, is what success looks like: a client who no longer needs me day to day.