Pluggable-approach-for-Mappers-and-Drivers.md

@@ -23,17 +23,19 @@ Key points:
 - This eases the effort required to reuse community implementations while accommodating provider-specific sets of Drivers.
 - Reusing the community OSDU platform implementation becomes more accessible with reduced effort.
 - Community service implementations serve as tested binaries, maintained by the community, and open to updates and contributions.
-- To implement the platform on a custom set of technologies, the primary requirement is to develop the necessary Drivers while reusing tested binaries from the platform.
+- To implement the platform on a custom set of technologies, the primary requirement is to develop the necessary Drivers while reusing tested binaries from the platform. <br/>
+![Untitled_Diagram.drawio_16_](uploads/a10ae0924491f15994faf24a5876ea0f/Untitled_Diagram.drawio_16_.png)
 
 #### Hybrid Platform:
 - The current state of the platform doesn't allow selective swapping of technologies.
-- The introduction of a plugin-based platform provides the capability to selectively swap underlying resources.
-
+- The introduction of a plugin-based platform provides the capability to selectively swap underlying resources. <br/>
+![Untitled_Diagram.drawio_17_](uploads/84649218906056b4cba8f15cbf021f58/Untitled_Diagram.drawio_17_.png)
 #### Maven Shade and Plugin-Based Approaches Not Mandatory:
 - The plugin-based approach does not impose mandatory usage of Maven Shade and Uber jars.
 - Providers have the option to introduce their drivers as they are and use them in the provider module as direct dependencies.
 - Additionally, the community's south decision point or core-plus module won't require providers to remove already bundled community dependencies since they are not present.
 
+
 ### 4. Prerequisites
 
 **For Local Development Build Environment**: