Brandon A. Cox

Work

Work that connects the message to the next step.

These are not one-off redesigns. They are case studies in ongoing retainer relationships where communications consulting, WordPress development, content systems, and staff workflows keep evolving after launch.

A diocesan website as ongoing publishing hub and communications center
WordPress ยท Divi ยท Retainer support
Visit current site
DirectoryChurch finder
PublishingNews and stories
MediaPodcast flow
StaffReusable systems

What changed: clearer diocesan publishing paths and church-finder visibility. Why it mattered: staff could keep news, events, and local church discovery moving without a rebuild every season. Handled: WordPress, Divi, publishing support, and retainer care.

A large diocesan platform with archives, ministry hubs, and public tools
WordPress ยท Divi ยท Retainer support
Visit current site
DirectoryChurch finder
ArchivesMigration support
MinistryFocused hubs
StaffUsable tools

What changed: a large diocesan web system became easier to navigate, maintain, and extend. Why it mattered: archives, ministries, and public tools stayed findable for a broad audience. Handled: WordPress support, content architecture, archives, and ongoing problem solving.

A historic church site with elegant public pathways and practical operations
WordPress ยท Events ยท Forms
Visit current site
EventsScannable calendar
FormsPayments and workflows
StoryHistory content
SupportOngoing updates

What changed: events, forms, payments, and public pathways became calmer and easier to scan. Why it mattered: a historic church could keep practical operations connected to public communication. Handled: WordPress, events, forms, and ongoing updates.

A merger-scale diocesan platform with shared identity and practical systems
WordPress ยท Directory ยท Communications
Visit current site
MergerReunified site
DirectoryChurch finder
EventsShared calendar
CommsNewsletter paths

What changed: a merger-scale site gave shared identity, church discovery, and events one clearer home. Why it mattered: leaders and visitors could find the system after organizational change. Handled: WordPress, directory structure, communications paths, and launch support.

A church website and support relationship built around clear next steps
WordPress ยท Sermons ยท Retainer support
Visit current site
SitePublic pathways
SermonsPublishing flow
EventsCurrent updates
SupportOngoing care

What changed: public pathways, sermons, and current updates had a more dependable site foundation. Why it mattered: church staff could keep the site useful after launch. Handled: WordPress, sermon publishing flow, retainer support, and ongoing care.

Formal case studies are coming. For now, each project opens the current client site so the portfolio points somewhere useful while the deeper stories are being written: information architecture, content flow, publishing workflows, integrations, retainer support, and the public design that makes all of it usable over time.

Want this kind of clarity for your site?

Start with a clarity review. We will look at the site, the message, the workflow, and the next step before deciding whether the work belongs with Brandon or 5ox Creative.