ClickHelp.com
ClickHelp.com @ClickHelpNews ·
Docs as Code works great—until documentation starts scaling beyond developer-owned READMEs. In this article we explore where Docs as Code reaches its limits and how hybrid documentation platforms address those gaps. Read here → tinyurl.com/599ac3x3 #Documentation #DocsAsCode
6
47
Daisy Faith Auma 🇰🇪🇬🇧
Daisy Faith Auma 🇰🇪🇬🇧 @daisyfaithauma ·
Week 5 Articles Medium friend link: medium.com/@daisyfaithaum… Medium: medium.com/@daisyfaithaum… Substack : open.substack.com/pub/daisyfaith… Dev.to : dev.to/daisyauma/how-… #TechnicalWriting #DocsAsCode
Daisy Faith Auma 🇰🇪🇬🇧 Daisy Faith Auma 🇰🇪🇬🇧 @daisyfaithauma ·
Different customers needed different documentation. The obvious solution? Multiple doc sites. The obvious solution? A maintenance nightmare. Here’s how I used Mintlify’s group-based access control to serve multiple audiences from one doc site 👇 �medium.com/@daisyfaithaum…KQ #TechnicalWriting #DocsAsCode
Medium
How I Built Customer-Specific Documentation in Mintlify

A practical guide to serving different audiences without maintaining multiple doc sites

From medium.com
1
69
Fern
Fern @buildwithfern ·
Introducing the Fern Editor: Edit your docs in the browser. Feels like Notion, powered by Git. link.buildwithfern.com/GoF5ed0 ✨ Notion-like visual editing for anyone ⚙️ Dev Mode for Markdown control 🔄 Automatic draft PRs via Git (no GitHub account needed) #DevTools #DocsAsCode
Introducing the Fern Editor - Edit Developer Docs in the Browser, Powered by Git | Fern

The Fern Editor makes writing developer documentation accessible to everyone. Non-technical teammates can edit docs in the browser while developers keep Git-backed workflows for review and version...

From buildwithfern.com
142