Markdown - writing articles on DataHub

Markdown is an easy-to-use markup language, used to format docs for web, using plain text.

It is used by DataHub, GitHub, Stackoverflow and many other sites.

General markdown guideline

General syntax when using markdown to format your text is popular


usual text usual text
*italic text* italic text
**bold text** bold text,
~~crossed though~~ crossed though
double space - linebreak

--- horizontal line like this:


Santa Claus said:

> Happy Christmas, hohoho

Santa Claus said:

Happy Christmas, hohoho


# this is a Header1
## Header2
###### Header6 - automatic
[Example]( Example - defined text
![alt text]( "image title") alt text


* task 1
* task 2
  * task 2a
  * task 2b
  • task 1
  • task 2
    • task 2a
    • task 2b

List with checkboxes:

* [x] unchecked
* [ ] checked
  • task 1
  • task 2


This is an inline code: `inline code`

This is an inline code: inline code

Multi-line code starts with triple backtick (also you can add the programming language name - ```[python|bash|php|etc]
print('hello world)

print('hello world')

and ends with triple backtick apostrophe as well.

DataHub specific features

As you can see, formatting text with Markdown is as easy as using notepad. Also, the markdown syntax could be extended easily, and here is the extra features, you can use to format pages for DataHub.


In the world of computer programming, frontmatter is metadata at the top of a file. Just put your metadata between two lines like this:

title: 5 minutes Markdown guide
date: 2017-12-21
authors: ['name']

And our site will use this metadata while forming the page. The result you can see on top of this page ('authors' is used in the blog posts).

Table of contents

Directive boxes (Callouts)

You can add info boxes in your text and the message will appear in a colored box:

>[!info]My important message here.

and this is how it would be rendered:

My important message here.

For more supported callouts please refer to

CLI output

Sometimes you might need to display how a CLI result, especially, if you're writing a tutorial about data wrangling. In such situation, you could use code blocks like below (use backticks instead of single quotes):

This is printed in the CLI

and this is how it would be rendered:

This is printed in the CLI

Articles on DataHub

There are 2 types of articles on the DataHub that you normally write: blog posts and docs.

A blog post

All blog posts are located in the frontend repository. To create a new one you'd a new .md file in the /blog/ directory. A file name should follow this pattern so that it is sorted correctly in the blog home page: Below is the check list of what else you need to remember when writing a blog post:

  • You have a frontmatter with published date (YYYY-MM-DD), title and authors (see above for more details about frontmatter).
  • You have a small introduction paragraph.
  • Check if a new post appears in the home /blog page.

After publication you may need to announce about the new post in our community gitter chat:

Documentation article

Documentation files are located in the repository and placed in the /docs/ directory. Feel free to create pull requests and our team will review it.