Task Stages
******************
* Start
* Build
* Render
* Review
* Publish

Preflights

For every production task each hook requires a ton of flexibility depending on myriad factors.  Preflights hooked to each hook in each task allow us to easily create custom hooks for every department in production.

For example, a Build preflight for animation might include importing published rigs for their shot, wheras a build preflight for look dev might include importing a model and textures.

Start
=====
This starts a task.  A typical "start" might include preflights like copying over a default file for that task. Some get more complex where they have to copy over the latest published file from some dependent task.

In Unreal Engine there's no need for a build task so the start task is where we do all the heavy lifting.

Build
=====
This is typically the fist step once you've opened a DCC.   You hit build and preflights handle importing all upstream dependencies and any other automated tasks that can set up your scene for you.

Render
======
Nearly every task in production has to produce images or movies.   The Render hook is where we attach preflights specific to rendering in each production task.


Review
======
One of the philosophical pillars of alchemy is that all reviews should be able to be submitted with 1 click.   The Review hook allows us to use preflights to handle all the rendering processing and uploading involved with submitting a review


Publish
=======
The publish is the hook that started everything in alchemy.  The idea with publishing and preflights was always to easily add tests to ensure artistic assets did not leave one production task in a way that would create bugs downstream.   The first iteration of the cookbook only had "publish" preflights, but as we expanded we realized that the 5 task hooks all needed preflights in order to scale, iterate and be flexibile with the needs of production.

Deliver
=======
The deliver hook is the final step in the production pipeline.  It's where we attach preflights to handle all the processing and uploading of final deliverables.  This is where we attach preflights to handle uploading to Shotgun, or uploading to a client's FTP server, or other cloud storage provider like Google Drive or Dropbox or the most stable/secure but also the hardest to set up - Amazon S3.