Documentation Style Guide

Where are the docs?

TL;DR version: docs is the marketing website. documentation is the website. (Yes, the names are backwards!)
The two websites
  1. 1.
    • The main website
    • Source code: docs
    • Mostly "marketing" for the project.
    • Rarely changes. Updated via GitHub "pages" feature.
  2. 2.
    • Project documentation
    • Source code: documentation
    • Users and developer documentation
    • Changes frequently. Updated via GitBook
The directory structure
Within the git repo, docs are grouped:

How to add a new page?

  1. 1.
    Add the page to the documentation folder (possibly a sub folder)
  2. 2.
    List the page in so that it will appear in the table of contents, sidebar, etc.

Top-of-Document parameters

Files in the documentation/functions/{record,domain,global} subdirectories have a header at the top that is used to populate other systems.
Here's an example from A
name: A
provider: NAMEDOTCOM
- name
- address
- modifiers...
name: string
address: string | number
"modifiers...": RecordModifier[]
  • name: The name of the function/constant in the document. This should match the filename (aside from the .md suffix).
  • parameters: These are the names of the parameters that the function accepts. modifiers... indicates that a variable number of modifiers can be added.
  • parameter_types: The typescript type for each parameter. This is used when generating types-dnscontrol.d.ts
  • provider: If a feature is only available for one provider

Documentation previews

"Preview links are only accessible by GitBook users. We're working on a feature that will allow preview links to be viewable by anyone who accesses the PR." — GitBook

Formatting tips


Break lines every 80 chars.
Include a blank line between paragraphs.
Leave one blank line before and after a heading.
JavaScript code should use double quotes (") for strings, not single quotes ('). They are equivalent but consistency is good.


# Title of the page
## Heading
At least one paragraph.
## Subheadings
At least one paragraph.
* **Step 1: Foo**
Description of the step.
* **Step 2: Bar**
Description of the step.
(further sub sub headings are discouraged encouraged)

Code Snippets

See the examples below, for the Markdown syntax click on the 'Source code'.
Long example: (with filename)
var REG_NONE = NewRegistrar("none");
var DNS_BIND = NewDnsProvider("bind");
D("", REG_NONE, DnsProvider(DNS_BIND),
A("@", "")
Long example: (without filename)
var REG_NONE = NewRegistrar("none");
var DNS_BIND = NewDnsProvider("bind");
D("", REG_NONE, DnsProvider(DNS_BIND),
A("@", "")


Hints are a great way to bring the reader's attention to specific elements in your documentation.
There are 4 different types of hints, and both inline content and formatting are supported.

Example of a hint

Info hints are great for showing general information, or providing tips and tricks.
Success hints are good for showing positive actions or achievements.
Warning hints are good for showing important information or non-critical warnings.
Danger hints are good for highlighting destructive actions or raising attention to critical information.

This is a heading

This is a line
This is a second line

Technical references

Mentioning language features

Not every mention to A, CNAME, or function needs to be a link to the manual for that record type. However, the first mention on a page should always be a link. Others are at the authors digression.
The [`PTR`](functions/domain/ feature is helpful in LANs.

Mentioning functions from the Source code

The function `GetRegistrarCorrections()` returns...
Blah blah blah [M365_BUILDER](functions/record/
NOTE: The .md is required.
Just list the URL.
Blah blah blah <> blah blah.
Blah blah blah [a search engine]( blah blah.


Please spellcheck documents before submitting a PR.
Don't be surprised if Tom rewrites your text. He often does that to keep the documentation consistent and make it more approachable by new users. It's not because he has a big ego. Well, not usually.