From Zero Visibility to a Trusted Digital Home

Frontend Development: A Collaborative Build

I worked alongside another frontend contributor rather than presenting the website as a solo engineering project. The shared implementation used Next.js, React, TypeScript, and Tailwind CSS to create the public-facing experience across the homepage, About, programmes, Get Involved, stories, and contact journeys.

My verified contributions included content and interface updates across core pages, responsive navigation and footer improvements, reusable form behaviour, FAQ and legal pages, blog and patient-story content, image handling, and numerous usability fixes through launch and continued iteration.

Forms, Donations, and Production Hardening

I built and refined the contact, volunteer, newsletter, and donation experiences, including inline validation, input limits, draft persistence, disposable-email checks, secure verification, user feedback, and transactional response emails.

I also implemented the Paystack and Flutterwave payment flows, one-time and monthly donation handling, post-donation status screens, webhook verification, Cloudflare D1 records, Turnstile protection, request rate limiting, signed links, and donation confirmation emails. This work connected the frontend experience to secure production workflows instead of stopping at static page design.

Project Management — Running the Whole Build

My first job on this project was making sure it actually got done. That sounds obvious, but nonprofit digital projects have a well-documented habit of stalling — too many stakeholders, unclear ownership, and no one accountable for the timeline. I came in specifically to prevent that.

I managed the full project lifecycle from kickoff to handover. That meant defining the scope upfront so everyone agreed on what was in and what wasn't, breaking the work into clear phases with milestones the team could hit, coordinating between the designers and developers, and keeping MatataBrown's leadership informed without pulling them into decisions that weren't theirs to make. No missed milestones. No scope creep. Delivered on time.

Product Management — Defining What to Build and Why

Before any design or development happened, someone had to answer the harder questions: who actually uses this site, what do they need to be able to do, and in what order does any of that matter? That was my job.

I ran the product discovery work — mapping out every user type (donors, community members, partners, media), what each of them needed from the site, and where they were most likely to drop off if we got it wrong. That user map shaped every decision that followed: what pages we built, what content appeared where, how navigation was structured, and what the primary calls to action were. The product strategy was built before a single design file was opened.

The Homepage — Writing for Three Audiences at Once

The homepage had to do something genuinely difficult: speak clearly to three completely different people at the same time. A potential donor who needs to trust before they give. A community member who just needs to know help exists and where to find it. A potential partner who needs to see an organisation worth taking seriously.

I defined the information architecture and wrote all the copy with those three readers in mind simultaneously. Every headline, every paragraph, every CTA was tested against the same question: does this build trust, communicate purpose, and move the right person to act?

The About Section — Making the Story Do the Work

I wrote the full About section from scratch — the founding story, the mission, what preventable blindness actually looks like in Nigeria, the values behind the work, and the leadership profiles. This wasn't just background information. It was the section designed to turn a curious visitor into someone who actually cares.

Nonprofits often underestimate how much their story matters. Facts inform. Stories move people. I wrote this section to do the second thing.

The Programmes Section — Building the Evidence Base

Donors and partners need to see evidence that an organisation actually does what it says. I scoped and wrote the programmes section to serve that specific need — documenting every initiative MatataBrown runs with enough clarity and depth to answer the questions a serious supporter would ask.

I also structured it so that as MatataBrown's work expands, the section can grow with it. New programmes slot in without needing to redesign anything.

The Get Involved Section — Removing Every Barrier

Most nonprofit websites have a generic 'Contact Us' page and leave it at that. I pushed for something more intentional — separate, clearly-labelled pathways for each type of person who might want to get involved: donor, volunteer, corporate partner, community referral.

I wrote the copy for each pathway with one aim: get the right person to the right action with as little friction as possible. The worst outcome would be someone who wanted to help, landing on a page that made them feel unsure about what to do next.

The Blog — An SEO Asset, Not Just a News Feed

I made the case early on that the blog needed to be thought of as a long-term SEO investment, not just a place to post updates. Google rewards organisations that publish original, relevant content consistently — and for a nonprofit in the eye health space, the keyword opportunities are real.

I defined the content structure, wrote the launch content, and made sure the team had a publishing system they could use independently. The blog was custom built for MatataBrown specifically — not a generic CMS dropped in. The content foundation is there — it compounds in value every time they publish.

The Contact Page — Right Person, Right Message

I mapped out exactly who would land on the contact page and what each person needed to be able to do. Donor enquiry. Service referral. Partnership discussion. Media request. Each pathway got its own clearly-written copy and its own direction — so nothing got lost in a generic inbox.