Timeline
Case Study 01
Central Church of Christ Website (Minnesota)
A paid, 7-8 month web delivery for a Minnesota-based church organization. The project started with WordPress for discovery and template direction, then shifted to a coded website with structured hardcoded content for reliability and full control.
Scope
10+ pages, multi-department structure
Status
Live production website
What I Built
- Events, departments, and staff pages with role-based content grouping.
- Prayer timings, services, educational offerings, and church history sections.
- Department member history and poster/profile information pages.
- Clean content hierarchy to keep non-technical visitors oriented.
Difficulties and Solutions
- Most content was not available in reusable digital form, so information intake was manual and iterative.
- Image volume was high; content and media had to be standardized before publishing.
- Donation flow intentionally avoided payment gateway by client requirement; contact-based donation path was used instead.
- Cross-checking facts required both client-provided details and additional online verification.
Vertical Learning Highlight
This project was the biggest jump in my content architecture and delivery maturity. I moved from theme/template-level work to coded, structure-first implementation where information design, content reliability, and long-term maintainability mattered as much as visual quality.