Bill Elgin · Custom WordPress

WordPress without the plugin pile-up.

This custom WP theme developed by Bill Elgin is a working example of clean, maintainable WordPress development: a custom theme, native APIs, restrained tooling, and front-end work that stays readable after handoff.

WP Development

Why this site exists

Hire someone who can build WordPress carefully — and maintain it properly.

Comfortable working in both WordPress code and within the WP admin dashboard. This site is the evidence: maintainable theme structure, performance-conscious assets, accessibility basics, and a local workflow with Git and Docker/wp-env before anything reaches production.

How I work

Strategy, code, AI, experience, and care.

Strong websites come from combining thoughtful planning, solid engineering, modern tools, careful iteration, testing, deployment discipline, and ongoing support — not from any single shortcut.

  • Start with intention
  • Use the right tools
  • Build, test, iterate
Process diagram illustrating how strategy, code, AI, experience, and care work together.

Capabilities

What this approach brings to a WordPress project.

Whether the need is a new custom theme or steadier care of an existing site, the focus stays the same: clarity, restraint, and maintainability.

  • Build custom themes

    From templates to design tokens — WordPress that editors can use and developers can extend without a page builder.

  • Maintain what you already have

    Inherited sites, tangled plugins, and unclear themes are normal. The work starts by understanding the system before changing it.

  • Improve front-end quality

    Responsive layouts, keyboard support, reduced-motion respect, and lean assets that feel intentional rather than bolted on.

  • Modernize the workflow

    Local development with wp-env, Git for reviewable changes, and a controlled path from staging judgment to production.

Evidence on this site

Filter the capabilities this implementation proves.

These are not fictional client case studies. Each card describes something you can inspect in the theme, the interactions, or the local workflow behind this site.

Filter capability cards by category

  • Themes

    Custom theme architecture

    This site ships as a classic custom theme with template parts and shared chrome — not a page-builder export.

    • Native APIs
    • No page builder

  • Performance

    Lean front-end habits

    Proper enqueueing, deferred scripts, and a system font stack that avoids unnecessary third-party font requests.

    • Enqueueing
    • System fonts

  • Workflow

    Local before live

    Docker/wp-env for local parity and Git for reviewable changes — so production is not the first place code is tested.

    • wp-env
    • Git

  • Maintenance

    Care for inherited sites

    Updates, plugin review, and smoke checks treated as engineering work — not a scramble after something breaks.

    • Upgrades
    • Plugin restraint

  • Themes

    Accessibility built in

    Skip links, labeled controls, keyboard-friendly filters and navigation, visible focus, and reduced-motion support.

    • A11y
    • Responsive

  • Performance

    Intentional JavaScript

    The filterable cards and reveals on this page use a small vanilla script — progressive enhancement, no framework tax.

    • Vanilla JS
    • Progressive

Working approach

Understand first. Change with intent. Leave the next person a cleaner system.

Good WordPress work is judgment: when core APIs are enough, when a plugin earns its place, and when custom code is the cleaner path. The preference is to preserve what already works while improving structure, accessibility, and maintainability.

  1. Read the existing project Theme, plugins, content, and hosting habits before proposing big swings.
  2. Prefer maintainable defaults Native WordPress patterns, restrained dependencies, and code other developers can follow.
  3. Test locally, then promote wp-env, Git, and checks so production is a controlled step — not an experiment.

Next step

Need WordPress built, cleaned up, or taken over carefully?

Whether it is a custom theme, an inherited site, or a maintenance rhythm that needs steadier engineering, start with a short note on the Contact page.

Contact Bill Approach