describe passing of information as being like ‘ports’
Show to use RocketLauncher to run a particular fw_id (probably in the priorities tutorial) (note, this is already implemented, just needs documentation)
Tell people how to run different EXE based on machine, ie.. by changing bashrc and using an alias
Now that the “bird’s eye view” does a good job of explaining the features of FireWorks, remind users of these good attributes of the code within the other tutorials. e.g. point out how compact the spec is in the first quickstart tutorial.
Update all tutorials so config file is handled smoothly, not terribly...
Update all tutorials so that FireWorks have names, and lpad get_fws command uses the name of the FireWork rather than the id. Also talk about the metadata parameter of workflows
Update docs from the written FW docs notes in my blue folder...
Detailed tutorial on implementing dynamic jobs
Give examples on how to implement certain things, e.g. a workflow where one step gives an output file used as input by the second step.
Setting up logging (in deployment section of tutorials)
Provide a video showing how things look in production. That way people get a quick feel for what’s going to happen.
Put the bird’s eye view on the Home Page rather than as something you need to click.
Document the FWAction