Skip to content

DigitalBits Documentation and API Reference (Fork).

Notifications You must be signed in to change notification settings

bajetech/digitalbits-docs

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

65 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

DigitalBits Docs

This repository is home to the DigitalBits documentation. These docs feed into the DigitalBits developers site builder and is on display at developers.digitalbits.io.

How to write docs

There are a few conventions when writing docs that go into the DigitalBits Developers site. Most the docs are written in markdown format. For an introduction of what Markdown is, take a look at Github's Mastering Markdown Guide.

Headers

Lines that start with a hash tag (#) are considered headers. Below is an example of a few and the name of the header:

# h1
## h2
### h3
#### h4
  • DO NOT use h1 since that is reserved for the page title generated from front matter.
  • DO NOT skip a header size (don't go from h2 to h4).
  • DO use smaller headers (more hash tags) to represent that a section is nested under a parent one with a larger header.
  • DO add a space after the hash tags. Some markdown parsers will not render the text as a header without the space.

Front matter

At the top of most documents are something called "front matter". This is metadata for the file written in YAML format.

Here is an example of front matter in action:

---
title: Frontier Reference
---

The currently used keys in the front matter are:

  • title

Document title

Do not start a page with a markdown header (# Title). Instead, leave it in the front matter. The developers site will take the title from the front matter.

Links

Use inline links and not reference links.

There are three different kind of links, and each different kind of link has a significant meaning. Some of these links are transformed in the generation of the developers site.

link type where to use markdown link example resulting link (after dev portal processing)
Relative
  • links within same repository
../reference/accounts-all.md ../reference/accounts-all.html
Root relative
  • when you want to use the github file viewer (like for source files)
/src/ledger/AccountFrame.cpp https://github.com/xdbfoundation/CURRENT-REPOSITORY/tree/master/src
Absolute links https://www.digitalbits.io/developers/xdb-digitalbits-base/learn/building-transactions.html https://www.digitalbits.io/developers/xdb-digitalbits-base/learn/building-transactions.html

Non-markdown files

Sometimes we want to include other types of content such as .pdf's. To add front matter to the pdf, create a sibling file with the pdf file name and an added extension of .metadata. This file can then define metadata for the title of the .pdf.

An example can be seen in digitalbits-core's software folder.

Contributing

Your contributions to the DigitalBits network are greatly appreciated.

We want to make it as easy as possible to contribute changes that help the DigitalBits network grow and thrive. There are a few guidelines that we ask contributors to follow so that we can merge your changes quickly. Please read our Contribution Guide and sign our Contributor License Agreement.

About

DigitalBits Documentation and API Reference (Fork).

Resources

Stars

Watchers

Forks