Markdown

    Here “inline” refers to elements that can be found within blocks of text, i.e. paragraphs. These include the following elements.

    Surround words with two asterisks, , to display the enclosed text in boldface.

    Italics

    Surround words with one asterisk, *, to display the enclosed text in italics.

    1. A paragraph containing an *emphasized* word.

    Literals

    Surround text that should be displayed exactly as written with single backticks, ` .

    1. A paragraph containing a `literal` word.

    Literals should be used when writing text that refers to names of variables, functions, or other parts of a Julia program.

    Tip

    To include a backtick character within literal text use three backticks rather than one to enclose the text.

    1. A paragraph containing a ``` `backtick` character ```.

    By extension any odd number of backticks may be used to enclose a lesser number of backticks.

    $\LaTeX$

    Surround text that should be displayed as mathematics using $\LaTeX$ syntax with double backticks, `` .

    1. A paragraph containing some ``\LaTeX`` markup.

    Tip

    As with literals in the previous section, if literal backticks need to be written within double backticks use an even number greater than two. Note that if a single literal backtick needs to be included within $\LaTeX$ markup then two enclosing backticks is sufficient.

    Note

    The \ character should be escaped appropriately if the text is embedded in a Julia source code, for example, "``\\LaTeX`` syntax in a docstring.", since it is interpreted as a string literal. Alternatively, in order to avoid escaping, it is possible to use the raw string macro together with the @doc macro:

    1. @doc raw"``\LaTeX`` syntax in a docstring." functionname

    Links to either external or internal addresses can be written using the following syntax, where the text enclosed in square brackets, [ ], is the name of the link and the text enclosed in parentheses, ( ), is the URL.

    1. A paragraph containing a link to [Julia](http://www.julialang.org).

    It’s also possible to add cross-references to other documented functions/methods/variables within the Julia documentation itself. For example:

    1. """
    2.     tryparse(type, str; base)
    4. Like [`parse`](@ref), but returns either a value of the requested type,
    5. or [`nothing`](@ref) if the string does not contain a valid number.
    6. """

    This will create a link in the generated docs to the documentation (which has more information about what this function actually does), and to the nothing documentation. It’s good to include cross references to mutating/non-mutating versions of a function, or to highlight a difference between two similar-seeming functions.

    Note

    Footnote references

    Named and numbered footnote references can be written using the following syntax. A footnote name must be a single alphanumeric word containing no punctuation.

    Note

    The text associated with a footnote can be written anywhere within the same page as the footnote reference. The syntax used to define the footnote text is discussed in the section below.

    The following elements can be written either at the “toplevel” of a document or within another “toplevel” element.

    Paragraphs

    A paragraph is a block of plain text, possibly containing any number of inline elements defined in the Inline elements section above, with one or more blank lines above and below it.

    1. This is a paragraph.
    3. And this is *another* one containing some emphasized text.
    4. A new line, but still part of the same paragraph.

    Headers

    A document can be split up into different sections using headers. Headers use the following syntax:

    1. # Level One
    2. ## Level Two
    3. ### Level Three
    4. #### Level Four
    5. ##### Level Five
    6. ###### Level Six

    A header line can contain any inline syntax in the same way as a paragraph can.

    Tip

    Try to avoid using too many levels of header within a single document. A heavily nested document may be indicative of a need to restructure it or split it into several pages covering separate topics.

    Source code can be displayed as a literal block using an indent of four spaces as shown in the following example.

    1. This is a paragraph.
    3.     function func(x)
    4.     end
    6. Another paragraph.

    Additionally, code blocks can be enclosed using triple backticks with an optional “language” to specify how a block of code should be highlighted.

    1. A code block without a "language":
    3. ```
    4. function func(x)
    5.     # ...
    6. end
    7. ```
    11. ```julia
    12. function func(x)
    13.     # ...
    14. end
    15. ```

    Note

    “Fenced” code blocks, as shown in the last example, should be preferred over indented code blocks since there is no way to specify what language an indented code block is written in.

    Block quotes

    Text from external sources, such as quotations from books or websites, can be quoted using > characters prepended to each line of the quote as follows.

    1. Here's a quote:
    3. > Julia is a high-level, high-performance dynamic programming language for
    4. > technical computing, with syntax that is familiar to users of other
    5. > technical computing environments.

    Note that a single space must appear after the > character on each line. Quoted blocks may themselves contain other toplevel or inline elements.

    Images

    The syntax for images is similar to the link syntax mentioned above. Prepending a ! character to a link will display an image from the specified URL rather than a link to it.

    1. ![alternative text](link/to/image.png)

    Lists

    Unordered lists can be written by prepending each item in a list with either *, +, or -.

    1. A list of items:
    3.   * item one
    4.   * item two
    5.   * item three

    Lists can contain other nested toplevel elements such as lists, code blocks, or quoteblocks. A blank line should be left between each list item when including any toplevel elements within a list.

    1. f(x) = x
    2. ```

    • And a sublist:

      • sub-item one
      • sub-item two ```

    Note

    The contents of each item in the list must line up with the first line of the item. In the above example the fenced code block must be indented by four spaces to align with the i in item two.

    Ordered lists are written by replacing the “bullet” character, either *, +, or -, with a positive integer followed by either . or ).

    1. Two ordered lists:
    3.  1. item one
    4.  2. item two
    5.  3. item three
    7.  5) item five
    8.  6) item six

    An ordered list may start from a number other than one, as in the second list of the above example, where it is numbered from five. As with unordered lists, ordered lists can contain nested toplevel elements.

    Large $\LaTeX$ equations that do not fit inline within a paragraph may be written as display equations using a fenced code block with the “language” math as in the example below.

    1. ```math
    2. f(a) = \frac{1}{2\pi}\int_{0}^{2\pi} (\alpha+R\cos(\theta))d\theta
    3. ```

    Footnotes

    This syntax is paired with the inline syntax for . Make sure to read that section as well.

    Footnote text is defined using the following syntax, which is similar to footnote reference syntax, aside from the : character that is appended to the footnote label.

    1. [^1]: Numbered footnote text.
    3. [^note]:
    5.     Named footnote text containing several toplevel elements.
    7.       * item one
    8.       * item two
    9.       * item three
    11.     ```julia
    12.     function func(x)
    13.         # ...
    14.     end
    2. Note
    4. No checks are done during parsing to make sure that all footnote references have matching footnotes.
    6. ### Horizontal rules
    8. The equivalent of an `<hr>` HTML tag can be written using the following syntax:

    Text above the line.

    And text below the line.

    2. ### Tables
    4. Basic tables can be written using the syntax described below. Note that markdown tables have limited features and cannot contain nested toplevel elements unlike other elements discussed above – only inline elements are allowed. Tables must always contain a header row with column names. Cells cannot span multiple rows or columns of the table.
    2. Note
    4. As illustrated in the above example each column of `|` characters must be aligned vertically.
    6. A `:` character on either end of a column's header separator (the row containing `-` characters) specifies whether the row is left-aligned, right-aligned, or (when `:` appears on both ends) center-aligned. Providing no `:` characters will default to right-aligning the column.
    8. ### Admonitions
    10. Specially formatted blocks, known as admonitions, can be used to highlight particular remarks. They can be defined using the following `!!!` syntax:

    !!! note

    !!! warning “Beware!”

    1. And this is another one.
    3. This warning admonition has a custom title: `"Beware!"`.

    ```

    The type of the admonition can be any word, but some types produce special styling, namely (in order of decreasing severity): danger, warning, info/note, and tip.

    A custom title for the box can be provided as a string (in double quotes) after the admonition type. If no title text is specified after the admonition type, then the title used will be the type of the block, i.e. "Note" in the case of the note admonition.

    Admonitions, like most other toplevel elements, can contain other toplevel elements.

    In principle, the Markdown parser itself can also be arbitrarily extended by packages, or an entirely custom flavour of Markdown can be used, but this should generally be unnecessary.