powered by
LOGO

Learn X In Y Minutes, where X=FTD

FTD is created with the goal to make programming accessible to more people. {ds.highlight: FTD compiles to HTML/CSS/JS and is used to create web pages}. FTD is designed with authoring web content in mind, it can be seen as markdown with data types, event handling, APIs integrations etc.

Comments
Single line comments start with ;;.

\ this is a single line comment
Mutliline comments are not yet implemented, but this is how it would look (details: RFC 480):
{-:

A multiline comment.

:-}

Sections
FTD files are composed of “sections”, a section looks like this:

-- name-of-section: optional "caption of a section"
optional: key-value-pairs
we-call-them: headers

optional "body" of the section. a section ends at the end of a file
or when the next section starts.

some sections also have an end marker:

-- end: name-of-section
Sections start with -- . The space after -- is optional, but we are strict so we may make it mandatory.
LOGO

Learn X In Y Minutes, where X=FTD

FTD is created with the goal to make programming accessible to more people. {ds.highlight: FTD compiles to HTML/CSS/JS and is used to create web pages}. FTD is designed with authoring web content in mind, it can be seen as markdown with data types, event handling, APIs integrations etc.

Comments
Single line comments start with ;;.

\ this is a single line comment
Mutliline comments are not yet implemented, but this is how it would look (details: RFC 480):
{-:

A multiline comment.

:-}

Sections
FTD files are composed of “sections”, a section looks like this:

-- name-of-section: optional "caption of a section"
optional: key-value-pairs
we-call-them: headers

optional "body" of the section. a section ends at the end of a file
or when the next section starts.

some sections also have an end marker:

-- end: name-of-section
Sections start with -- . The space after -- is optional, but we are strict so we may make it mandatory.