Merge pull request #6014 from EnterpriseDB/DOCS-955-pgd-new-flow-laun…

…ch-add-cta-call-to-action-to-s

DOCS-955 POC for new flow

product_docs/docs/pgd/5/index.mdx

@@ -48,6 +48,24 @@ navigation:
 
 EDB Postgres Distributed (PGD) provides multi-master replication and data distribution with advanced conflict management, data-loss protection, and [throughput up to 5X faster than native logical replication](https://www.enterprisedb.com/blog/performance-improvements-edb-postgres-distributed). It enables distributed Postgres clusters with high availability up to five 9s.
 
+
+<div class="container mt-4 mb-4 border border-primary">
+<div class="row bg-light">
+<div class="col-12 text-center px-3 py-3">
+Read about why PostgreSQL is better when it’s distributed with EDB Postgres Distributed in <a href="https://www.enterprisedb.com/distributed-postgresql-always-on-database-availability">Distributed PostgreSQL:The Key to Always On Database Availability</a>
+</div>
+</div>
+<div class="row bg-light">
+<div class="col-6 px-3 py-3 d-flex justify-content-center align-items-center">
+<a href="https://www.enterprisedb.com/products/edb-postgres-distributed" class="btn btn-lg btn-primary text-light px-4 text-nowrap text-center" title="Get a free trial of PGD">PGD Free Trial</a>
+</div>
+<div class="col-6 px-3 py-3 d-flex justify-content-center align-items-center">
+<a href="https://www.enterprisedb.com/contact" class="btn btn-lg btn-primary text-light px-4 text-nowrap text-center" title="Contact sales with any questions">Contact Sales</a>
+</div>
+</div>
+</div>
+
+
 By default, EDB Postgres Distributed uses asynchronous replication, applying changes on
 the peer nodes only after the local commit. You can configure additional levels of synchronicity between different nodes, groups of nodes, or all nodes by configuring
 [Group Commit](durability/group-commit), [CAMO](durability/camo), or
@@ -68,3 +86,4 @@ Postgres 16 support is available only in EDB Postgres Distributed 5.3 and later.
 !!!
 
 For feature compatibility with compatible servers, see [Choosing a Postgres distribution](planning/choosing_server).
+

product_docs/docs/pgd/5/overview/index.mdx

@@ -1,12 +1,29 @@
 ---
 title: "PGD overview"
 description: An overview of EDB Postgres Distributed architecture and performance characteristics
+deepToC: true
 redirects: 
   - bdr
 ---
 
 EDB Postgres Distributed (PGD) provides multi-master replication and data distribution with advanced conflict management, data-loss protection, and [throughput up to 5X faster than native logical replication](https://www.enterprisedb.com/blog/performance-improvements-edb-postgres-distributed). It also enables distributed Postgres clusters with high availability up to five 9s.
 
+<div class="container mt-4 mb-4 border border-primary">
+<div class="row bg-light">
+<div class="col-12 text-center px-3 py-3">
+Read about why PostgreSQL is better when it’s distributed with EDB Postgres Distributed in <a href="https://www.enterprisedb.com/distributed-postgresql-always-on-database-availability">Distributed PostgreSQL:The Key to Always On Database Availability</a>
+</div>
+</div>
+<div class="row bg-light">
+<div class="col-6 px-3 py-3 d-flex justify-content-center align-items-center">
+<a href="https://www.enterprisedb.com/products/edb-postgres-distributed" class="btn btn-lg btn-primary text-light px-4 text-nowrap text-center" title="Get a free trial of PGD">PGD Free Trial</a>
+</div>
+<div class="col-6 px-3 py-3 d-flex justify-content-center align-items-center">
+<a href="https://www.enterprisedb.com/contact" class="btn btn-lg btn-primary text-light px-4 text-nowrap text-center" title="Contact sales with any questions">Contact Sales</a>
+</div>
+</div>
+</div>
+
 PGD provides loosely coupled, multimaster logical replication using a mesh topology. This means that you can write to any server and the changes are sent directly, row-by-row, to all the other servers that are part of the same PGD group.
 
 By default, PGD uses asynchronous replication, applying changes on the peer nodes only after the local commit. Multiple synchronous replication options are also available.
@@ -104,3 +121,4 @@ Synchronous replication options can send changes concurrently to multiple nodes
 If the workload tries to use all CPU resources, then this resource constrains replication, which can then affect the replication lag.
 
 In summary, adding more master nodes to a PGD group doesn't result in significant write throughput increase when most tables are replicated because all the writes are replayed on all nodes. Because PGD writes are in general more effective than writes coming from Postgres clients by way of SQL, you can increase performance. Read throughput generally scales linearly with the number of nodes.
+