Pantheon documentation is written using Markdown syntax.
However, we use two flavors of this syntax:
- One for pages inside the /docs directory that will be rendered by MkDocs as described below in the Installed Markdown Extensions section.
- Another using the Github syntax for pages outside of this documentation directory. These are mainly files to support our open source community.
The Pantheon documentation website is maintained by PegaSys from the content of the /docs directory.
The /docs directory in the Pantheon repository contains all the documentation that is generated into a static HTML website using MkDocs and the Mkdocs Material theme and hosted by readthedocs.org.
The documentation is automatically updated using WebHooks linking GitHub to the readthedocs.org site when you merge a pull-request in the master branch of Pantheon.
The system also detects tags in the Github repository and takes care of making the latest stable release and previous versions available.
If any issues occur, contact the maintainers of the Pantheon documentation project.
MkDocs is a Python tool that generates the static HTML website that is published.
Our MkDocs setup uses a Mkdocs Material theme to render the html pages. It also comes with a number of useful extensions.
MkDocs in configured in the mdkocs.yml file.
This file configures:
- Site meta data and variables
- Theme configuration
- Page navigation
- Extensions
- Plugins
If you add pages to the documentation (rather than updating existing pages), update the "nav" section to add your page and specify the page name.
We recommended previewing your work locally before pushing your changes within a pull-request. As the final documentation is build with MkDocs, you have to build your docs locally with this tool to ensure the Markdown is correctly understood and displayed.
To preview Pantheon documentation locally:
- Install Python
- Install PIP
- Install all the required dependencies :
pip install -r docs/requirements.txt
- Run the following command in the project directory :
mkdocs serve
- Follow the link displayed on the output of this command that
looks like
[I 190206 18:48:47 server:298] Serving on http://127.0.0.1:8000, here connect to [http://127.0.0.1:8000]
You can let this doc server run while you work on the doc, it updates the local website automatically when you save changes in your Markdown files.
Final documentation rendering is essential, but the format of the Markdown files is also very important.
Formatting the Markdown code helps reviewers and writers easily navigate in the code and review your changes.
A few basic rules:
- Each file must contain a header composed of meta-data
and ended by a specific comment.
Ex:
title: Installation overview description: Overview and requirements to install Pantheon <!--- END of page meta data --> - As for other code, each line of Markdown code must be limited to 100 columns long to be readable on any editor. Lines have to be wrapped without cutting the line in the middle of a word. A line break displays as a space.
- No HTML markup can be used inside a Markdown document. We provide a lot of extensions that are able to do the same thing without HTML. If you think one is missing, just discuss it with the team on Gitter and we'll decide together if it's worth adding an extension.
- Only one first level title can be present on a page.
- Format tables so they are also readable in the source code. You can quickly achieve this by using a tool like http://markdowntable.com/
Important Extensions are only available for the docs under /docs directory.
As markdown can be a bit limited when it comes to some specific rendering of code, TOCs, and other documentation elements, we configured some extensions for these items. Extensions enable you to use simple Markdown syntax to achieve some complex rendering.
Important Never use HTML tags directly in the Markdown files to try to render content. For consistency reasons we only allow the specific renderings available in the extensions.
Here is a list of the available extensions:
This extension automatically displays a table of content of the current page on the right side of the page.
It displays titles to the third level (###). After the third level, titles won't be displayed in the TOC.
This extension also displays a link on the right of any title called "permalink". This link can be used to point directly to the title from another website.
If you have content to be repeated on multiple pages, you can create it in a common page in and include it in all required pages.
Example: To include the content of the "test_accounts.md" page in the "/docs/global" directory in another page, use:
{!global/test_accounts.md!}The Admonition extension enables information, warning, and danger blocks.
Example:
!!! note
This is a multi line note
in the Pantheon documentation. The 4 spaces indentation is required for the content to be part of the admonition.
We generally use the following types in our documentation:
- Note : Used to add information about a subject that doesn't directly needs to be taken in account to use this specific part. Example: "Available since v0.8.3"
- Abstract : Used at the beginning of a long article. Also known as "TL;DR", this can help users jump into the content knowing that they will find their answer somewhere in the page.
- Info : Used to provide detail about a specific part of the documentation. Ex: "The miner coinbase account is one of the accounts defined in the genesis file."
- Tip : Used to provide information that could help improve the use of the tool, make it faster. Example: "To restart the private network in the future, start from 4. Restart First Node as Bootnode."
- Warning : Used to warn the users about something important. Ex: "This will be deprecated in next version."
- Danger : Used to alert the user about a potential dangerous effect such as a risk of destroying something or losing assets. Ex: "Never use the development private keys for production use".
- Example : used to display an example. We usually use it with a single or tabbed code-block:
!!! example
This example shows how to use the `net_listening` RPC method.
```bash tab="curl HTTP request"
$ curl -X POST --data '{"jsonrpc":"2.0","method":"net_listening","params":[],"id":53}' <JSON-RPC-http-endpoint:port>
```
```bash tab="wscat WS request"
{"jsonrpc":"2.0","method":"net_listening","params":[],"id":53}
```
```json tab="JSON result"
{
"jsonrpc" : "2.0",
"id" : 53,
"result" : true
}
```The Footnotes extension enables adding footnotes.
Footnotes display content at the end of the page and a numbered link inside the text to go to this content. The extension also adds a link at the end of the footnote back to the text.
The def_list extension enables listing definitions directly in the Markdown.
Generally we avoid the use of abbreviations but some like "PoW" for proof-of-work or "dApp" for decentralized application are now part of the Ethereum jargon. The Abbreviation extension enables a tool tip hint to be provided for abbreviations.
Place abbreviations at the beginning of the Markdown file just after the meta-data header.
Example:
description: This is an example page
<!--- END of page meta data -->
*[PoA]: Proof of Work
Clique is a PoA mechanism used in the Rinkeby test networkArithmatex extension enables writing math formulas in the documentation using the provided syntax.
Example:
$\sigma=\displaystyle\prod_{k=1}^t\sigma_{i_k}^{L_{i_k}(0)}$
Constructing the threshold signature $\sigma$ from $t$ individual
signatures $\sigma_{i_k}$, $k=1,\dots,t$ and the Lagrange polynomials
$L_{i_1}, \dots,L_{i_t}$ associated to the set $I=\{i_1,\dots,i_t\}$ of signers.The Betterem extension is automatically applied to your bold and italic content.
The Keys syntax extension enables displaying keyboard shortcuts.
Example:
++ctrl+C++You can use a folding block to hide content. The block can be closed by default or open. This pattern helps reduce the content length and enables a faster overview of the whole page.
Ex:
???+ note "Folding details"
This is the detail of my content.
The plus sign makes it unfolded by default.
Remove the plus sign and it will be folded by default.Emojis are fun, but they can also be useful to draw the reader's attention.
Try to use only neutral emojis like
Refer to a supported full list of available emojis to find the suitable code.
Example:
:warning: displays
If you want an URL to be displayed as a link, simply write it and this extension automatically displays it as a link. You don't need to surround it with Markdown links syntax.
The Mark extension enables highlighting of content.
Text surrounded by double equals is highlighted in yellow.
Example:
==This is highlighted text==The tilde syntax extensions enables text strike through to be displayed.
Example:
~~This is the wrong way to do~~The Smart symbols syntax enables the inclusion of symbols.
Ex:
--> will draw a nice right arrow.
The Task list syntax extension enables displaying a list as a checklist.
Code Samples And Examples With SuperFences
For writing code examples inside the documentation, refer to the developer style guides:
- Java : refer to our coding convention.
- JSON : use https://jsonformatter.curiousconcept.com/ to format your JSON code.
- TOML : we follow version 0.5.0 language definition.
- JavaScript : see Google JavaScript Style Guide.
We use code-blocks provided by the SuperFences extension to present code samples and examples in the documentation.
A basic code-block uses triple back ticks and the language name to enable syntax highlighting.
For example, a JSON result is written as:
```json
{
"jsonrpc": "2.0",
"id": 1,
"result": true
}
```SuperFences enables additional functionality such as the tabbed code-block.
For example, to group the usage syntax and a usage example in the same block with tabs:
```bash tab="Syntax"
$ pantheon rlp encode [--from=<FILE>] [--to=<FILE>] [--type=<type>]
```
```bash tab="File Example"
$ pantheon rlp encode --from=ibft_extra_data.json --to=extra_data_for_ibft_genesis.txt --type=IBFT_EXTRA_DATA
```
```bash tab="Standart Input/Output Example"
$ cat extra_data.json | pantheon rlp encode > rlp.txt
```SuperFences can also add line numbers to the code sample which makes it easier when discussing the code the sample.
The line numbers will only appear on the code block that uses the linenums="1" parameter.
Example:
```javascript linenums="1"
// A very long javascript sample code
```Codehilite extension enables automatic syntax highlighting of code blocks. Define the language after the code block delimiter to ensure correct highlighting. If you don't provide the language name, the extension attempts to automatically discover it but this can lead to errors.
Example:
```json
{
"jsonrpc" : "2.0",
"id" : 51,
"result" : {
"startingBlock" : "0x5a0",
"currentBlock" : "0xad9",
"highestBlock" : "0xad9"
}
}
```Pygment is the implementation for this extension, refer to Pygment website for a list of the supported languages.