Good news: You can now use Markdown syntax to format your deck descriptions!
For example, start a line with # to create a heading or surround text with two asterisks to make it
**bold**. You can also make sections that can be shown/hidden on click, which should come in particularly handy for primers.
In addition, I have also made a few more changes to make working with descriptions a bit easier:
- There is now a button to show a preview of your description before you save it.
- You will be warned if you try to leave your deck page without saving changes to your description.
- Descriptions and notes for previous revisions of your deck will be kept, and when you revert your deck they will also be restored.
Below are a few examples of our Markdown syntax. You can see the result of this code
in this example deck.
# Markdown example
The line above will become a heading because it is prefixed with a #.
## Introduction
Two ## make a sub-heading, ### make a sub-sub-heading and so on.
Leave an empty line to make a new paragraph. **This text will be shown in bold**, *while this will be in italics*.
You can also insert a link [like this](https://deckstats.net). Card names like Black Lotus or Forest will automatically be made clickable.
## > Hidden sections
If you start a section heading with a > after the # then it will be hidden by default, and can be revealed by clicking on the heading.
To end a section, just start another one at the same or higher level:
## Lists
Here is a list of a few items:
- item1
- item2
- item3
## Advanced syntax
Use three dashes to insert a horizontal rule:
---
You can even make tables:
First Header | Second Header
------------ | -------------
Content from cell 1 | Content from cell 2
Content in the first column | Content in the second column
To read more about Markdown, have a look at this
Markdown reference or
Github's guide to mastering Markdown. Note that Github has a few extra features that we don't support here though, like checklists, syntax highlighting and @mentions.
Markdown is only supported in deck descriptions and private notes. In the forums and in comments we will continue to use BBCode.
English
Deutsch
Español
Português
Italiano
Français