Merge pull request #60 from php-etl/feature/add-content-to-custom-plugin-page

Feature/add content to custom plugin page

Author: sebprt

content/connectivity/custom/_index.en.md

@@ -8,12 +8,16 @@ description: "Read transform and write files in any format"
 weight: 3
 ---
 
-- [What is it ?](#what-is-it-)
+- [What is it ?](#definition)
 - [Installation](#installation)
 - [Usage](#usage)
   - [Building an extractor](#building-an-extractor)
   - [Building a transformer](#building-a-transformer)
   - [Building a loader](#building-a-loader)
+- [Usage examples](#usage-examples)
+  - [Example of an extractor](#example-of-an-extractor)
+  - [Example of a transformer](#example-of-a-transformer)
+  - [Example of a loader](#example-of-a-loader)
 ---
 
 ## Definition
@@ -29,42 +33,58 @@ This plugin is already integrated into the Satellite package, so you can’t req
 
 Unlike other plugins, the configuration is the same whether it is an extractor, a transformer or a loader.
 
-First you need to [determine your services](../../feature/services) in your pipeline or workflow and then use the `use` 
-option which allows you to define which service to use.
-
 ### Building an extractor
 
+In the example given, we explain how to configure a custom extractor with the `Bar` class located in the `App\Class` namespace.
+
+Here's a more detailed explanation:
+
 ```yaml
 custom:
   extractor:
-    use: 'App\Class\Bar'
+    use: 'App\Class\Bar' # This line specifies the extractor class you want to use.
     services:
-      App\Class\Bar: ~
+      App\Class\Bar: ~ # Here, we declare the service associated with the Bar class with the syntax App\Class\Bar: ~. This simply indicates that we want to use the default parameters for this service.
 ```
 
+For more details about service configurations, please visit the [declaring-services](../../feature/services) documentation.
+
 ### Building a transformer
 
+In the example given, we explain how to configure a custom extractor with the `Bar` class located in the `App\Class` namespace.
+
+Here's a more detailed explanation:
+
 ```yaml
 custom:
   transformer:
-    use: 'App\Class\Bar'
+    use: 'App\Class\Bar' # This line specifies the extractor class you want to use.
     services:
-      App\Class\Bar:
-        factory: 
+      App\Class\Bar: # Here, we declare the service associated with the Bar class.
+        factory: # This section indicates that the service must be created by calling the extract method of the App\Class\Bar class.
           class: App\Class\Bar
           method: extract
-        arguments:
+        arguments: # The arguments to be passed to the extract method. In this example, the @foo symbol indicates that the foo service should be injected as an argument. Make sure that the foo service is configured correctly elsewhere in your pipeline.
           - '@foo'
+      foo: ~
 ```
 
+For more details about service configurations, please visit the [declaring-services](../../feature/services) documentation.
+
 ### Building a loader
 
+In the example given, we explain how to configure a custom extractor with the `Bar` class located in the `App\Class` namespace.
+
+Here's a more detailed explanation:
+
 ```yaml
 custom:
   loader:
-    use: 'App\Class\Bar'
+    use: 'App\Class\Bar' # This line specifies the extractor class you want to use.
     services:
-      App\Class\Bar:
-        calls:
-          - withUsername: [ 'admin' ]
+      App\Class\Bar: # Here, we declare the service associated with the Bar class.
+        calls: # This section indicates that specific method calls must be made to the service instance.
+          - withUsername: [ 'admin' ] # This means that a method call named withUsername must be made to the instance of the Bar class, with the username "admin" passed as an argument.
 ```
+
+For more details about service configurations, please visit the [declaring-services](../../feature/services) documentation.

themes/middleware/assets/css/style.css

@@ -641,7 +641,10 @@ h1.single-title {
 
 .content h1,
 .content h2,
-.content h3 {
+.content h3,
+.content h4,
+.content h5,
+.content h6 {
   padding: 10px 0;
   position: sticky;
   top: 95px;