Reworked the index page to add more cards

Author: nastena1606

docs/app-credentials.md

@@ -1,6 +1,6 @@
 # Get credentials for your app
 
-For production and for most applications, you should use a dedicated **application-level (unprivileged) user** instead of the database admin account. The Operator can create this user for you and store the credentials in a Kubernetes Secret that your app can read.
+For production and for most applications, you should use a dedicated **application-level (unprivileged) user** instead of the [database admin account](system-users.md). The Operator can create this user for you and store the credentials in a Kubernetes Secret that your app can read.
 
 ## Create one application user via Custom Resource
 

docs/architecture.md

@@ -40,11 +40,13 @@ By default, the Operator creates Percona Server for MongoDB replica set with thr
 
 ## High availability
 
-The Operator supports high availability through replica set topology, Pod distribution, automatic recovery, and client connectivity.
+High-availability is natively supported via Percona Server for MongoDB replica set or sharded cluster topology. 
+
+The Operator adds to it through replica set topology, Pod distribution, automatic recovery, and client connectivity.
 
 ### Pod distribution
 
-The Operator uses [node affinity and anti-affinity](constraints.md) to spread MongoDB Pods across separate worker nodes when possible. That way a single node failure does not take down multiple replica set members. You can tune affinity rules in the PerconaServerMongoDB custom resource.
+The Operator uses [node affinity and anti-affinity](constraints.md) to spread MongoDB Pods across separate worker nodes when possible. That way a single node failure does not take down multiple replica set members. You can [tune affinity](constraints.md) rules in the `PerconaServerMongoDB` custom resource.
 
 ### Automatic recovery
 
