Plenty of lightweight markup languages exist, but only three are really worth discussing: Markdown, reStructuredText, and AsciiDoc.

Making proper use of links lets us attain a sort of Holy Grail in technical writing: single sourcing.

if things change—and things always change—you only have to update the documentation in one place.

Learn everything about a subject. Write down exactly what an audience needs to know and no more. Make the content beautiful, discoverable, scannable, and searchable. Consider everything a draft, and iterate relentlessly. Make contribution simple.

What does a simple, start to finish operation look like?

you should break your writing into bite-sized pieces, often called topics, none of which overlap in content.

the better approach is to use a feature sometimes called "conditional text." Conditional text lets you selectively include or exclude files (or portions of files) in the final output.

What topics should be is relatively complete in their discussion of a particular subject.

How does this product fit into a broader ecosystem, if at all? Does it have any dependencies?