A ministry that publishes without calling the developer
A website and multi-user publishing system for a mission organisation supporting theological education and frontline pastors in Myanmar — with an editorial workflow the team runs themselves.
A Burmese-speaking church on the Thai–Myanmar border, rebuilt from a single builder page into eight pages with its own content system — and a free Sunday ride you can book from a phone instead of calling a stranger before seven in the morning.
Ambassadors for Christ Church — AFC — has met in Mae Sot since 2013, on the Thai side of the Myanmar border, and worships in Burmese. Its congregation is the Myanmar community in that town: people working long hours, often a long way from the church, and frequently without a vehicle. Whether somebody can come on Sunday is a transport question before it is anything else.
The church had answered that years earlier by running a free pickup on Sunday mornings. The website had not. Everything the church had online was one page built in a website builder, and the ride was a sentence on it — telephone the pastor before seven o’clock. That asks a newcomer to find the number, spend the credit, and ring a stranger at dawn to ask for a lift. Three chances to decide against coming, before anyone has met them.
Eight pages with a real content system behind them, and every word of the old page carried across first: the service times, the ministries, the pastor’s number, the Bangkok Bank details digit for digit. Nothing was left to be re-entered later, because later is how a church loses the account number people give to.
The ride is a form now. Name, phone, where to collect you, how many are coming, which service — filled in from the phone already in somebody’s hand, at any hour, without a conversation. The number stays on the page for anyone who would rather call; the form is for everyone who would not have.
Around it, the things a congregation actually looks for: five albums of the church’s own photographs, a news section, giving with the bank details one tap from copied, WhatsApp reachable from every page, and an admin the church’s own people can work in — it reads in English, not only in the language it was built in.
Eight pages live, in the church’s own words and its own photographs, and a Sunday ride that can be asked for without phoning anybody.
Measured on a phone on 4 August 2026, every one of the eight pages scores 100 for accessibility, best practices and search. That is not a trophy. This congregation reads on inexpensive Android phones over patchy mobile data, and each of those numbers is a different way of saying the page will work anyway.
The rest of the site is what everybody expects a church site to have. The form is the part that changes who is in the room.
A website and multi-user publishing system for a mission organisation supporting theological education and frontline pastors in Myanmar — with an editorial workflow the team runs themselves.
A humanitarian organisation working across Southeast Asia, on a WordPress theme written from scratch — so the team keeps the editor they already know without the template look.