If you have a similar business problem
Read the plain-English summary, real situation, and result first. Those sections explain what the work changed without requiring you to know the code or platform details.
Selected Work / Case Studies
Real development case studies you can learn from.
These are production scenarios and product work, not a gallery of screenshots. Named live work is shown where it can be public, while other client details stay private. Alongside client case studies, in-house products such as ConduitTools show how focused ideas are designed, built, and maintained over time.
How to use this portfolio
Read the part that helps you make a better decision.
You do not need to understand every technology mentioned in a case study. Start with the problem and result, then go deeper into the implementation only if it is relevant to your own site or product.
If you are evaluating a technical approach
Read the constraint and implementation sections. They explain why the obvious fix was not enough and what tradeoffs shaped the final solution.
If you are planning a release
Use the release-check section as a practical QA reference. It shows what needed verification before a change was safe to ship to real users.
If you only want the takeaway
Jump to the reusable lesson. It condenses the case into a principle that can help with future websites, stores, applications, or integrations.
28Retail e-commerce
Case mapContent QAEditorial CTA → Resolve canonical route → Update href → Test production URL
- 01Editorial CTA
- 02Resolve canonical route
- 03Update href
- 04Test production URL
Retail e-commerce
Finding brand-page links that looked correct but sent shoppers to 404 pages
Editorial copy can be visually finished and still fail the buying journey when a store-location or shop-online link points to an outdated route.
Read case study29WordPress systems
Case mapRelease workflowNormal live page → ?debug preview gate → New template + assets → QA on real data
- 01Normal live page
- 02?debug preview gate
- 03New template + assets
- 04QA on real data
WordPress systems
Using ?debug as a controlled live-preview feature flag during a WordPress rebuild
A major location-template update needed real production content and integrations for QA, but unfinished ACF fields, sections, styles, and layout changes could not replace the stable public page until the rebuild was complete.
Read case study30U.S. e-commerce accessibility
Case mapTheme remediationWAVE finding → Inspect rendered DOM → Fix Liquid semantics → Keyboard verification
- 01WAVE finding
- 02Inspect rendered DOM
- 03Fix Liquid semantics
- 04Keyboard verification
U.S. e-commerce accessibility
Fixing a cart drawer ARIA relationship and an empty mega-menu link at the source
The homepage looked normal visually, but WAVE exposed two markup failures: a dialog labelled by an ID that did not exist and a navigation CTA rendered without meaningful content or destination.
Read case study31U.S. e-commerce accessibility
Case mapAudit methodologyMap templates → Run automated tools → Test interactions → Resolve discrepancies
- 01Map templates
- 02Run automated tools
- 03Test interactions
- 04Resolve discrepancies
U.S. e-commerce accessibility
Auditing representative e-commerce templates and user journeys instead of blindly scanning every URL
The storefront had too many products and content URLs for a useful manual review of every page, so the audit was organized around unique templates, shared components, important states, and real purchase journeys.
Read case study32U.S. e-commerce accessibility
Case mapMonitoring & documentationMonthly baseline → Compare evidence → Remediate regressions → Retest
- 01Monthly baseline
- 02Compare evidence
- 03Remediate regressions
- 04Retest
U.S. e-commerce accessibility
Turning accessibility checks into a dated monthly evidence and regression workflow
The legal follow-up required ongoing evidence, so the accessibility process needed a repeatable monthly record that could distinguish fixed issues, new regressions, manual-review items, and third-party limitations.
Read case study33U.S. e-commerce accessibility
Case mapPerformance & accessibilityBaseline metrics → Image + asset audit → Reduce blocking work → Preserve semantics
- 01Baseline metrics
- 02Image + asset audit
- 03Reduce blocking work
- 04Preserve semantics
U.S. e-commerce accessibility
Improving a heavy Shopify product page without sacrificing accessibility semantics
A complex product page had slow lab metrics, large image payloads, third-party UI, and a lot of JavaScript. The optimization work reduced blocking work and image waste while keeping accessible names, live regions, focus behavior, and product interactions intact.
Read case study34WordPress systems
Case mapCRM & lead routingGravity Forms → Submission context → Zapier mapping → Salesforce lead
- 01Gravity Forms
- 02Submission context
- 03Zapier mapping
- 04Salesforce lead
WordPress systems
Connecting WordPress Gravity Forms to Salesforce through a traceable Zapier workflow
Website inquiries needed to move from WordPress into Salesforce reliably, with the page and form context preserved so the sales team could work from one consistent lead pipeline.
Read case study35WordPress systems
Case mapElementor developmentRegister widget → Editor controls → Render markup → Scoped styles
- 01Register widget
- 02Editor controls
- 03Render markup
- 04Scoped styles
WordPress systems
Building custom Elementor widgets with documented controls, rendering, and styling
A custom Elementor widget is only useful when editors can add it confidently and developers can understand where its controls, markup, and styles live after the original implementation is finished.
Read case study36WordPress systems
Case mapWordPress architectureTheme bootstrap → Feature hooks → Reusable helpers → Templates + shortcodes
- 01Theme bootstrap
- 02Feature hooks
- 03Reusable helpers
- 04Templates + shortcodes
WordPress systems
Organizing custom WordPress templates, shortcodes, hooks, and reusable theme behavior
As custom WordPress work grows, the difficult part stops being writing one shortcode or template and becomes keeping templates, hooks, helpers, and reusable rendering logic organized enough to change safely.
Read case study