3d ago · 12 min read · Series: Git & GitHub for Technical Writers · Part 6 🔹 Part 1 — Git Basics for Technical Writers 🔹 Part 2 — Git vs GitHub: Understanding the Documentation Workflow 🔹 Part 3 — From Editing Files to M
Join discussion
Mar 12 · 8 min read · A few years ago, technical writers were asking whether AI would help us write faster. In 2026, the question feels sharper: will AI replace us? My answer is still no. Not yet. AI can already draft copy
Join discussion
Mar 9 · 5 min read · You have a .py file — or a handful of them — and you need a PDF or Word document. Maybe you're submitting coursework, sharing code with a non-developer, creating a printable archive, or reviewing an o
Join discussionMar 5 · 19 min read · Most organizations don't have a compliance problem. They have a documentation architecture problem. The policies exist. The procedures exist. Somewhere, there are checklists and training decks and aud
Join discussion
Mar 2 · 1 min read · Most documentation describes what an endpoint does. It rarely explains how the system thinks. In the current era of rapid technical evolution, products are being shipped at a velocity that makes 'Docu
Kklement and 1 more commented
Mar 3 · 8 min read · Vale: Prose Linting for Technical Writers and Documentation Teams Code has ESLint. CSS has Stylelint. But what catches the errors in your documentation? Most teams rely on manual review -- someone reads the PR, spots inconsistencies in tone, flags j...
Join discussion
