Skip to content
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/guides/deploy/local.md
Original file line number Diff line number Diff line change
Expand Up @@ -216,7 +216,7 @@ Since our chain is running in a docker container, we want to enter the docker co
docker exec -it gm-world sh
```

Now that you are in the docker container, you can interact with the chain using the `gmd` command and the example you used in the [gm-world tutorial](/docs/guides/gm-world.md).
Now that you are in the docker container, you can interact with the chain using the `gmd` command and the example you used in the [gm-world tutorial](/guides/gm-world.md).

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Thanks for fixing this link. I noticed a couple of other links in this file were missed. For example, on lines 3 and 20, the links still use the old /docs/... path. It would be great to fix all of them in this file for consistency.


Once you are done interacting with your chain, you can exit out of your docker container with:

Expand Down
2 changes: 1 addition & 1 deletion docs/guides/deploy/overview.md
Original file line number Diff line number Diff line change
Expand Up @@ -6,7 +6,7 @@ description: This page provides an overview of some common ways to deploy chains

One of the benefits of building chains with Evolve is the flexibility you have as a developer to choose things like the DA layer, the settlement scheme, and the execution environment.

You can learn more about Evolve architecture [here](/docs/learn/specs/overview.md).
You can learn more about Evolve architecture [here](/learn/specs/overview.md).

The challenge that comes with this flexibility is that there are more services that now need to be deployed and managed while running your chain.

Expand Down
12 changes: 6 additions & 6 deletions docs/guides/deploy/testnet.md
Original file line number Diff line number Diff line change
Expand Up @@ -2,7 +2,7 @@

This tutorial is going to show you how to deploy a Evolve testnet, focusing on the architecture choices and components that make up a complete EVM-based chain deployment.

You can learn more about Evolve EVM architecture [here](/docs/learn/execution.md).
You can learn more about Evolve EVM architecture [here](/learn/execution.md).

<!-- markdownlint-disable MD033 -->
<script setup>
Expand Down Expand Up @@ -90,7 +90,7 @@ graph TB

## 💻 Pre-requisites {#prerequisites}

Make sure you understand the sequencing topology you want to use by reading the [Sequencing Overview](/docs/learn/sequencing/overview.md).
Make sure you understand the sequencing topology you want to use by reading the [Sequencing Overview](/learn/sequencing/overview.md).

## 🛠️ Dependencies {#dependencies}

Expand All @@ -107,7 +107,7 @@ Currently, Evolve supports one sequencing implementation:
- **Advantages**: Easy setup, fast block production, independence from DA block time
- **Requirements**: One sequencer node, multiple optional full nodes

For detailed information about sequencing topologies, see the [Sequencing Overview](/docs/learn/sequencing/overview.md) and [Single Sequencer](/docs/learn/sequencing/single.md) documentation.
For detailed information about sequencing topologies, see the [Sequencing Overview](/learn/sequencing/overview.md) and [Single Sequencer](/learn/sequencing/single.md) documentation.

## 🏗️ Deployment Architecture {#deployment-architecture}

Expand Down Expand Up @@ -300,8 +300,8 @@ Congratulations again! You now know how to deploy Evolve EVM chains and understa

For detailed setup instructions, see:

- [Single Sequencer Setup Guide](/docs/guides/evm/single.md) - Step-by-step deployment instructions
- [RETH Backup Guide](/docs/guides/evm/reth-backup.md) - Data protection and backup procedures
- [Celestia DA Guide](/docs/guides/da/celestia-da.md) - Connecting to Celestia networks
- [Single Sequencer Setup Guide](/guides/evm/single.md) - Step-by-step deployment instructions
- [RETH Backup Guide](/guides/evm/reth-backup.md) - Data protection and backup procedures
- [Celestia DA Guide](/guides/da/celestia-da.md) - Connecting to Celestia networks
Comment on lines +303 to +305

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

Good catch on these links. I noticed that the link on line 307, just below this list, appears to have been missed. It still points to /docs/guides/deploy/local.md and should probably be updated to /guides/deploy/local.md to align with the other changes in this PR.


You can also learn more about local deployments in our [Docker Compose guide](/docs/guides/deploy/local.md).
10 changes: 5 additions & 5 deletions docs/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -15,22 +15,22 @@ hero:
actions:
- theme: brand
text: Quick start
link: /docs/guides/quick-start
link: /guides/quick-start
- theme: alt
text: Introduction
link: /docs/learn/about
link: /learn/about

features:
- title: Full Control Over Execution
details: Design your network exactly how you want it. Choose your VM, customize your execution environment, and maintain complete control without middlemen or revenue share.
link: /docs/learn/about#why-evolve
link: /learn/about#why-evolve
icon: 🚀
- title: Speed to Traction
details: Get to market fast with infrastructure that adapts to your app—not the other way around. Skip the complexity and start building what matters; your product.
link: /docs/learn/execution
link: /learn/execution
icon: ⚡
- title: No Validator Overhead
details: Skip the complexity of running validators. Focus on building your application while Celestia handles consensus and data availability.
link: /docs/learn/about
link: /learn/about
icon: 🛡️
---
Loading