wrap widget tree structure in a details element

Author: manuel-plavsic

README.md

@@ -70,6 +70,9 @@ The package supports many features, like providers that accept arguments. But to
 
     **Note:** the `ProviderScope` defined in step 2 needs to be an ancestor of this `InjectingWidget` widget.
 
+<details>
+<summary><strong>If the widget tree structure is still not clear</strong>, click <strong>here</strong> to expand</summary>
+
 ### Widget tree structure
 
 To make things clear, here is the widget tree structure from the example above, shown in the most detailed form:
@@ -92,6 +95,8 @@ To make things clear, here is the widget tree structure from the example above,
 
               * ... — widget(s)
 
+</details>
+
 ## What is unique about this library
 
 The **key difference between Disco and other established solutions** is that Disco **does not rely solely on types** for providing and injecting dependencies.

docs/src/content/docs/index.mdx

@@ -54,6 +54,9 @@ The package supports many features, like providers that accept arguments. But to
 
     **Note:** the `ProviderScope` defined in step 2 needs to be an ancestor of this `InjectingWidget` widget.
 
+<details>
+<summary><strong>If the widget tree structure is still not clear</strong>, click <strong>here</strong> to expand</summary>
+
 ### Widget tree structure
 
 To make things clear, here is the widget tree structure from the example above, shown in the most detailed form:
@@ -76,6 +79,8 @@ To make things clear, here is the widget tree structure from the example above,
 
               * ... — widget(s)
 
+</details>
+
 ## What is unique about this library
 
 The **key difference between Disco and other established solutions** is that Disco **does not rely solely on types** for providing and injecting dependencies.

packages/disco/README.md

@@ -70,6 +70,9 @@ The package supports many features, like providers that accept arguments. But to
 
     **Note:** the `ProviderScope` defined in step 2 needs to be an ancestor of this `InjectingWidget` widget.
 
+<details>
+<summary><strong>If the widget tree structure is still not clear</strong>, click <strong>here</strong> to expand</summary>
+
 ### Widget tree structure
 
 To make things clear, here is the widget tree structure from the example above, shown in the most detailed form:
@@ -92,6 +95,8 @@ To make things clear, here is the widget tree structure from the example above,
 
               * ... — widget(s)
 
+</details>
+
 ## What is unique about this library
 
 The **key difference between Disco and other established solutions** is that Disco **does not rely solely on types** for providing and injecting dependencies.