add info about static vs dynamic content

Author: PoojaB26

docs/ff-concepts/adding-customization/common-examples.md

@@ -41,7 +41,11 @@ Most custom FlutterFlow classes in the generated code are prefixed with `FF<Clas
 
 ![suggestions-dropdown.png](imgs/suggestions-dropdown.png)
 
-### Leveraging Component from Custom Widget 
+### Leveraging Components in Custom Widget 
+
+:::warning[Static Components vs Dynamic]
+Use this approach only when the component is a fixed element that does not change across different use cases. If the child component needs to change based on user choices, pass it directly [**as a parameter**](custom-widgets.md#creating-a-new-custom-widget).
+:::
 
 In a **[Custom Widget](custom-widgets.md)**, you can integrate a previously built **[FlutterFlow Component](../../resources/ui/components/intro-components.md)** directly, saving you from recreating child content in code. For example, if you’re building a Custom Widget to display custom dialog boxes or bottom sheets using a package from 
 [pub.dev](custom-code.md#pubdev), you can simply return an existing Component created on the canvas, rather than coding a new one from scratch.
@@ -50,6 +54,8 @@ In a **[Custom Widget](custom-widgets.md)**, you can integrate a previously buil
 When referencing a Component class in your code, FlutterFlow will automatically add the necessary import statement.
 :::
 
+
+
 ![return-widget-custom-code.png](imgs/return-widget-custom-code.png)