explaingit

race2infinity/the-documentation-compendium

5,962Audience · developerComplexity · 1/5LicenseSetup · easy

TLDR

A collection of copy-paste templates and plain-English writing advice for README files, changelogs, contributing guides, and other standard open-source docs.

Mindmap

mindmap
  root((Documentation Compendium))
    Templates
      README
      Pull request
      Issue reports
      Contributing guide
      Changelog
    Writing advice
      Friendly tone
      Short explanations
      Show examples
      Avoid jargon
    External links
      Write the Docs
      Google style guide
      Season of Docs
    License
      CC0 public domain
      No attribution needed
Click or tap to explore — scroll the page freely

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Things people build with this

USE CASE 1

Copy a ready-made README template into your project and fill in the blanks instead of starting from scratch.

USE CASE 2

Use the contributing guide template to set clear expectations for people who want to submit pull requests.

USE CASE 3

Apply the writing advice to improve tone and clarity in existing documentation, shorter sentences, more examples, less jargon.

USE CASE 4

Browse linked resources from Write the Docs and Google to learn professional technical writing practices.

Getting it running

Difficulty · easy Time to first run · 5min
Placed in the public domain under CC0, use any template for any purpose with no attribution required.

In plain English

The Documentation Compendium is a collection of ready-to-use templates and written advice for anyone who wants to write better documentation for a software project. The repository does not contain code. Instead, it contains Markdown files you can copy into your own projects as starting points for things like README files, pull request descriptions, issue report formats, contributing guides, changelogs, and codes of conduct. Alongside the templates, the repository includes a section on best practices for writing documentation. The advice covers tone (keep it friendly and assume the reader is new to the topic), structure (use headings often, keep explanations short, show examples rather than just describing things), and a list of things to avoid (idioms, assumed prior knowledge, and terms that exclude any group of readers). There is also a short case for why documentation matters at all, pointing out that even useful software goes unused when it is hard to understand. The repository links out to external resources on technical writing, including guides from the Write the Docs community, Google's developer documentation style guide, and several blog posts from working technical writers. There are also pointers to formal programs like Google Season of Docs for anyone who wants to contribute documentation to open-source projects as a volunteer. The templates are organized in an English subfolder and cover most of the standard files you would find in a well-maintained open-source project. The project itself is released under the CC0 license, which places the contents in the public domain, so you can use any template without attribution.

Copy-paste prompts

Prompt 1
Using the Documentation Compendium README template, help me fill in the sections for my Python CLI tool that converts CSV files to JSON.
Prompt 2
Adapt the Documentation Compendium contributing guide template for a small open-source project with 2 maintainers and monthly releases.
Prompt 3
Review my existing README against the Documentation Compendium best practices and suggest specific improvements to tone and structure.
Prompt 4
Help me write a changelog entry following best practices for a release that adds two new features and fixes one bug.
Open on GitHub → Explain another repo

← race2infinity on gitmyhub — every repo by this author, as a profile.

Verify against the repo before relying on details.