Bryan Willson

A Standard-plan user asks your AI assistant about SSO. It answers from the Enterprise docs. The text matched, the plan didn’t. Embeddings capture what the text means, not who it’s for. Metadata fills that gap → tinyurl.com/5hdtxaed #TechnicalWriting #RAG #TechComm #AIdocs

Second product, same argument: one docs site or separate ones? Both setups fail the same way. The real question is what must stay separate for readers and what must stay shared for the team. Read the article → tinyurl.com/4dp4ss36 #TechComm #Documentation

Documentation generation with AI takes under a minute. Reads perfectly. Also wrong — because the ticket it drew from was outdated before the writer even opened it. Where should tech writers sit in the SDLC? 🧵👇 Read → tinyurl.com/39c2tf87 #TechnicalWriting #AIWriting #SDLC

Your changelog and your release notes should never read the same. One's for developers. One's for users. Most teams write both the same way — which is why nobody reads either. Read more → tinyurl.com/4y8mec2y #TechnicalWriting #ReleaseNotes #DevOps #TechComm #CICD

Ask MT to translate the same term twice, and there's no guarantee it comes back the same way. That's how one feature name ends up with three names across your docs. We asked @alconost what actually fixes it. Read here→ tinyurl.com/yxamm92s #Localization #TechDocs #AI

Docs-as-code brings technical documentation into the same workflow as software development: Git, pull requests, versioning, CI, automated validation, and continuous publishing. In this article: popular docs-as-code tools → tinyurl.com/2uuzse7j #TechnicalWriting #DocsAsCode

Same warning copied into 40 topics. Product changes, and now you're hunting down 40 places to fix it. Snippets fix this: write the block once, insert it everywhere, update the source when things change. Read more → tinyurl.com/3ee2a2bj #TechWriting #DocumentationManagement

Two sentences that explain this better than any doc redesign meeting: Text tells users what to do. Video shows how it actually looks in the UI. Full breakdown of when to use each format → tinyurl.com/wmyn2m9x #TechnicalWriting #TechComm #Documentationtips

AI agents are only as useful as the data they can reach. MCP changes that — one server, any compatible client. We built a working MCP server in Python in under 30 lines. Step-by-step guide 👉 tinyurl.com/yc87rbxn #mcpserver #python #TechComm

Publishing docs for more than one product or brand? ClickHelp now lets you run several independent, public-facing documentation sites from a single portal. One place for authors. Separate sites for readers. Now in public beta — try it free at clickhelp.com

Regex = superpower for technical writers. Search, replace, extract, automate — in seconds instead of hours. Full guide👉 tinyurl.com/35fbyb9z #TechnicalWriting #TechComm #Documentation #regularexpressions #regex

Google Docs works well for small docs. But at scale — reuse, versioning, and publishing become painful. Read 🤓 tinyurl.com/ybnp2mrc #TechnicalWriting #TechComm #Documentation #AI #ClickHelp #GoogleDocs #KnowledgeManagement #SingleSourcing

AI is changing how technical writers create video content 🎬 From Descript's text-based editing to Synthesia's AI avatars — tools that used to need a full production team now fit into one workflow. Full breakdown 👉 tinyurl.com/mvsf6tm8 #TechnicalWriting #AITools #TechDoc

AI agents are no longer just “reading” documentation—they can now interact with your documentation portal directly via MCP (Model Context Protocol). This opens the door to more dynamic technical writing systems. 👉 tinyurl.com/ypmdc5v3 #AI #MCP #TechnicalWriting #Documentation

AI is changing customer support — not by replacing humans, but by helping them work faster. With Agent Assist tools. The result: faster resolutions, happier customers, less burnout. Read more 👉 tinyurl.com/fywmbnwv #CustomerSupport #AI #AIAgents #CX #CustomerExperience

Still sending users to a separate help page mid-task? That's where they drop off. In-app help keeps guidance inside the product right where users need it. Read more 👉 tinyurl.com/3sfkwdrm #InAppHelp #UserOnboarding #ProductAdoption #UX #TechnicalWriting

Your documentation exists, but AI tools can't read it. When ChatGPT fetches your portal and gets a wall of HTML, it guesses. Sometimes it guesses wrong (confidently.) The content is fine, the delivery isn't. Read tinyurl.com/3ykd9j7p #TechnicalWriting #AITools #Documentation

Architecture docs help teams align on system structure, decisions, dependencies, and future changes. A practical guide to writing architecture documentation that’s actually useful 👉tinyurl.com/3vkvhbyu #TechnicalWriting #SoftwareArchitecture #DevDocs #Documentation

Developer docs aren’t just “nice-to-have.” They’re core infrastructure for IT teams — just like CI/CD, observability, and security. Learn how to build docs that reduce outages, speed up onboarding, and actually stay up-to-date 👉tinyurl.com/4323me8p #DevDocs #DevOps #techcomm

Our April 2026 update is out 🚀 Claude and Cursor can now read and write your ClickHelp docs directly. Plus API v2, Markdown export, language switcher, and more. Read the details → tinyurl.com/5fcbxw3z #update #clickhelp #ai #mcp #techcomm #technicalwriting