Cheche Za Nuru Foundation
A non-profit’s website goes out of date quickly when every update needs a developer.
The foundation’s website and the admin system behind it, which the team uses to publish its own stories and updates.
- CMS & Admin Dashboards
- Organisational Autonomy
- Impact Reporting
- Donations & Submissions
The problem
Cheche Za Nuru runs programmes for children in Kibera, Nairobi. Their work changes from month to month. An out-of-date website would undersell it to the very funders they depend on.
What I built
The team manages every section of the public site from a dashboard I built for them. They can publish a story or update their impact figures without asking me, which was rather the point.
What it does
- Stories with photo galleries.
- Editable programmes and impact figures.
- Team profiles.
- Donation and volunteer forms, with submissions collected in the admin.
- Email alerts whenever a new submission arrives.
Under the hood
- Next.js and TypeScript on Supabase.
- A small purpose-built admin, so the team only sees what they need.
Where it stands
The site is live and the team runs it day to day. They seldom need to call me, and I take that as the best review I could get.
Why it might matter to you
If your organisation needs a website it can keep current itself, this is the pattern I’d use.
Next Case Study
daftari
For many small businesses and households, the financial record is a WhatsApp chat full of forwarded M-PESA messages.