first batch of descriptions

Author: fhennig

modules/concepts/pages/authentication.adoc

@@ -1,5 +1,6 @@
 = Authentication
 :keycloak: https://www.keycloak.org/
+:description: Overview of Stackable’s user authentication methods and configuration for LDAP, OIDC, TLS, and Static providers.
 
 The Stackable Platform uses the AuthenticationClass as a central mechanism to handle user authentication across supported products.
 The authentication mechanism needs to be configured only in the AuthenticationClass which is then referenced in the xref:stacklet.adoc[Stacklet] definition.

modules/concepts/pages/container-images.adoc

@@ -2,6 +2,7 @@
 :ubi: https://catalog.redhat.com/software/base-images
 :stackable-image-registry: https://repo.stackable.tech/#browse/browse
 :stackable-sboms: https://sboms.stackable.tech/
+:description: Overview of Stackable’s container images, including structure, multi-platform support, and why upstream images are not used.
 
 The core artifacts of the Stackable Data Platform are container images of Kubernetes operators and the products that these operators deploy.
 

modules/concepts/pages/index.adoc

@@ -1,4 +1,5 @@
 = Concepts
+:description: Explore Stackable Data Platform concepts like Stacklets, configuration mechanisms, resources, connectivity, security, and observability.
 
 == Overview
 

modules/concepts/pages/labels.adoc

@@ -1,5 +1,6 @@
 = Labels
 :common-labels: https://kubernetes.io/docs/concepts/overview/working-with-objects/common-labels/
+:description: Understand resource labeling by Stackable operators and tools like stackablectl and Helm for better management and organization.
 
 Labels are key/value pairs in the metadata of Kubernetes objects that add identifying information to the object.
 They do not have direct semantic implications but can be used to organize and manage resources.

modules/concepts/pages/logging.adoc

@@ -8,6 +8,7 @@
 :vector-agg-install: https://vector.dev/docs/setup/installation/package-managers/helm/#aggregator
 :vector-source-vector: https://vector.dev/docs/reference/configuration/sources/vector/
 :vector-topology-centralized: https://vector.dev/docs/setup/deployment/topologies/#centralized
+:description: Learn Stackable's logging setup: human-readable and aggregated logs with Vector, consistent configuration across Stacklets, and custom overrides.
 
 Logging is important for observability of the platform.
 Stackable provides human-readable plaintext logs for each running container, as well as aggregated and persisted logs with identical structure across the whole platform.

modules/concepts/pages/operations/cluster_operations.adoc

@@ -1,5 +1,6 @@
 = Cluster operations
 :page-aliases: ../cluster_operations.adoc
+:description: Manage Stackable clusters with operations like pausing reconciliation, stopping Pods, and manual/automatic restarts. Learn how to update and restart services effectively.
 
 Stackable operators offer different cluster operations to control the reconciliation process.
 This is useful when updating operators, debugging or testing of new settings:

modules/concepts/pages/operations/graceful_shutdown.adoc

@@ -1,4 +1,5 @@
 = Graceful shutdown
+:description: Graceful shutdown ensures a controlled, clean shutdown of service instances, allowing time for normal shutdown activities.
 
 Graceful shutdown refers to the managed, controlled shutdown of service instances in the manner intended by the software authors.
 Typically, an instance will receive a signal indicating the intent for the server to shut down, and it will initiate a controlled shutdown.

modules/concepts/pages/operations/index.adoc

@@ -1,4 +1,5 @@
 = Operations
+:description: Guidance for maintaining Stackable Data Platform installations. Covers service availability, maintenance actions, and performance optimization.
 
 This section of the documentation is intended for the operations teams that maintain a Stackable Data Platform installation.
 It provides you with the necessary details to operate it in a production environment.

modules/concepts/pages/operations/pod_disruptions.adoc

@@ -1,5 +1,6 @@
 = Allowed Pod disruptions
 :k8s-pdb: https://kubernetes.io/docs/tasks/run-application/configure-pdb/
+:description: Configure PodDisruptionBudgets (PDBs) to minimize planned downtime for Stackable products. Default values are based on fault tolerance and can be customized.
 
 Any downtime of our products is generally considered to be bad.
 Although downtime can't be prevented 100% of the time - especially if the product does not support High Availability - we can try to do our best to reduce it to an absolute minimum.

modules/concepts/pages/operations/pod_placement.adoc

@@ -1,5 +1,6 @@
 = Pod placement
 :page-aliases: ../pod_placement.adoc
+:description: Configure pod affinity, anti-affinity, and node affinity for Stackable Data Platform operators using YAML definitions.
 
 Several operators of the Stackable Data Platform permit the configuration of pod affinity as described in the Kubernetes https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/[documentation].
 If no affinity is defined in the product's custom resource, the operators apply reasonable defaults that make use of the `preferred_during_scheduling_ignored_during_execution` property.