"Use 1...n TASKS per workflow are allowed in each WDL file " -> this is ambiguous, I originally took it to mean you have to have at least one task declarations in a WDL file (not true, you can have zero task declarations if you import all your tasks from a separate WDL file); if you mean you must have one or more tasks in the workflow that should be stated more clearly (I'm not sure I've ever tested what happens wrt validation if you make a workflow with 0 tasks)
"Refactor long WDL files using imports" -> not sure I would frame imports as a refactoring thing at this level; would prefer to emphasize the ability to reference tasks and workflows up front.
"List the Workflow and task calls BEFORE the task descriptions" -> to be clear this is a style recommendation, not a requirement
"Add Comments - designated with ## (workflow) or # (task)" -> also not a requirement, I think this is just an artifact that some of us have introduced out of a preference; could enshrine this as a best practice but should be clear that it's not mandatory
Additional comments:
"Use 1...n TASKS per workflow are allowed in each WDL file " -> this is ambiguous, I originally took it to mean you have to have at least one task declarations in a WDL file (not true, you can have zero task declarations if you import all your tasks from a separate WDL file); if you mean you must have one or more tasks in the workflow that should be stated more clearly (I'm not sure I've ever tested what happens wrt validation if you make a workflow with 0 tasks)
"Refactor long WDL files using
imports" -> not sure I would frame imports as a refactoring thing at this level; would prefer to emphasize the ability to reference tasks and workflows up front."List the Workflow and task calls BEFORE the task descriptions" -> to be clear this is a style recommendation, not a requirement
"Add Comments - designated with
##(workflow) or#(task)" -> also not a requirement, I think this is just an artifact that some of us have introduced out of a preference; could enshrine this as a best practice but should be clear that it's not mandatory