Terminology

This documentation is written for the most recent release of Chasse (Ballet: v1.0.0).

Here is the minimal terminology that is used across the entire utility. These terms also recur in the other sections of
the documentation.

• Resultant (or Generated) HTML Files: The files that get produced after the chasse command is run. These files are only
  for use by the browser and (conventionally) not meant to be developed on.
• Components: Blocks of reusable (or overly bulky & messy) HTML code. Sometimes we may also define components that
  are not reusable but are too bulky to put into the child Chasse files (see below).
• Chasse Files: These files are where we write development code, create and inherit components, etc. They have a mandatory
  extension of .chasse.html.
• Parent Chasse (or Parent) Files: These files are where we define components. These files are never directly converted into
  Resultant HTML files. Their components are inherited by the Child Files.
• Child Chasse (or Child) Files: These files are the ones that get directly converted into Resultant HTML files. They inherit
  and use components defined in the parent Chasse files.
• Parent Declaration: The act of specifying, at the start of the child file, the parents that would be inherited from.
• Component Inheritance: The act of the child files inheriting components from the parent files.
• Lean Development: The act of defining components that are not reusable, but are too bulky to be put into the
  development files. This may be done in order to keep the child files tidy and shift load to parents.
• Optionals: Arguments that are optional to execute the command.
• Positionals: Positional arguments that are compulsory to execute the command.

The next section deals with basic use-cases of using the utility to its full potential.