Duncan Anderson

Trauma Therapy Group · Client · 2026

Trauma Therapy Group Publisher

A publishing workspace that turns approved Google Docs into review-ready WordPress drafts, while a person makes every clinical and publishing decision.

Delivered

The problem

Trauma Therapy Group publishes articles about mental health. Each article is written and approved in Google Docs, and then someone still had to rebuild it for the website: clean up the HTML, fill in the SEO fields, prepare and upload a featured image, and assemble the page in Elementor. Each of those steps was manual, and each was a chance to break the formatting or miss a field. The team needed articles that looked right and carried complete SEO fields without anyone hand-editing HTML.

Speed was not the only constraint. Because the content concerns mental health, publication could not be automated. Any tool had to take the rebuilding work off the team's hands while leaving clinical, editorial and publishing decisions exactly where they were.

The leadership side had a related problem. Revenue, appointments, therapist capacity and expenses lived in Jane reports and bank exports, so answering the weekly question of what needs attention meant pulling several files together by hand.

What I built

I built a private publishing workspace. It takes a shared, approved Google Doc, cleans the content and prepares the article structure. It suggests SEO metadata and generates a featured image consistent with the practice's brand, and both stay editable. The editor reviews each choice before the tool uses the WordPress REST API to create an Elementor draft.

Every suggestion is a starting point, not a decision. The SEO title, description and featured image are shown to the editor before anything is sent to WordPress, and any of them can be changed or replaced. That keeps the tool useful on the articles where a suggestion is right, and harmless on the ones where it isn't.

The tool never publishes. WordPress receives a draft, and publication remains a separate human action. That boundary was the point of the design, not a limitation added at the end: formatting, metadata, image selection and draft assembly now happen in one guided process, and the judgment about what goes live stays with the team.

I also built a private leadership dashboard that brings Jane reports and bank exports into one weekly view of revenue, appointments, therapist capacity, expenses and the questions that still need checking. The reporting period and source coverage are visible, and open questions stay on screen instead of being smoothed over. Direct client details are removed before reporting data is stored. The dashboard is built around what the owner needs to decide each week, not around every figure the source systems can produce.

  1. 01ImportTake the approved Google Doc.
  2. 02CleanStrip the formatting and build the article structure.
  3. 03SuggestPropose SEO fields and a featured image.
  4. 04ReviewThe editor checks and edits every choice.
  5. 05DraftCreate an Elementor draft in WordPress. A person publishes.

What stays human

  • Clinical and editorial decisions about every article.
  • SEO and image choices, which stay editable until the editor accepts them.
  • Publication. The tool only creates drafts.
  • In the dashboard, open questions are left for leadership to answer rather than resolved by the system.
  • Leadership decides what the weekly figures mean and what to do about them.

What can be verified

  • The publishing phase was completed and delivered to the client.
  • The client's website is public; the publishing workspace and dashboard are private.
  • Client content, reporting data and screens are not shown. Any illustration is representative.
  • No time-saving, traffic or financial figures are claimed.

Stack

  • Next.js
  • TypeScript
  • Google Docs
  • WordPress REST API
  • Elementor
  • Yoast SEO
  • Image generation

Have a workflow that eats your team's week?

Tell me about it in 30 minutes. If AI isn't the right fix, I'll say so.