docs: update guide sidebars

Author: jahvon

docs/_sidebar.md

@@ -4,13 +4,13 @@
 
 - User guides
 
-    - [Customizing the TUI](guide/interactive.md "Customizing the interactive UI")
     - [Secrets vault](guide/secret.md "Using the secrets vault")
     - [Workspaces](guide/workspace.md "Managing workspaces")
     - [Executables](guide/executable.md "Managing executables")
     - [Templating](guide/templating.md "Using flowfile templates")
     - [Managing state](guide/state.md "Managing executable state")
     - [Conditional execution](guide/conditional.md "Conditional execution")
+    - [Customizing the TUI](guide/interactive.md "Customizing the interactive UI")
 
 - Reference
 

docs/guide/_sidebar.md

@@ -3,11 +3,11 @@
 - [Quick start](../quickstart.md "Quick start guide")
 
 - User guides
-    - [Customizing the TUI](interactive.md "Customizing the interactive UI")
     - [Secrets vault](secret.md "Using the secrets vault")
     - [Workspaces](workspace.md "Managing workspaces")
     - [Executables](executable.md "Managing executables")
     - [Templating](templating.md "Using flowfile templates")
-    - [Managing state](guide/state.md "Managing executable state")
-    - [Conditional execution](guide/conditional.md "Conditional execution")
+    - [Managing state](state.md "Managing executable state")
+    - [Conditional execution](conditional.md "Conditional execution")
+    - [Customizing the TUI](interactive.md "Customizing the interactive UI")
 

docs/guide/conditional.md

@@ -1,17 +1,17 @@
-# Conditional Expressions
+## Conditional Expressions
 
 flow CLI uses conditional expressions to control [executable](executable.md) behavior based on runtime conditions. These expressions are written
 using a simple expression language that provides access to system information, environment variables, and stored data.
 
-## Expression Language
+### Expression Language
 
 Flow uses the [Expr](https://expr-lang.org) language for evaluating conditions. The language supports common
 operators and functions while providing access to flow executable-specific context data.
 
 **See the [Expr language documentation](https://expr-lang.org/docs/language-definition) for more information on the
 expression syntax.**
 
-### Basic Operators
+#### Basic Operators
 
 The expression language supports standard comparison and logical operators:
 
@@ -20,7 +20,7 @@ The expression language supports standard comparison and logical operators:
 - String: `+` (concatenation), `matches` (regex matching)
 - Length: `len()`
 
-### Available Context
+#### Available Context
 
 When writing conditions, you have access to several context variables:
 
@@ -35,12 +35,12 @@ When writing conditions, you have access to several context variables:
 - `store`: Key-value map of data store contents
 - `env`: Map of environment variables
 
-## Writing Conditions
+### Writing Conditions
 
 Conditions can be used in various places within flow, most commonly in the `if` field of executable configurations. Here are
 some examples of common conditional patterns:
 
-### Operating System and Architecture Checks
+#### Operating System and Architecture Checks
 
 Check for specific operating systems or architectures:
 
@@ -60,7 +60,7 @@ executables:
           cmd: make build-arm64
 ```
 
-### Environment Variable Checks
+#### Environment Variable Checks
 
 Make decisions based on environment variables:
 
@@ -76,7 +76,7 @@ executables:
           cmd: echo "Debug mode enabled"
 ```
 
-### Data Store Conditions
+#### Data Store Conditions
 
 Use stored data to control execution:
 
@@ -93,7 +93,7 @@ executables:
           cmd: echo "Optional key exists"
 ```
 
-### Complex Conditions
+#### Complex Conditions
 
 Combine multiple conditions using logical operators:
 
@@ -109,7 +109,7 @@ executables:
           cmd: echo "Valid build on Unix-like system"
 ```
 
-### Path and Location Checks
+#### Path and Location Checks
 
 Use context information to make path-based decisions:
 

docs/guide/state.md

@@ -1,22 +1,22 @@
-# State Management
+## State Management
 
 flow provides several mechanisms for managing state across [executable](executable.md) runs. This guide explores how to use the data store
 and temporary directories to maintain state, as well as how to make execution decisions based on that state.
 
-## Data Store
+### Data Store
 
 The data store is a key-value store that persists data across executions. It provides a simple way to share information
 between executables and maintain state between runs.
 
-### Store Persistence Scope
+#### Store Persistence Scope
 
 Values in the data store have different persistence scopes depending on where they are set:
 
 - Values set outside an executable (using the CLI directly) persist across all executions until explicitly cleared
 - Values set within an executable persist only across that executable's sub-executables (both serial and parallel)
 - All values set within an executable are automatically cleared when the parent executable completes
 
-### Managing Store Data
+#### Managing Store Data
 
 The data store can be managed at a global level in the CLI and within an executable's script. Here are the key operations:
 
@@ -51,7 +51,7 @@ flow store clear
 flow store clear --full
 ```
 
-### Using the Store in Executables
+#### Using the Store in Executables
 
 Here's an example of how to use the data store within an executable:
 
@@ -73,7 +73,7 @@ executables:
             echo "Last run: $(flow store get last-run)"
 ```
 
-### Store-Based Conditional Execution
+#### Store-Based Conditional Execution
 
 The data store's contents can be accessed in executable `if` conditions using the `data` context variable. This allows for
 dynamic execution paths based on stored values:
@@ -95,12 +95,12 @@ executables:
 
 See the [Conditional Execution](conditional.md) guide for more examples of using conditions in Flow.
 
-## Temporary Directories
+### Temporary Directories
 
 Flow provides a special directory reference `f:tmp` that creates an isolated temporary directory for an executable. This
 directory is automatically cleaned up when the executable completes.
 
-### Using Temporary Directories
+#### Using Temporary Directories
 
 To use a temporary directory, set the `dir` field in your executable configuration:
 
@@ -116,7 +116,7 @@ executables:
         make build
 ```
 
-### Sharing Temporary Files
+#### Sharing Temporary Files
 
 While temporary directories are isolated, you can share files between steps in a serial or parallel executable by using
 the same temporary directory:
@@ -133,7 +133,7 @@ executables:
         - cmd: cat output.txt
 ```
 
-## Combining State Management Approaches
+### Combining State Management Approaches
 
 The data store and temporary directories can be used together for more complex state management:
 
@@ -157,17 +157,3 @@ executables:
         - if: data["cleanup-enabled"] == "true"
           cmd: make clean
 ```
-
-### Best Practices
-
-When managing state in Flow, consider the following:
-
-1. Use the data store for:
-    - Sharing simple key-value data between executables
-    - Storing configuration that needs to persist between runs
-    - Managing feature flags and conditional execution
-
-2. Use temporary directories for:
-    - Build and compilation workspaces
-    - Processing temporary files
-    - Isolating file operations between different executions