rules of steps

Author: elithrar

src/content/docs/workflows/build/dynamic-steps.mdx

@@ -6,12 +6,9 @@ sidebar:
 
 ---
 
-TODO
+A Workflow does not have to define all of its steps statically: steps can be created programmatically and/or conditionally.
 
-- Workflows don't have to have a fixed number of steps
-- Create them programatically, on the fly
-- Define names and parameters
-- Create steps in a loop or within a Promise
+This allows you to not only trigger steps based on specific input parameters, but to also name steps dynamically, set the retry configuration for a step 
 
 
 ## Example

src/content/docs/workflows/build/retrying.mdx

@@ -2,7 +2,7 @@
 title: Retrying
 pcx_content_type: concept
 sidebar:
-  order: 5
+  order: 4
 
 ---
 

src/content/docs/workflows/build/rules-of-steps.mdx

@@ -0,0 +1,26 @@
+---
+title: Rules of Steps
+pcx_content_type: concept
+sidebar:
+  order: 10
+
+---
+
+A Workflow step is self-contained, individually retriable component of a Workflow. Steps may emit (optional) state that allows a Workflow to persist and continue from that step, even if a Workflow fails due to a network or infrastructure issue. A Workflow is comprised of one or more steps.
+
+### Ensure API calls are idempotent
+
+TODO
+
+### Don't rely on state outside of a step
+
+TODO
+
+### Set sensible retry parameters
+
+TODO
+
+### Name your steps clearly
+
+TODO
+