@@ -63,10 +65,7 @@ Applications should use a **mongodb+srv** connection URI. MongoDB drivers (4.2 a
 
     The Operator applies security settings that are stricter than default Percona Server for MongoDB. The initial configuration includes default passwords for required user accounts; change them in production as described in the [installation instructions](System-Requirements.md#installation-guidelines).
 
-## What to read next
+## Next step
 
-- [About backups](backups.md) — How backups and restores work with PBM
-- [Scale the cluster](scaling.md) — Scale your cluster vertically or horizontally
-* [Control Pod placement](constraints.md) — Configure anti-affinity and pod distribution
-* [Upgrade the Operator and database](update.md) — Keep your cluster up to date
-* [Custom Resource options](operator.md) — Description of available configuration options
+[Get started with the Operator](quickstart.md){.md-button}
+[Compare with other solutions](compare.md){.md-button}

docs/compare.md

@@ -81,3 +81,5 @@ Finally, let’s compare various features that are not a good fit for other cate
 | Helm              | Yes                          | Yes                | Yes, for operator only | Yes, for operator only        | Yes, for operator only            |
 | SSL/TLS           | Yes                          | Yes                | Enterprise only    | Yes                               | Yes                               |
 | Create users/roles| Yes                          | Yes                | No                 | Yes                               | Yes                               |
+
+[Get started with the Operator](quickstart.md){.md-button}

docs/everest.md

@@ -1,9 +1,9 @@
-# Install Percona Server for MongoDB cluster using Everest
+# Install Percona Server for MongoDB cluster using Open Everest
 
-[Percona Everest :octicons-link-external-16:  :octicons-link-external-16:](https://docs.percona.com/everest/) is an open source cloud-native database platform that helps developers deploy code faster, scale deployments rapidly, and reduce database administration overhead while regaining control over their data, database configuration, and DBaaS costs.
+[Open Everest :octicons-link-external-16:](https://openeverest.io) is an open source cloud-native database platform that helps developers deploy code faster, scale deployments rapidly, and reduce database administration overhead while regaining control over their data, database configuration, and DBaaS costs.
 
 It automates day-one and day-two database operations for open source databases on Kubernetes clusters.
-Percona Everest provides API and Web GUI to launch databases with just a few clicks and scale them, do routine maintenance tasks, such as software updates, patch management, backups, and monitoring.
+Open Everest provides API and Web GUI to launch databases with just a few clicks and scale them, do routine maintenance tasks, such as software updates, patch management, backups, and monitoring.
 
-You can try it in action by [Installing Percona Everest :octicons-link-external-16:  :octicons-link-external-16:](https://docs.percona.com/everest/quickstart-guide/qs-overview.html) and [managing your first cluster :octicons-link-external-16:  :octicons-link-external-16:](https://docs.percona.com/everest/use/cluster-management.html).
+Refer to [Open Everest documentation :octicons-link-external-16:](https://openeverest.io/docs/) to try it in action.
 

docs/features.md

@@ -24,6 +24,7 @@ Protect your data with [Percona Backup for MongoDB (PBM)](backups.md), which run
 * **Scheduled backups** — [Configure scheduled backups](backups-scheduled.md) with [remote storage](backups-storage.md) (S3, GCS, Azure, MinIO, or a file server) and retention policies.
 * **On-demand backups** — [Create a backup](backups-ondemand.md) at any time for critical operations.
 * **Logical and physical backups** — Use logical backups for portability or physical backups (including [physical incremental](backups.md#backup-types)) for faster restore on large datasets.
+* **PVC snapshots** to boost your backup and restore performance.
 * **Point-in-time recovery** — [Store oplog and restore to a point in time](backups-pitr.md).
 * **Restore** — [Restore on the same cluster or a new cluster](backups-restore.md); [replica set name remapping](backups-restore-replset-remapping.md) is supported when needed.
 
@@ -40,7 +41,7 @@ Scale your database infrastructure as demand grows:
 
 Keep your data and backups secure with built-in options:
 
-* **Transport encryption** — [Enable TLS](TLS.md) for client and server; use [cert-manager](tls-cert-manager.md) or [manual certificates](tls-manual.md).
+* **Transport encryption** — [Enable TLS](TLS.md) for client and server; use [cert-manager](tls-cert-manager.md) or [custom certificates](tls-manual.md).
 * **Data-at-rest encryption** — [Encrypt MongoDB data on disk](encryption.md).
 * **Users and roles** — Manage [application users](app-users.md) and [system users](system-users.md); optionally use [Vault](system-users-vault.md) for system user credentials.
 * **Backup encryption** — [Encrypt backups](backups-encryption.md) in object storage.
@@ -70,12 +71,10 @@ Here is what happens under the hood:
 This declarative approach means you describe what you want, and the Operator handles the orchestration so your database cluster matches your specification.
 
 [Explore the architecture](architecture.md){.md-button}
-[Comparison with other solutions](compare.md){.md-button}
+[Compare with other solutions](compare.md){.md-button}
 
-## What's next?
+## Next steps
 
-* [Get started](quickstart.md) — Get up and running in minutes, whether you build and application or need to deploy and operate the database
-* [Single- and multi-namespace deployment](single-namespace-and-multi-namespace-deployment.md) — Understand your required deployment mode
-* [Backups and restores](backups.md) — Protect your data with automated backups
-* [Monitor with PMM](monitoring.md) — Gain visibility into database performance
-* [TLS and security](TLS.md) — Secure client and server communications
+Get up and running in minutes, whether you build and application or need to deploy and operate the database.
+
+[Get started](quickstart.md){.md-button}

docs/how-it-works.md

@@ -1,10 +1,10 @@
 # How the Operator works
 
-The Percona Operator for MongoDB is a custom controller. It automates deployment and management of Percona Server for MongoDB on Kubernetes. This page explains how the Operator fits into Kubernetes and how it keeps your database cluster in the state you define.
+The Percona Operator for MongoDB is a custom controller. It is deployed as a Deployment. The Operator automates deployment and management of Percona Server for MongoDB on Kubernetes. This page explains how the Operator fits into Kubernetes and how it keeps your database cluster in the state you define.
 
 ## Extending the Kubernetes API
 
-The Operator extends the Kubernetes API with a set of custom resources: 
+The Operator extends the Kubernetes API with a set of Custom Resources: 
 
 * **PerconaServerMongoDB** for the database cluster
 * **PerconaServerMongoDBBackup** for backups
@@ -15,20 +15,29 @@ These Custom Resources are defined by the Custom Resource Definitions (CRD), whi
 Then you describe the database you want by creating or updating a `PerconaServerMongoDB` object in `deploy/cr.yaml`. At this point, the Operator steps in and handles the hard work for you. It automatically does the following:
 
 * Creates and manages the necessary Kubernetes resources (StatefulSets, Services, Pods)
-* Ensures your cluster matches the desired state you’ve defined
+* Ensures your cluster matches the desired state you've defined
 * Monitors the cluster health and automatically recovers from failures
 * Coordinates upgrades and scaling operations
 
 These operations ensure that your actual database environment always matches your request.
 
 Each `PerconaServerMongoDB` object corresponds to a single Percona Server for MongoDB setup - either a replica set or a sharded cluster. The Operator does not manage MongoDB servers that were created without using these custom resources.
 
-By default, the Operator creates Percona Server for MongoDB replica set with three members, one primary and the remaining secondaries. This is the minimal recommended configuration and it natively provides high availability. A replica set can have up to 50 members with the maximum of 7 voting members.
+## Default database deployment
+
+By default, the Operator creates Percona Server for MongoDB replica set with three members: one primary and the remaining secondaries. This is the minimal recommended configuration and it natively provides high availability. A replica set can have up to 50 members with the maximum of 7 voting members. Read more about these requirements in [MongoDB documentation :octicons-link-external-16:](https://www.mongodb.com/docs/manual/core/replica-set-architectures/#strategies).
+
+## Storage
 
 To keep your data safe and persistent, the Operator uses Kubernetes storage systems called Persistent Volumes (PVs) and PersistentVolumeClaims (PVCs). When you request storage for your database, a PVC automatically finds and attaches available storage for you. If a node fails, the Kubernetes storage system can move your data to another node, making sure your database remains available and your data stays protected. For local or special storage needs, see [Local Storage](storage.md).
 
 ## Next steps
 
-- [Design and architecture](architecture.md) — Components (mongod, PBM, mongos), replica set and sharding, and high availability.
-- [Features and capabilities](features-and-capabilities.md) — What you can do with the Operator (backups, scaling, TLS, and more).
-- [Custom Resource options](operator.md) — All options you can set in the PerconaServerMongoDB spec.
+Ready to get started? Continue to the [quickstart guide](quickstart.md) to deploy your first cluster. Or, explore the [architecture overview](architecture.md) to understand the inner workings of the Operator.
+
+[Quickstart guide](quickstart.md){.md-button}
+
+## Useful links
+
+- [Design and architecture](architecture.md)
+- [Features and capabilities](features-and-capabilities.md) 

docs/index.md

@@ -21,41 +21,64 @@ Choose how you want to use the Operator:
 
 ---
 
-## Featured topics
+<div data-grid markdown>
+<div data-banner markdown>
 
-Pick the topic that matches what you need to do:
+## :fontawesome-solid-magnifying-glass: Understand the Operator { .title }
 
-<div data-grid markdown><div data-banner markdown>
+Understand how the Operator works, how it’s designed, and how it compares to other ways to run MongoDB on Kubernetes.
 
-## :fontawesome-solid-magnifying-glass: Discover the Operator { .title }
+* [How the Operator works](how-it-works.md)
+* [Features](features.md)
+* [Architecture](architecture.md)
+* [Compare with other solutions](compare.md)
 
-Understand how the Operator works, how it’s designed, and how it compares to other ways to run MongoDB on Kubernetes.
+</div><div data-banner markdown>
 
-[How the Operator works :material-arrow-right:](how-it-works.md){ .md-button }
+## :material-progress-download: Set up the Operator and the database { .title }
+
+Ready to run robust, production-grade Percona Server for MongoDB on Kubernetes? Install the Operator and learn how to easily manage daily operations.
+
+* [Installation](install-overview.md)
+* [Manage users](users.md)
+* [Configure backups](backups.md)
+* [Scale your cluster](scaling.md)
+* [Monitor database health](monitoring.md)
+* [Upgrade](update.md)
 
 </div><div data-banner markdown>
 
-## :material-file-document-multiple: User guides { .title }
+## :material-file-document-multiple: User guides {.title}
 
 Optimize your Kubernetes and database workflows with the Operator.
 
-[User guides :material-arrow-right:](.md){ .md-button }
+* [Configure external access to the cluster](expose.md)
+* [Configure TLS](TLS.md)
+* [Encrypt data at rest](encryption.md)
+* [Set up disaster recovery with multi-cluster deployment](replication.md)
+
 
 </div><div data-banner markdown>
 
-### :material-frequently-asked-questions: Troubleshooting { .title }
+### :fontawesome-solid-user-tie: Manage cluster lifecycle {.title}
 
-Diagnose and fix issues with the Operator, the cluster, storage, or logs.
+Take control of your cluster's lifecycle. Follow these guides to keep your environment running smoothly with minimal downtime.
 
-[Troubleshooting :material-arrow-right:](debug.md){.md-button}
+* [Upgrade](update.md)
+* [Pause and resume](pause.md)
+* [Migrate data using backups](backups-move-from-external-db.md)
 
 </div><div data-banner markdown>
 
-### :material-book-education: Reference { .title }
+### :material-book-education: Look up reference materials { .title }
 
 Explore Custom Resource, backup and restore options, certified images and version compatibility.
 
-[Custom Resource options :material-arrow-right:](operator.md){ .md-button }
+* [Custom Resource options :material-arrow-right:](operator.md)
+* [Backup Resource options](backup-resource-options.md.)
+* [Restore Resource options](restore-options.md.)
+* [Percona certified images](images.md)
+* [Version compatibility matrix](versions.md)
 
 </div>
 </div>