Projects — Christopher Goehrs

Projects

Featured work and project stories.

A curated view of professional projects, workflow improvements, technical leadership, and open-source/personal work as it becomes relevant.

Professional

Custom Ecommerce Platform

WordPress was a hard client requirement, but the catalog and pricing rules went well beyond what off-the-shelf store plugins could handle. I built the commerce layer directly in PHP so the business rules drove the code, instead of forcing the business to fit a plugin.

Modeled quantity price-breaks and customer-specific pricing as first-class rules rather than plugin add-ons.
Kept a heavily customized catalog supportable, so later changes did not require unwinding earlier work.
Delivered the deep customization the client needed without leaving the mandated WordPress stack.

Professional

CI/CD Workflow Standardization

Every developer deployed a little differently, which made releases slow and easy to get wrong. I introduced a shared CI/CD workflow so deploying became a repeatable step instead of a per-person ritual.

Replaced ad-hoc, developer-specific deploys with one pipeline the whole team followed.
Made releases predictable enough that shipping stopped being a recurring source of risk.
Cut the manual steps that had the team babysitting deployments.

Professional

SOC 2 Compliance SaaS Platform (In Progress)

Building a custom .NET platform with a Blazor frontend to support SOC 2 readiness work through structured workflows, clearer operational visibility, and maintainable application architecture.

Translating compliance-heavy requirements into practical product and engineering decisions.
Owning architecture and implementation of a custom .NET + Blazor product while coordinating delivery across distributed contributors.
Designing for long-term maintainability so the platform can evolve with changing compliance and customer needs.

Professional

Custom .NET + Kentico MVC Platform

The client workflows did not fit Kentico standard page models or its storage assumptions. Rather than bend the business to the CMS, I extended Kentico MVC and built custom data-storage interfaces so the platform matched how the business actually worked.

Built custom Kentico MVC page patterns for requirements the stock CMS could not express.
Designed data-storage interfaces so operational data stayed usable across the systems that depended on it.
Kept a heavily customized build maintainable and releasable, not a one-off that could not evolve.

Professional

CMS Platform Leadership

Client work spanned five CMS ecosystems with very different strengths, so choosing the right platform mattered as much as building on it. I delivered and supported projects across all five and helped match each client to the platform that actually fit.

Worked across five CMS platforms instead of forcing every client onto one familiar stack.
Built and maintained Kentico/Xperience implementations spanning multiple major versions.
Kept diverse, sometimes-legacy CMS environments stable and supported.

Leadership

Distributed Team Technical Leadership

Distributed and offshore teams tend to fail on communication gaps, not on talent. My role was to close those gaps: turning vague requirements into clear implementation work and keeping review standards consistent no matter who wrote the code or where they sat.

Translated ambiguous requirements into implementation work offshore developers could act on directly.
Scaled review depth to risk: light on routine changes, thorough on larger or higher-risk features.
Held remote contributors to the same quality and maintainability bar as in-house work.

Workflow

AI-Assisted Development Process

AI adoption on a team usually collapses into either a free-for-all or an outright ban. I documented a middle path: a repeatable process where AI accelerates the work, but every output clears the same engineering review as any other code.

Used AI for research, prototyping, documentation, implementation support, and review assistance.
Required validation, maintainability, security checks, and HIPAA-aware risk review when work touched regulated data.
Set team expectations that AI output is draft code and must pass developer review before merge.