DeployIt blog — product knowledge for humans and AI agents
Guides on MCP servers, wiring support agents like Intercom Fin or HubSpot Breeze to your codebase, and keeping product knowledge — docs, changelogs, help centers — up to date at every deploy.
New here? Start with the MCP server for your codebase, or see how the same expert answers your team in the AI Help Center & Messenger.
Your internal wiki contradicts the code: which one do you trust?
When the wiki and the code disagree, the code wins on what the product does, the wiki on why and how the team works. A precedence rule, sentence by sentence.
Read more →How do you announce an API or feature removal so nobody misses it?
A deprecation notice fails when it is read, understood, then forgotten. What it must contain, when to repeat it, and how to derive it from the code instead of writing it from memory.
Read more →Changelog, release notes, "What's new": which one do you need?
One change, three artefacts, three different texts. A worked example shows what each of a changelog, release notes and a "What's new" page keeps, drops and rewrites, and how to pick.
Read more →How do you keep developer portal content current between redesigns?
A developer portal ages page by page, not all at once. The way out: know which pages carry a fact from the code, and recompute those from the code instead of rereading them by hand.
Read more →How do you keep an engineering team's onboarding docs current?
An onboarding guide goes stale because it describes the code as it was the day it was written. Pull the facts from the code itself, and keep by hand only what no code can say.
Read more →What should an API changelog for integrators contain?
An integrator reads an API changelog to decide one thing: do I have to touch my code? Six fields answer it, and most changelogs carry two.
Read more →Can you generate Notion documentation from your code without overwriting what your team writes?
Generating Notion documentation from code is the easy part; making it coexist with what your team writes by hand is the real problem. The four writing rules that decide whether the page survives.
Read more →How do you build a "What's new" page generated from git?
A "What's new" page is not a changelog with better styling: its window belongs to the reader, not to the release. What you have to derive from diffs to make it work, and the triage that remains.
Read more →How do you detect documentation drift?
You do not find a stale page by rereading it. You start from the diffs of the period and work back to the pages they invalidated. The manual audit, its blind spots, and continuous detection.
Read more →How do you keep a help center in sync with releases?
Not by writing faster: by deriving the pages from the source that changes. The back-of-the-envelope maths behind why manual updating falls behind, the four surfaces a release invalidates at once, and the loop that holds.
Read more →Architecture Decision Records from Git: Always Current
ADRs go stale as soon as the code moves on. Derive them from git history so every decision record stays current, traceable and auditable — for humans and AI agents.
Read more →10 minutes now. The dashboard tonight, your first report on Monday. You decide.
Free plan, no credit card. Read-only. No action required from your team.
Free plan · No CC · Read-only · Hosted in EU