GTM Toolkit

Developer-Native Marketing

Content Workflow Example

Standardize how marketing drafts move from idea to publish using GTM Toolkit checkpoints.

Workflow Stages
Suggested kanban columns for marketing and engineering partners
  • Briefing: Capture the idea, primary keyword, and success metric in planning docs.
  • Drafting: Create markdown under content/blog/YYYY-MM-DD-slug.md with frontmatter metadata.
  • SEO Lint: Run npx gtm-toolkit lint content/blog --format console and clear any errors.
  • AI Review: Use npx gtm-toolkit analyze --gaps to identify missing angles or sections.
  • Ready to Publish: Open a pull request once linting passes and reviewers sign off.
Weekly Ritual
Turn GTM Toolkit outputs into a repeatable marketing review
1. Every Monday, run npx gtm-toolkit audit --all and capture the scores.
2. Share regressions in Slack or Linear and assign owners for fixes.
3. Document agreed actions in your planning doc alongside the audit summary.
Continuous Improvement Loop
Close the gap between insights and published updates
  1. Lint existing content with npx gtm-toolkit lint content/blog --format json and log findings.
  2. Generate an execution plan using npx gtm-toolkit suggestions content/blog --format json --output fix-plan.json.
  3. Apply quick wins via npx gtm-toolkit fix --plan fix-plan.json --auto or review interactively.
  4. Regenerate SEO files with npx gtm-toolkit generate --all before merging the fixes branch.
  5. Re-run npx gtm-toolkit audit --content to confirm the improvements landed.

Need more structure? Pair these checkpoints with a GitHub branch naming convention such as content/feature/<slug> so progress stays visible in commit history.