ADR Publishing Pipeline: From Architecture Decision to Confluence in 60 Seconds
ADRs die in the repo because only engineers read git. Here's how to wire a pipeline that publishes every merged ADR to Confluence (and Notion) automatically — with a worked .mdspecmap example.
Why AI Agents Need Your Specs in Git, Not Locked in a SaaS (And How to Serve Them from S3)
AI coding agents can't authenticate into your Confluence or Notion. They need specs at a URL they can reach. Here's the pattern for keeping a machine-readable copy current alongside your human-readable docs.
Publish Markdown to Confluence with GitHub Actions in One Line: A 2026 Setup Guide
A plain comparison of every real option for syncing markdown from GitHub to Confluence — mark, markdown-confluence, duo-labs, and mdspec — with a complete working setup you can copy today.
mdspec in 5 Minutes: From Zero to Publishing Markdown on Every Merge
A screencast-style walkthrough: create a repo, add one .mdspecmap, add the GitHub Actions step, push a commit, see it appear in Confluence or Notion. Real YAML throughout.
Spec-as-Code: Publishing One Markdown Source to Notion, Confluence, ClickUp, and S3 from a Single Repo
Spec-as-code is the missing layer between 'docs as code' and the reality of multi-tool engineering orgs. One markdown source in git. Automatic fan-out to wherever your team actually reads.