This example implementation of templates and request chaining aims to work within our current system of templates and extensions. 2 new types of files are introduced to our templating system to improve our current templates. First, the definitions file, which will cut down on the clutter and ugliness of our templates. Second, the sequence file, which will allow us to support request chaining. For example purposes, these files will be JSON files, but because writing JSON files by hand is tedious, these could be YAML or some other format, if we want.
A definition file is a file that essentially outsources most of the markup in our templates, which contributes to their clutter, to a seperate file altogether. This allows us to greatly clean up our template files. External calls will be the primary thing that these definition files support, but they can also be used to markup our templates without actually having to clutter up our templates. For example, if we wanted, type restriction