docs: edited define-inputs-and-outputs

docs/creating-pipelines/define-inputs-and-outputs.mdx

@@ -2,6 +2,46 @@
 sidebar_position: 3
 ---
 
-# Define inputs & outputs
+# Define Inputs & Outputs
 
-Will be soon here...
+Once your nodes are connected, the next step is to define where your pipeline starts (inputs) and ends (outputs).
+
+## What are Inputs?
+
+Inputs are the data your pipeline begins with.  
+For example:
+
+- A **text prompt** 
+- An **image** uploaded by the user
+- A **number** or configuration value used in calculations
+
+To define an input:
+
+Here
+
+Video
+
+## What are Outputs?
+
+Outputs are the final result produced by the pipeline.  
+For example:
+
+- A generated text
+- A generated or modified image
+- JSON data for use in another app
+
+To define an output:
+
+Here
+
+Video
+
+## Tips for Working with Inputs and Outputs
+
+- Use **clear names** for your input/output nodes to make the pipeline easy to understand.
+- You can have **multiple inputs and outputs** if your use case requires it.
+- Some nodes can act as both intermediate processors and final outputs — choose what makes the most sense for your flow.
+
+:::tip Tip
+Defining inputs and outputs makes your pipeline reusable and easier to integrate into other systems.
+:::