Case study
A church website that answers the question visitors actually ask
A Queens church website organized around service times, sermons, events, and the information a first-time visitor needs.
The situation
A growing congregation in Jamaica, Queens, with an active Sunday service and no website a visitor could rely on.
The question a first-time visitor asks is not “what do you believe.” It is “when do you meet, and where do I park.” That answer has to survive being read on a phone, one-handed, on the way out the door.
Whatever replaced it had to be editable by the church office. A site only its builder can update stops being true within a month.
What I built
- Service times as the first thing on the page
- Day, time, and address above the fold on every screen size, marked up so Google and Maps can read them directly rather than guessing from prose.
- Sermons and events in one place
- Dedicated areas for sermons and events give the congregation a place to find messages and upcoming activities. The site includes browser-based content editing.
- Built bilingual-ready from the start
- The site’s structure carries a second language whenever the congregation wants one, rather than needing a rebuild to add it later.
- Fast on the phone people actually own
- Static pages served from a CDN, with responsive layouts for phones and larger screens. Hosting, content upkeep, and software maintenance are distinct parts of keeping the site working.
Where it landed
- Service times findable in one glance, on a phone
- Dedicated sermon and event sections
- Responsive layouts for phones and larger screens
- Published service information and location links
Written by Travis Lodge, Music director & founder · September 2026
Church in New York City with the same problem? Tell me about it. I reply personally within two business days.