Skip to content
All work

Client work

Al-Birr

Website for a Mumbai community trust.

Year
2025
Role
Sole engineer
Type
Client work

What it is

Al-Birr is a socio-religious trust based in Mumbai with branches across several regions. The site carries their eight programme areas — lectures, publications, fieldwork, regional tours, women's education, village outreach, competitions and their YouTube channel — alongside downloadable literature and an online donation flow that accepts Zakat and Sadaqah as well as general giving.

By the numbers

8
Programme areas
1
Donation flow, three tender types

The brief, and who it is actually for

This was not an audience of developers. A large share of visitors arrive on mid-range Android phones over uneven mobile connections, many are not reading in their first language, and a meaningful number are older and not confident online. That set the constraints far more than any design preference did.

It also meant the usual portfolio instincts were wrong. Heavy motion, clever layouts and anything that delays first paint would actively cost this client donations. The job was clarity and speed, not expression.

What I built

The eight programmes are modelled as content rather than hardcoded pages, so the trust can add a programme or reorder them without a developer. Each one leads with a photograph and a plain description, because that is what tells a visitor whether this is the organisation they were looking for.

The donation path is deliberately short, and the page carries the reassurance signals that actually matter for charitable giving: secure-payment confirmation, tax-exemption status, and explicit handling of Zakat and Sadaqah as distinct categories rather than a single generic amount. Literature is offered as direct downloads, and scholar testimonials sit near the giving path rather than buried on an About page.

Designing for trust rather than polish

A donation page lives or dies on credibility. Someone deciding whether to give money to a religious trust is asking a very specific question — is this real, and will the money reach where it says. Every design decision on that page answers that question or it is noise.

So the endorsements, the registration and exemption details, and the named programmes are all load-bearing content, not decoration. The most effective thing I did on this project was resist making it look more impressive.

Decisions

Four calls I would make the same way again

  • 01

    Lead with proof, not with design

    Scholar endorsements, tax-exemption status and named programmes sit high on the page. For a giving audience these are the conversion levers, and burying them under a hero would have been a designer's decision rather than a useful one.

  • 02

    Zakat and Sadaqah as first-class categories

    These are religiously distinct obligations with different rules, not labels on the same donation. Treating them as separate options respects how the audience actually thinks about giving, and it is the detail that signals the site was built for them.

  • 03

    Programmes as content, not pages

    The trust adds and retires activities over time. Modelling them as data means that is an edit rather than a deployment, which matters when the client has no developer on hand.

  • 04

    Treat performance as accessibility

    On a low-end Android over a weak connection, every unnecessary kilobyte is a person who leaves before the page renders. For this audience, a fast site is not a technical achievement — it is whether they saw the content at all.

Stack

Application

  • Next.js
  • TypeScript
  • Tailwind CSS

Content

  • Programme model
  • Literature downloads
  • Testimonials

Delivery

  • Vercel
  • Image optimisation
  • Static rendering

Next case study

CipherWeb