Your Technical Documentation Should Be a Graph: Here’s Why
By Bryce Merkl Sasaki
April 25, 2016 4 mins read
TL;DR: This blog post is mainly about how technical documentation should ideally be structured: as a graph (not to be confused with a chart). As a software developer and author I have had the chance (and also the obligation) to… Read more →
Explore: github • graph • graphconnect • Knowledge Graph • natural language processing • nlp • software developer • stack overflow • Structr • technical documentation
