Skip to content

Commit 41d7f8a

Browse files
Merge branch 'main' of https://github.com/0xPolygon/polygon-docs into km/style_scan
2 parents 64e7938 + 8220871 commit 41d7f8a

File tree

16 files changed

+1721
-295
lines changed

16 files changed

+1721
-295
lines changed

docs/_site_essentials/stylesheets/extra.css

Lines changed: 3 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -23,10 +23,7 @@
2323
}
2424

2525
img.figure {
26-
border: 5px solid #ae6fdb !important;
27-
box-shadow: 0 0 10px rgba(0, 0, 0, 0.3);
2826
margin: 0 auto;
29-
max-width: 80%;
3027
display: block;
3128
}
3229

@@ -35,10 +32,10 @@ div.flex-figure {
3532
}
3633

3734
div.flex-figure div.flex-figure-left {
38-
flex-grow: 2;
35+
flex-grow: 1;
36+
flex-shrink: 5;
3937
}
4038

4139
div.flex-figure div.flex-figure-right {
42-
flex-grow: 1;
43-
flex-shrink: 1.5;
40+
flex-grow: 2;
4441
}

docs/_site_essentials/stylesheets/polygon-docs.webflow.css

Lines changed: 9 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ h1 {
1111
margin-top: 0;
1212
margin-bottom: 0 !important;
1313
font-size: 38px;
14-
font-weight: 1000 !important;
14+
font-weight: 600 !important;
1515
line-height: 44px;
1616
color: var(--main-black) !important;
1717
font-family: Generalsans, sans-serif !important;
@@ -27,6 +27,10 @@ h2 {
2727
font-family: Generalsans, sans-serif !important;
2828
}
2929

30+
div.main h1 {
31+
margin-top: 0 !important;
32+
}
33+
3034
div.main h3 {
3135
margin-top: 0 !important;
3236
}
@@ -121,8 +125,10 @@ div.main .section {
121125
grid-column-gap: 3rem;
122126
grid-row-gap: 3rem;
123127
justify-content: space-between;
124-
align-items: center;
128+
align-items: flex-start;
125129
display: flex;
130+
position: relative;
131+
bottom: 50px;
126132
}
127133

128134
.hero-content-flex.product-hero-flex {
@@ -154,6 +160,7 @@ div.main .section {
154160
font-size: 48px !important;
155161
line-height: 1.3 !important;
156162
font-weight: 1000;
163+
max-width: 400px;
157164
}
158165

159166
.hero-subext {

docs/cdk/index.md

Lines changed: 34 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1 +1,34 @@
1-
TODO: marketing copy and frontend design
1+
<div class="flex-figure" markdown="1">
2+
<div class="flex-figure-left" markdown="1">
3+
# Polygon CDK
4+
Polygon Chain Development Kit (CDK) is a modular, open source software toolkit for blockchain developers which supports the installation and configuration of a variety of chain architectures. Polygon CDK empowers developers to launch new L2 chains on [Ethereum](https://ethereum.org/en/) or, in the future, transition existing Layer 1 (L1) chains into L2s.
5+
</div>
6+
<div class="flex-figure-right">
7+
<img src="../img/cdk/cdk.svg" class="figure figure-right" alt="" />
8+
</div>
9+
</div>
10+
11+
Developers can select a chain architecture specific to their needs from a set of supported, open source components. Alternatively, developers can select custom components for specific requirements. The diagram below shows the two supported configuration options, rollup or validium. Rollups post transaction data from Polygon CDK directly onto Ethereum whereas validiums only post the transaction hash.
12+
13+
![](../img/cdk/overview-1.png)
14+
15+
A chain tailored for a specific application might leverage the zkEVM execution environment, adopt the Validium mode, and implement a centralized sequencer.
16+
17+
Regardless of these individualized choices, after the completion of the in-development interop layer, every chain will have the option to be interoperable with other Polygon network chains.
18+
19+
## Why build with Polygon CDK?
20+
21+
Polygon CDK gives developers a toolkit for sovereign and modular chain design, without sacrificing future interoperability with other L2 chains. Chains built with Polygon CDK can access an ecosystem of (forthcoming) unified liquidity, optimized performance, and seamless asset transfers, all while prioritizing user experience and data security.
22+
23+
Here is what developers can expect when they build with Polygon CDK.
24+
25+
1. **Modularity and sovereignty**: Polygon CDK offers a modular environment for ZK-powered L2 chain design. Developers can customize chains according to their needs.
26+
2. **Scalability**: Polygon CDK-developed L2 chains enhance transaction speed and can be multiplied to achieve an elastically scalable ecosystem.
27+
3. **Independent data availability**: With a dedicated data availability layer and a data availability committee, Polygon CDK-developed chains provide robust off-chain data access and reliability. This structure, independent of Ethereum, ensures substantial data resilience and integrity.
28+
4. **Interoperability (forthcoming)**: Through an in-development interop layer, CDK-developed chains can be seamlessly interoperable, meaning atomic L2 <> L2 transactions. Chains deployed with Polygon CDK will have the opportunity to opt-in to the interop layer and tap unified liquidity.
29+
5. **Near-instant finality**: Chains deployed using Polygon CDK rely on cryptographic security, ensuring transaction integrity without the need of full nodes. This approach guarantees near-instant finality and robust security.
30+
6. **Extensive Web3 support**: Polygon CDK chains leverage a comprehensive ecosystem with premium service providers offering essential tools for application integration, development, and deployment.
31+
32+
The following diagram illustrates how Polygon CDK-developed chains may opt into a web of interoperable L2 chains:
33+
34+
![](../img/cdk/overview-2.png)

docs/img/cdk/cdk.svg

Lines changed: 474 additions & 0 deletions
Loading

docs/img/home/cdk.svg

Lines changed: 0 additions & 81 deletions
This file was deleted.

docs/img/home/miden.svg

Lines changed: 0 additions & 110 deletions
This file was deleted.

0 commit comments

Comments
 (0)