DescribeCompiler templating

The describe compiler is templateable - you can provide your own output templates (aka stencils) that contain "sockets" - the text in curly brackets, and the data from the parsed lists will replace those "socket" placeholder text. You can put any text in those output templates. Here is how it works.

If using version 0.9.1 or higher, there must be a folder named "Templates" next to your exe and/or dll. This folder will contain other folders - currently only one other folder, named "HTML_PARACORD". Those are the available templates, again, currently only the one, and the names on the folders are the names of the templates (We currently only have the "HTML_PARACORD" template. You can create your own here, for example by copy/pasting an existing one and modifying it. When you run the DesscribeCompilerCLI or the dll, you can use the option template=YOUR_TEMPLATE_NAME_HERE to use your template. You must name your template with a unique name that does not contain spaces, and you must have all the files, named the same as described in the list below, and containing all those placeholders, as described in the list below. File extensions does not matter, so you can have Root.html or Root.json or just Root, but not root.html or _Root.json or Root.html.json. (Look at the default "HTML_PARACORD" template and this text will become much more obvious)

Last but not least, if you don't have said "Templates" folder, you can use the DescribeCompilerCLI ext command to output it from the utility. (You can also use the same command to reset said folder, as it will overwrite the default templates).

Also, if you do not choose to use another template, "HTML_PARACORD" will be used by default.

You could also implement your own translator class if needed, but this is another topic. Below is template data for the default translator:

• "Root" must have the socket {ITEMS}
• "Production" must have the sockets {TITLE} and {ITEMS}
• "ProductionColored" must have the sockets {TITLE},{ITEMS} and {COLOR}
• "Page" must have the socket {DATA}
• "Item" must have the socket {TEXT}
• "ItemColored" must have the sockets {TEXT} and {COLOR}
• "ItemComment" must have the sockets {TEXT}
• "ItemEmpty" need not have socket(s)
• "Link" must have the sockets {TEXT} and {HTTPS}