Added the SUSE SolidDriver Program reference.

Author: lvicoun

articles/customizing-products-images.asm.xml

@@ -34,6 +34,10 @@
   <resources>
     <resource xml:id="_customizing-products-identification"
     href="../concepts/customizing-products-identification.xml"/>
+    <resource xml:id="_customizing-products-kernel"
+    href="../concepts/customizing-products-kernel.xml"/>
+    <resource xml:id="_customizing-products-drivers"
+    href="../concepts/customizing-products-drivers.xml"/>
     <resource xml:id="_customizing-products-images-introduction" href="../concepts/customizing-products-images-introduction.xml"/>
 
   </resources>
@@ -175,9 +179,23 @@
           <para/>
         </abstract>
       </merge>
-      </module>
+      </module>      
     <!-- pull in a topic and switch the title -->
     <module resourceref="_customizing-products-identification" renderas="section"/>
+    <module resourceref="_customizing-products-kernel" renderas="section">
+      <merge>
+        <abstract>
+          <para/>
+        </abstract>
+      </merge>
+      </module>
+      <module resourceref="_customizing-products-drivers" renderas="section">
+      <merge>
+        <abstract>
+          <para/>
+        </abstract>
+      </merge>
+      </module>
 
     <module resourceref="_customizing-products-images" renderas="section"/>
 

concepts/customizing-products-drivers.xml

@@ -18,44 +18,21 @@
  xmlns:xlink="http://www.w3.org/1999/xlink"
  xmlns:trans="http://docbook.org/ns/transclusion">
   <info>
-    <title>Concept</title><!-- can be changed via merge in the assembly -->
+    <title>Creating custom dirvers</title><!-- can be changed via merge in the assembly -->
     <!--add author's email address-->
-    <meta name="maintainer" content="" its:translate="no"/>
+    <meta name="maintainer" content="[email protected]" its:translate="no"/>
     <abstract><!-- can be changed via merge in the assembly -->
       <para>
-       Introductory text
+       The topic serves as a link to the SolidDriver Program description.
       </para>
     </abstract>
   </info>
-  <section xml:id="concept-example-what-is">
-    <title>What is foo bar?</title>
-    <para>
-      A paragraph of text, answering the question above and explaining the
-      aim/function of foo bar.
-    </para>
-  </section>
-  <section xml:id="concept-example-how-it-works">
-    <title>How does foo bar work?</title>
-    <para>
-      A paragraph of text, answering the question above and explaining the
-      mechanism behind foo bar.
-    </para>
-    <figure xml:id="fig-one">
-      <title>A figure</title>
-      <mediaobject>
-        <imageobject role="html">
-          <imagedata fileref="example.png"/>
-        </imageobject>
-        <imageobject role="fo">
-          <imagedata fileref="example.png" width="85%"/>
-        </imageobject>
-      </mediaobject>
-    </figure>
-  </section>
-  <section xml:id="concept-example-benefits">
-    <title>Benefits of foo bar</title>
-    <para>
-      A paragraph of text, pointing out the benefits of foo bar.
-    </para>
-  </section>
+  <para>
+Installing third-party hardware drivers into a mission-critical environment can be a source of significant concern, from ensuring compatibility to guaranteeing support. The &suse; SolidDriver Program directly addresses these challenges by creating a standardized framework for our hardware partners. This ensures that kernel drivers are delivered in a uniform, proven, and reliable manner, giving customers the confidence to integrate the latest technology into their &sle;.
+  </para>
+  <para>
+    For a detailed description of the &suse; SolidDriver Program refer to the <link
+    xlink:href="https://drivers.suse.com/doc/SolidDriver/index.html">official documentation of the
+    program</link>.
+  </para>
 </topic>

concepts/customizing-products-kernel.xml

@@ -28,6 +28,6 @@
     </abstract>
   </info>
   <para>
-Working with external kernel modules on SUSE Linux Enterprise systems requires a specific approach to ensure they remain compatible with kernel updates. The official Kernel Module Packages (KMP) Manual provides detailed guidelines on this process. This comprehensive guide covers everything from the background on kernel ABI stability to the step-by-step process of building, packaging, signing, and deploying your own kernel modules correctly.
+Working with external kernel modules on SUSE Linux Enterprise systems requires a specific approach to ensure they remain compatible with kernel updates. The official Kernel Module Packages Manual provides detailed guidelines on this process. This comprehensive guide covers everything from the background on kernel ABI stability to the step-by-step process of building, packaging, signing, and deploying your own kernel modules correctly.
   </para>
 </topic>