Two-campus visitor journey
Distinct campus information, first-visit guidance, service details, ministries, and connection paths within one recognizable church identity.
Church website / publishing / integrations
LifeWay Community Church
07 / 11A two-campus church website connecting first-time visitors, online worship, events, groups, devotionals, and a custom publishing and administration system.
Homepage: real church photography, a clear first-visit path, and information for both the Fred George and Fort Braden campuses.
THE BRIEF
What the project
needed to do.
LifeWay needed a website that could welcome someone new and remain useful to people already part of the church. With two campuses, several ministries, recurring messages, events, groups, and devotional writing, the site had to organize practical information without making every visitor start in the same place. The team also needed a way to keep that content current.
MY APPROACH
Connecting the design
with the work.
I combined a photo-led public website with React, TypeScript, and a Firebase content foundation. First-visit information, campus pages, watching, connecting, and devotional reading each have their own path. Planning Center integrations and custom administration support the operational side, while media and publishing tools let the website grow beyond its launch content.
PROJECT SCOPE
The work in detail.
Online worship & media
A Watch Online destination with the latest message, recent video listings, YouTube presentation, and a separate sermon archive.
Events & community groups
Planning Center calendar and group-feed integrations that connect public discovery with the church's existing operational tools.
Devotional publishing
Article reading and archive routes, legacy-content migration, structured metadata, and editable devotional content.
Custom CMS & media
Protected tools for pages, articles, events, sermons, galleries, media, and users, supported by visual page and rich-text editing.
Connection & giving interfaces
A Planning Center connect-card handler and giving interfaces backed by server-side payment handlers. Recurring giving remains labeled as a setup preview rather than an activated subscription flow.
THE EXPERIENCE
How the pieces connect.
- 01
Visit
Find the right campus and see what a first visit looks like.
- 02
Participate
Explore groups, events, and ministry opportunities.
- 03
Watch & read
Return for messages, devotionals, and church media.
- 04
Maintain
Update public content through protected publishing tools.
01 / PROJECT DETAIL
A church website has more than one audience.
Someone visiting for the first time needs a different set of answers from someone looking for this week's message or an upcoming group. The site gives those intentions distinct destinations: first visit, services, connection, watching, events, and devotional reading. Campus-specific pages keep practical local information from being lost in a general introduction.
The visual direction uses actual people and church life rather than an anonymous institutional presentation. The welcome page brings Eli and Kelley into that experience personally, while the homepage and campus information help a visitor move toward a real next step.
02 / PROJECT DETAIL
Connected publishing, video, and community information.
The public media experience brings recent YouTube messages into a dedicated watching destination. Devotional and blog routes provide a home for longer writing, with migration support for legacy articles. The build also includes search-friendly page snapshots and responsive image preparation.
Planning Center calendar and group feeds are part of the integration work. Behind the public pages, protected administration covers pages, articles, events, sermons, galleries, media, and users. Visual page editing and rich-text publishing give the team tools for routine content changes without treating every update as a new development task.
03 / PROJECT DETAIL
Practical operations, with clear implementation boundaries.
The project source includes a Planning Center connect-card submission handler, server-side Stripe payment-intent and webhook handling, and PayPal order handlers. These are implementation details behind the connection and giving interfaces, not evidence that a form or payment was completed during this portfolio review.
The monthly-giving choice is explicitly labeled as a recurring setup preview in the public interface. It is not presented here as an active subscription service. The captures show only public pages; no visitor record, giving transaction, or private church administration is exposed.
SELECTED SCREENS
A closer look at the work.
HAVE SOMETHING IN MIND?