Reworked intro on index page, added Beta info about async replication

Author: nastena1606

docs/ReleaseNotes/Kubernetes-Operator-for-PS-RN1.0.0.md

@@ -1,5 +1,7 @@
 # Percona Operator for MySQL Release Notes
 
+* [Percona Operator for MySQL 1.0.0 ({{date.v1_0_0}})](Kubernetes-Operator-for-PS-RN1.0.0.md)
+
 * [Percona Operator for MySQL 0.12.0 ({{date.v0_12_0}})](Kubernetes-Operator-for-PS-RN0.12.0.md)
 
 * [Percona Operator for MySQL 0.11.0 ({{date.v0_11_0}})](Kubernetes-Operator-for-PS-RN0.11.0.md)

docs/ReleaseNotes/index.md

@@ -70,6 +70,8 @@ replication types:
     modification or the actual statement. Then the replica executes each change
     on its own database and obtains consistent set of data.
 
+    This replication type is in Beta state and we don't recommend it for production use yet.
+
 * **Group Replication** means that a read transaction can be executed on any
     instance, while write transactions happen only on primary. For a write transaction, MySQL tries to get consensus with the other
     instances before returning it completed back to the client.

docs/architecture.md

@@ -7,4 +7,4 @@
 {% if config.site_description %}
 <h1>{{ config.site_description }}</h1>
 {% endif %} 
-<h2> 0.12.0 (September 23, 2025)</h2>
+<h2> 1.0.0 (October 23, 2025)</h2>

docs/assets/templates/pdf_cover_page.tpl

@@ -1,16 +1,61 @@
 # Percona Operator for MySQL based on Percona Server for MySQL
 
-Percona Operator for MySQL is a custom controller that extends Kubernetes to automate the entire lifecycle of [Percona Server for MySQL :octicons-link-external-16:](https://www.percona.com/doc/percona-server/LATEST/index.html) clusters. The Operator makes it much simpler to run and reliably manage databases that traditionally require a lot of manual effort on Kubernetes.
+If you run MySQL and want easier operations, better reliability, and to use modern cloud workflows - Percona Operator for MySQL is here for you. 
 
-You declare how you want your Percona Server for MySQL cluster to run (e.g., "I need a 3-node Percona Server for MySQL cluster with backups enabled") using a special Kubernetes configuration file called a Custom Resource. The Operator then takes over. It constantly watches your cluster, understands its unique needs, and automatically performs tasks like deployment, scaling, handling failures, managing backups, and coordinating upgrades.
+Percona Operator for MySQL is based on [Percona Server for MySQL :octicons-link-external-16:](https://www.percona.com/doc/percona-server/LATEST/index.html), delivering enhanced performance, better observability and robust backup capabilities right out of the box.
 
-For you, this means reduced operational overhead, faster deployments, and a highly available, self-healing database infrastructure that can run consistently across any cloud environment.
+Think of Percona Operator for MySQL as a MySQL automation engine inside your Kubernetes cluster. You define your desired setup in a YAML configuration file—and the Operator makes it real. It automates all database management operations for you, from deployment to scaling, backups and upgrades - everything you need to have a reliable, production ready database from day one.
+
+The Operator constantly watches your cluster, understands its unique needs and automatically manages its lifecycle ensuring it operates as you intended.
+
+!!! note ""
+
+    Percona Operator for MySQL is General Availability with [**group replication**](architecture.md#replication-types-and-proxy-solutions). Asynchronous replication remains in Beta state, and we don't recommend it for production use yet.
 
 [What's new in version {{release}}](ReleaseNotes/Kubernetes-Operator-for-PS-RN{{release}}.md){.md-button}
 
+## Why to use the Operator
+
+*  DBAs & SREs choose it because it reduces manual toil—no more babysitting clusters or writing custom failover logic.
+*  DevOps teams use it to deploy MySQL consistently across environments, with infrastructure as code.
+*  Architects choose it for its portability, reliability, and open source flexibility and benefit from no vendor lock-in.
+
+
+## Ready to get started? 
+
+Starting with the Operator is easy. Follow our documentation and you'll be set up in a minute.
+
+[Quickstart guides :material-arrow-right:](quickstart.md){ .md-button }
+
+
+<div data-grid markdown><div data-banner markdown>
+
+## :fontawesome-solid-magnifying-glass: Discover the Operator { .title }
+
+Learn the Operator's features, how it works and what it consists of.
+
+[Features :material-arrow-right:](features.md){ .md-button }
+
+</div><div data-banner markdown>
+
+## :material-security: Security and encryption { .title }
+
+Rest assured! Learn more about our security features designed to protect your valuable data.
+
+[Security measures :material-arrow-right:](TLS.md){ .md-button }
+
+</div><div data-banner markdown>
+
+### :material-backup-restore: Backup management { .title }
+
+Learn what you can do to maintain regular backups of your Percona Server for MySQL cluster.
+
+[Backup management :material-arrow-right:](backups.md){ .md-button }
 
-!!! note
+</div><div data-banner markdown>
 
-    Version {{ release }} of the [Percona Operator for MySQL :octicons-link-external-16:](https://github.com/percona/percona-server-mysql-operator) is **a tech preview release** and it is **not recommended for production environments**. **As of today, we recommend using** [Percona Operator for MySQL based on Percona XtraDB Cluster](https://www.percona.com/doc/kubernetes-operator-for-pxc/index.html), which is production-ready and contains everything you need to quickly and consistently deploy and scale MySQL clusters in a Kubernetes-based environment, on-premises or in the cloud.
+### :material-frequently-asked-questions: Troubleshooting { .title }
 
+Our comprehensive resources will help you overcome challenges, from everyday issues to specific doubts.
 
+[Diagnostics :material-arrow-right:](debug.md){.md-button}

docs/index.md

@@ -234,6 +234,7 @@ nav:
 
     - Release Notes:
           - "Release notes index": ReleaseNotes/index.md
+          - ReleaseNotes/Kubernetes-Operator-for-PS-RN1.0.0.md
           - ReleaseNotes/Kubernetes-Operator-for-PS-RN0.12.0.md
           - ReleaseNotes/Kubernetes-Operator-for-PS-RN0.11.0.md
           - ReleaseNotes/Kubernetes-Operator-for-PS-RN0.10.0.md

mkdocs-base.yml

@@ -22,6 +22,7 @@ year: '2025'
 
 release: '0.12.0'
 date: 
+  1_0_0: '2025-10-23'
   v0_12_0: '2025-09-23'
   v0_11_0: '2025-09-01'
   v0_10_0: '2025-06-04'