Guest columns, technical guides, and white papers — practitioner-written, final-draft quality for trade and business press.

I write technical and practitioner-facing pieces for editors who need a senior voice — someone who has shipped the thing, not just read about it.

Writing context: Publishing at thisismyurl.com since 2012. Guest contributor to WordPress and editorial-technology publications. Past pieces cover WordPress at institutional scale, AI operations for teams, LMS architecture, and government digital delivery. Available for guest columns, contributed articles, technical how-to guides, white papers, and case studies. Rates on request; editorial brief required.

This page is for editors and content leads who need a practitioner byline: trade publications covering WordPress, CMS, ed-tech, and government digital; corporate communications teams that want thought-leadership that holds up under scrutiny; and organisations commissioning long-form research or technical documentation. If you already know what you need, email directly.

Who this is for

• ✅ Trade and industry publications covering WordPress, CMS and editorial technology, ed-tech, learning design, or government digital. The pieces I write are for practitioners, not beginners — your audience reads past the first paragraph.
• ✅ Organisations that need a practitioner voice for a white paper, technical brief, or case study — content that reads as written by someone who has made the calls being described, not a generalist writer working from an interview transcript.
• ✅ Corporate communications and L&D teams commissioning thought-leadership content for senior or executive audiences in media, education, government, or professional services.
• ❌ SEO content mills, AI-content enhancement shops, or publications whose model is publishing at volume with no editorial standard. I write one piece well, not ten pieces fast.
• ❌ Ghostwriting for platforms I can’t stand behind, positions I don’t hold, or topics where I haven’t done the work. The byline question gets settled before the brief does.

What I write

• Guest column / contributed article · 800–1,800 words. Opinion or analysis on a topic I can back with delivered work. Not a product review with a link at the bottom. Suitable for trade publications, association newsletters, and industry blogs with a senior readership.
• Technical how-to · 1,200–3,000 words. Step-by-step guides for practitioners who already know the basics. I write to the developer, the L&D manager, or the digital director — not the beginner SEO funnel. Diagrams and annotated code included where they earn their keep.
• Case study · 1,000–2,500 words. A real engagement, real constraints, real decisions. One of the few practitioners who can write a case study about delivered work without ghosting the hard part — the call that was wrong the first time, the constraint the client didn’t tell us about, the thing we would change.
• White paper or long-form report · 3,000–8,000 words. Research-backed argument with a clear position, commissioned by an organisation. Not a listicle with a landing page attached. Suitable for associations, government bodies, and vendors who want a credible practitioner voice, not a marketing document.
• Thought-leadership piece · 600–1,200 words. Short-form opinion for executive or senior-practitioner audiences. The kind of piece a VP of Digital forwards to their team with one sentence of annotation. LinkedIn long-form, internal publication, or external byline.

Topics I cover

The topics below aren’t a menu — they’re the areas where I have delivered client work or run production systems and can write from the position of having made the calls. An editor who needs a WordPress piece from someone who ran it at Postmedia scale is looking for something different from an SEO content writer who covered WordPress last quarter.

WordPress at editorial and institutional scale

Content models, editorial workflow governance, performance under a live news desk, migration decisions, and the gap between what the block editor promises and what a newsroom can actually use. Built for Canadian regional news publishers, post-secondary institutions, and federal government properties.

AI operations for teams

Routing architecture, cost attribution, governance documentation, and what it actually costs to run a multi-provider AI stack in a consulting practice. I built and run AIOS — the system I use for client delivery — and have been writing about the practical, unglamorous side of AI ops since before it was a LinkedIn topic.

Learning technology and LMS architecture

LearnDash, Sensei, and LifterLMS from the inside; curriculum design for knowledge workers and trades professionals; SCORM vs. xAPI where it actually matters; and what L&D teams get wrong when they buy a platform before they design the course. MA candidate in Learning & Technology at Royal Roads.

Government digital and accessibility

WCAG 2.2, AODA, public-sector delivery patterns, and the difference between accessibility compliance as a legal obligation and accessibility as a design discipline. Past work includes federal government delivery at CS-03 level and municipal digital projects in Ontario.

Rates and process

• Contributed article or guest column: from $1,200 CAD. One brief, one draft, one round of revisions. Revisions beyond the brief are scoped separately.
• Technical how-to or case study: from $1,800 CAD. Includes a pre-writing call to confirm scope, technical accuracy review, and diagrams or annotated code where appropriate.
• White paper or long-form report: from $4,500 CAD. Scoped by word count and research requirement. Includes a detailed brief, source review, and a structured outline before writing begins.
• Thought-leadership or LinkedIn long-form: from $800 CAD. One brief, one draft. Best when you have a clear position and need someone to write it in a voice that doesn’t read like a press release.

Send a brief or email directly at hello@thisismyurl.com.

Author bio