Julie Zimmerman

WordPress & CMS Engineering

Building WordPress systems that remain reliable after launch.

I design and maintain WordPress as an application platform, not merely a page builder.

My work spans custom plugins and themes, structured content, accessibility, migrations, security recovery, and fleet-wide operational standards across more than 250 active environments.

Philosophy

Engineering Philosophy

A CMS succeeds when editors can use it confidently and engineers can still understand it years later.

A reliable CMS starts with clear content models and predictable behavior.

  • Customization should solve a real editorial or operational problem.
  • Accessibility, security, and maintainability belong in the architecture.
  • Fleet-scale work requires standards, repeatable checks, and planned retirement paths.

Fleet-scale work requires standards, repeatable checks, and planned retirement paths.

Problems

Problems I Solve

The most valuable work usually begins where a system has accumulated complexity, operational risk, or assumptions no one has revisited.

  • Custom plugins, themes, blocks, and post types
  • Complex migrations and legacy modernization
  • Fleet-wide updates, QA, and operational consistency
  • WCAG remediation and accessible content structures
  • Malware cleanup and hardening without destroying business functionality

Approach

How I Work

I begin with the publishing workflow and the system's actual constraints. I map the content model, dependencies, integrations, and failure points before choosing implementation details.

At fleet scale, one-off fixes become liabilities. I favor reusable patterns, clear ownership, conservative dependencies, and tooling that makes drift visible.

Selected Projects

Work that makes the method visible.

WordPress Fleet Management

Standards and operational tooling across 250+ active web environments.

  • Update and launch QA
  • Lifecycle and supportability standards
  • Cross-site incident response

Zoological Institution CMS Framework

A specialized WordPress content model informed by twelve years of institutional zoo photography.

  • Animal and collection-centered content architecture
  • Editorial workflows for nontechnical teams
  • Reusable structured content

WordPress Compromise Recovery

Forensic cleanup and hardening for persistent malware in legacy environments.

  • Payload and persistence analysis
  • Core and plugin integrity checks
  • Recovery followed by operational remediation

Managed Hosting Policy

A supportability and planned-obsolescence framework for a large production fleet.

  • Defined lifecycle expectations
  • Reduced permanent exceptions
  • Lowered technical debt and response complexity

Experience

Representative experience.

Zee Creative · 2011–Present

Lead Web Developer

Lead developer and systems architect for a large, long-lived portfolio of production websites and integrations.

  • 250+ active web environments
  • Custom application and integration development
  • Technical standards, migration planning, launch QA, and incident response

SunGard Higher Education · approximately 8 years

Lead Software Engineer

Technical lead in enterprise higher-education software, working across large Oracle systems, performance testing, defect analysis, and release delivery.

  • Synthetic data generation exceeding one million records
  • Defect cross-reference and recurrence prevention
  • Enterprise release estimation and delivery

Technologies

Core technologies and areas of focus.

WordPress

Custom PluginsCustom ThemesBlock EditorREST APIWooCommerceCustom Post TypesMultisite

Engineering

PHPJavaScriptSQLHTMLCSSGitPython

Focus

Fleet ManagementWCAGMigrationsSecurity RecoveryEditorial WorkflowsPerformance

Business Value

Why durable CMS architecture matters

Most CMS costs arrive after launch: fragile updates, unclear ownership, inaccessible interfaces, and custom behavior no one can safely change.

A well-structured system lowers those costs by making routine work predictable and unusual failures diagnosable.

Contact

Let's Talk

For technical leadership, architecture, modernization, or complex systems work, contact me directly.

Contact Julie
The best CMS is not the one with the most features. It is the one people can operate safely.