more descriptions

modules/guides/pages/custom-images.adoc

@@ -1,8 +1,8 @@
 = Using customized product images
-
 :stackable-docker-registry: https://repo.stackable.tech/#browse/browse:docker:v2%2Fstackable
 :kind: https://kind.sigs.k8s.io/
 :kind-load-image: https://kind.sigs.k8s.io/docs/user/quick-start/#loading-an-image-into-your-cluster
+:description: Customize Stackable product images by modifying base images, deploying to a registry or Kubernetes cluster, and configuring your Stacklet to use them.
 
 The Stackable operator require a certain structure inside the product images, but modifications can be made.
 This is useful to for example load additional extensions or database drivers into an image.

modules/guides/pages/enabling-verification-of-image-signatures.adoc

@@ -1,5 +1,6 @@
 = Enabling verification of image signatures
 :page-aliases: tutorials:enabling-verification-of-image-signatures.adoc
+:description: Learn to enable and verify image signatures in Kubernetes using Sigstore’s Policy Controller, ensuring image authenticity and security in your cluster.
 
 Image signing is a security measure that helps ensure the authenticity and integrity of container images. Starting with SDP 23.11, all our images are signed https://docs.sigstore.dev/cosign/openid_signing/["keyless"]. By verifying these signatures, cluster administrators can ensure that the images pulled from Stackable's container registry are authentic and have not been tampered with.
 Since Kubernetes does not have native support for verifying image signatures yet, we will use Sigstore's https://docs.sigstore.dev/policy-controller/overview/[Policy Controller] in this tutorial.

modules/guides/pages/providing-resources-with-pvcs.adoc

@@ -3,6 +3,7 @@
 :pvcs: https://kubernetes.io/docs/concepts/storage/persistent-volumes/
 :pvc-capacity: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#capacity
 :pvc-access-modes: https://kubernetes.io/docs/concepts/storage/persistent-volumes/#access-modes
+:description: Learn how to use PersistentVolumeClaims to provide external resources to Stacklets in Kubernetes, including access modes, node selection, and practical examples.
 
 Several of the tools on the Stackable platform can use external resources that the cluster administrator makes available via a PersistentVolume.
 Airflow users can access DAG jobs this way, and Spark users can do the same for data or other job dependencies, to name just two examples.

modules/guides/pages/running-stackable-in-an-airgapped-environment.adoc

@@ -1,5 +1,6 @@
 = Running Stackable in an air-gapped environment
 :page-aliases: tutorials:running-stackable-in-an-airgapped-environment.adoc
+:description: Learn how to run Stackable in an air-gapped environment by mirroring images, setting up a reverse proxy, and configuring container runtimes.
 
 The main challenge with running Stackable in an air-gapped environment is how to get the artifacts (container images and Helm charts) into the environment. There are a few ways to do this:
 

modules/guides/pages/viewing-and-verifying-sboms.adoc

@@ -1,5 +1,6 @@
 = Viewing and verifying SBOMs of the Stackable Data Platform
 :page-aliases: tutorials:viewing-and-verifying-sboms.adoc
+:description: Learn to view and verify SBOMs for Stackable Data Platform using CycloneDX standards and cosign. Ensure SBOM authenticity with Policy Controller.
 
 With release 24.3 of SDP, we started providing SBOMs (Software Bill of Materials) for our container images. Please note that they currently are in a draft stage and we are continually working on improving them. As a first step, we aim to provide a list of all primary (top level) components and their versions included in each container image. Our SBOMs follow the https://cyclonedx.org/[CycloneDX] standard and are available in JSON format.