# Frequently Asked Questions¶

This page covers some frequently-asked questions about the MyST markdown language, as well as the MyST parser for Sphinx. If you’re just getting started, see Getting Started.

## What is the relationship between MyST, reStructuredText, and Sphinx?¶

MyST markdown provides a markdown equivalent of the reStructuredText syntax, meaning that you can do anything in MyST that you can do with reStructuredText.

Sphinx has its own internal document model, and by default it knows how to convert reStructuredText into that document model (with an rST parser). The MyST markdown language defines markdown syntax that has all of the functionality that Sphinx provides (most notable, directives, roles, and labels). The MyST parser is a Sphinx extension that can parse this flavor of markdown into Sphinx’s internal document model. Once a document has been parsed into Sphinx, it behaves the same way regardless of whether it has been written in rST or MyST markdown.

myst markdown (.md) ------> myst parser ---+
|
+-->Sphinx document (docutils)
|
reStructuredText (.rst) --> rst parser ----+


For example, here’s how you’d write a toctree directive in MyST markdown:

{toctree}
My page name <page1>
page2



and here’s the same in rST:

.. toctree::

My page name <page1>
page2


They will both behave the same in Sphinx.

## What markup language should I use inside directives?¶

If you need to parse content inside of another block of content (for example, the content inside a note directive), note that the MyST parser will be used for this nested parsing as well.

## How fast is the myst-parser?¶

MyST-Parser uses the fastest, CommonMark compliant, parser written in Python!