Start here: what changes when we work together
If your website feels expensive to change, fragile to operate, or unclear on what to fix next, this is the work I do. I help teams stabilize WordPress systems, protect rankings while making changes, and leave behind operations your team can run without constant external support.
How I got here
I built my first website in 1996 in Notepad on a dial-up connection. WordPress became my core platform in the early 2000s and has stayed there. The work I take most often is the messy middle: delayed migrations, brittle publishing workflows, and sites that need to get faster without breaking what already works.
I live in Fort Erie and work with organizations across Canada. Most projects are remote. Local work in Niagara is usually with service businesses and training teams that need practical systems, not presentation theatre.
Client proof from real portfolio work
- Published portfolio examples: M.L. Campbell Training Centre, M.L. Campbell Website, Sayerlack Website, and o.canada.com.
- Draft/archive portfolio records: Corel, ABBX, Cognilore, Postmedia properties (Calgary Herald blogs, Dose.ca, and The StarPhoenix), Tinker Priest Media, Getaway Graphics, DNA Studios, and StockTwits.
- Typical engagement pattern: stabilize architecture first, remove editorial friction second, then improve discoverability and performance without making content teams relearn everything.
What clients ask me to fix first
- Publishing workflows that depend on one person and break when they are away.
- Theme and plugin stacks that are hard to update safely without regressions.
- SEO foundations that look complete on paper but fail in crawl, index, or internal linking behaviour.
- Handoffs where teams receive code but not operational clarity.
What I do
Most engagements follow three tracks in sequence: stabilize, improve, then enable your team.
Build and repair WordPress systems
Custom development, migration work, and cleanup passes for websites that have become difficult to run. This includes plugin architecture, technical SEO implementation, and editor workflows that survive staff changes.
Current scope of paid work →
Train teams to run what gets built
Workshops, mentoring, and delivery support for teams that need confidence after launch. Most programs are remote and Canada-wide, with periodic in-person sessions in Niagara.
Training programs & upcoming sessions →
Publish tools and field notes
I publish free plugins and templates, practical calculators, and long-form writeups on the blog. This keeps the work transparent and gives clients a clear view of how decisions are made.
Selected work & case studies →
How I work with teams
No black-box delivery
You see the reasoning behind architecture and content decisions. That makes handoff easier and prevents recurring rework.
Durable over clever
I optimize for maintainable systems: readable code, predictable publishing flows, and infrastructure that can survive the next plugin or core update.
Built to be operated by your team
Documentation, walkthroughs, and training are part of delivery. The goal is independent operation, not dependency.
Direct scoping
If a full rebuild is unnecessary, I will say that early. A smaller fix done well usually beats a larger project done for optics.
Lived examples from recent years
- I have inherited WordPress installs where editors avoided publishing because every update risked breaking layout. Those projects usually start with content model cleanup and safer defaults before any redesign discussion.
- On newsroom and training-oriented stacks, the recurring work is reducing handoff friction: fewer manual steps, clearer templates, and stronger review paths for non-technical teams.
- On technical SEO engagements, most wins come from fixing architecture, internal linking, and crawl/index hygiene, not writing bigger promises in metadata.
Where I work from
I work out of Fort Erie on the Niagara peninsula. Most projects are remote and Canada-wide. Locally, I support businesses and organizations across St. Catharines, Welland, Niagara Falls, and Fort Erie.
Background, in plain terms
- Web delivery since 1996, including two-plus decades of WordPress-led implementation.
- Corporate training and LMS delivery — including the M.L. Campbell Training Centre, a custom LearnDash platform in production since 2020 that grew learner attendance ten-fold over its life.
- MA in Learning and Technology (Royal Roads University), applied directly in handoff and team enablement work.
- Technical SEO and performance implementation focused on production architecture, structured data quality, and internal link systems.
- Open-source publishing through GitHub, plus ongoing documentation on the blog.
If you are new here, start with these
- Portfolio for delivery examples and company context.
- HTML5 Search for WordPress for plugin-level implementation quality.
- Construction calculators for practical publishing without lead-capture friction.
- WordPress pre-launch checklist for operational QA discipline.
How to reach me
If you are dealing with a difficult WordPress build, a migration that needs cleanup, or a training need your team has been postponing, send me a note. Include what is blocked, what has already been tried, and your timeline. I read inquiries myself and respond directly.