WORK · CASE STUDY · NON-PROFIT

Ten years of WordPress, rebuilt to raise more

Sanity CMSNext.jsRaisely & StripeData migrationHosting & support

10+Years of WordPress retiredA decade of programme reporting moved into a structured headless model, migrated record by record.

36Countries of programme work to serveHelmets, education, infrastructure and policy, in several languages, under one content model.

OneCMS behind every page and languageThe communications team composes pages from blocks that already look right. No developer ticket.

Built with

Next.js
Sanity
Tailwind CSS
Vercel
Stripe
Figma

A charity's website is not a brochure. It is the collection tin

AIP Foundation has worked on road safety since 1999, running helmet, education and policy programmes across 36 countries from their base in Ho Chi Minh City. Road crashes are the leading killer of children and young people worldwide; the Foundation exists to change that.

They came to us with a WordPress site more than ten years old: slow, awkward to edit, and unable to take a donation properly. We redesigned it, rebuilt it headless on Sanity and Next.js, migrated a decade of content, built a custom donation flow on Raisely and Stripe, and now host and support the platform we built.

03 THE WORK

Chapter by chapter.

The brief

AIP Foundation runs road safety programmes across 36 countries: helmets for schoolchildren, driver and teacher education, infrastructure work, campaigning and the research that proves any of it worked. It is field work, in many languages, funded by donors and corporate partners who need to see where their money went.

The website carrying all of that was WordPress, and more than a decade old. It was slow, the editor fought the people using it, and a decade of programme reporting had accumulated inside it. Every new campaign meant a developer ticket.

Design, and an editor they'd actually use

We redesigned the site from scratch around the way the Foundation actually communicates: programmes, countries, campaigns and impact, rather than a blog with pages bolted to it. The design gives the photography room to carry the story, because in this sector the photography is the argument.

Then we designed the back of it. In Sanity we modelled their content properly, programmes, countries, publications, campaigns, people, so the communications team composes pages from blocks that already look right. No developer in the loop, and no way to accidentally break the design.

Ten years of content, migrated

The unglamorous half of the project, and the half that decides whether a replatform is a success. A decade of WordPress had to come across into a structured headless model: pages, posts, programme reporting, publications, media and the multilingual content underneath it.

We migrated the data rather than retyping it, mapped the old URL structure to the new one so the Foundation kept the search equity it had spent ten years earning, and tested the result against the old site record by record before anything went live.

Donations, built properly

A non-profit site has one job the rest do not: it has to take money, cleanly, on the first attempt. We built a custom donation implementation on Raisely, integrated through its API and settled through Stripe, rather than dropping in an off-the-shelf embed and hoping.

That means the giving flow lives inside their design instead of bouncing donors to a third-party page, the campaign and appeal structure matches how the Foundation actually fundraises, and the finance side reconciles in the tools they already use.

Launch, then we keep it running

We ran the project end to end: design, build, integration, data migration, testing and launch. The platform is Next.js on the edge with Sanity behind it, so pages are fast wherever a donor or a ministry official opens them, and content changes go live without a deployment.

We did not hand over a repository and leave. Saigon Digital hosts the platform, maintains it and supports the team using it, which is the arrangement that stops a good rebuild quietly ageing into the next ten-year-old website.

Awaiting quote

A client quote from AIP Foundation belongs here. Placeholder only, not a real testimonial, and not for release.

Name and role to confirm
AIP Foundation

Questions about this project

Is a headless rebuild overkill for a charity website?

Not when the site is the collection tin. A charity site has to take donations reliably, publish in several languages and survive a decade of programme reporting. That is the same engineering problem a commercial platform has, and the running costs of getting it wrong are donations you never see.

What happens to ten years of content in a replatform?

It gets migrated, not retyped. We moved AIP Foundation’s decade of pages, posts, publications and programme reporting into a structured Sanity model, mapped the old URLs to the new ones so the search equity survived, and tested the result record by record before launch.

Can we take donations without a third-party donation page?

Yes. We built a custom flow on Raisely and Stripe so the donation stays on the Foundation’s own site, in their own design. Sending a donor off to a generic hosted page is where a meaningful share of them stop.

Who maintains it after launch?

We do. AIP Foundation is a build-and-support engagement, so the team that built the platform also hosts and looks after it. See hosting & maintenance.

Want to be
the answer?

Tell us what you're working on. You'll get an honest answer about whether we can help, and exactly how.

Start a project

Prefer email? hello@saigon.digital

Next case studyAnh Chi Em, CASE STUDY · SOCIAL ENTERPRISE→