List .wml files and directories containing .wml files, and WieldyJS will compile .html versions in the same location.

Use the -m or --mirror option and list an input directory and output directory, in that order. WieldyJS will find all .wml files in the input directory and compile them to .html files in the output directory.

Each line's Leading whitespace is used to detect it's nesting level. Use either tabs or spaces for indentation, but not both. The number of tabs or spaces that comprises an indentation is determined on the first line with any leading tabs or spaces, and then that is the standard used for the rest of the file.

For designating multiple, nested HTML tags on a single line in WieldyMarkup, use the \-\ delimiter between them. This is especially useful in a list of links. For example:

ul

li.active \-\ a href=# <Home>

li \-\ a href=# <Link>

li \-\ a href=#

i.icon-pencil

span <Link>

li \-\ a href=# \-\ span <Link>

becomes

<ul>

<liclass="active">

<ahref="#">Home</a>

</li>

<li>

<ahref="#">

<iclass="icon-pencil">

</i>

<span>Link</span>

</a>

</li>

<li>

<ahref="#">

<span>Link</span>

</a>

</li>

</ul>

Be careful nesting inside of an element after it is declared in a multi-tag line. You still have to indent to the proper level for following lines to be nested inside. Note the indentation of i.icon-pencil in the example above.

The list of attributes begins after the first whitespace character after the beginning of the selector. Key-value pairs are identified by three elements:

A key containing no whitespace characters or an equals sign (=)

An equals sign (=)

Either (1) a string starting with <% or {{ and ending with %> or }}, between which all characters are ignored, or (2) a string ending either at the innerText designation, the last whitespace character before the next =, or the end of the line

If the line ends with /, then the tag will be treated as self-closing.

If the line ends with innerText wrapped in < and >, or if the innerText spills over into proceeding lines and eventually ends with >, then everything between < and > will be designated as innerText for the HTML tag. The compiler will leave instances of <% [anything here] %>, as long as each instance is opened and closed on the same line; this restriction does not apply to {{ [anything here] }}. Leading whitespace for continuing lines of innerText is ignored and transformed into a single space.