Polygon edge documentation is down

[alfarkas]

[ Documentation ]

Description

Polygon edge documentation is down since the release of v0.8 (supernets).

Steps to reproduce

• Go to https://wiki.polygon.technology/docs/edge/
• You can see a "Page Not Found" error message, this happens with any page of the polygon edge documentation, even tho you can still search for stuff from that documentation and find results, but when you click on it, you get the "page not found" message.

[lucaspan]

Can you reopen the archived page so we can back it up as we are currently running on v0.6.3?

[salmad3]

Hi @lucaspan, thanks for raising this.

The source of the archived edge docs are still available in the repo, here. We had decided to put them in archive mode and not continue hosting them on the Polygon Wiki. Here is an example of a notice on the new Supernet docs:

Before diving into the documentation, please keep the following points in mind:

Polygon Supernets were officially introduced in v0.7.x of the Polygon Edge client.

The Polygon team will prioritize the latest version of the Edge client and as a result, will no longer provide support for older versions (v0.6.2 and earlier).

The repository will remain accessible, and users may fork it and use it as they wish, subject to applicable open-source license terms. It is highly recommended to upgrade to the latest version, which includes the most up-to-date features and fixes. However, users who prefer to stay on older versions may continue to do so.

Polygon Edge serves as a consensus client implementation for Polygon Supernets, much like how Geth serves as a client implementation for Ethereum.

Both geth and Edge serve as intermediaries between nodes and their respective blockchains, allowing users to interact with the network and take advantage of its benefits. To draw an analogy, Geth and Edge are to Ethereum and Supernets what web browsers are to the internet, enabling users to access and interact with the network.

The intent was to redirect the old endpoints to the new Supernet docs, which we can fix, or what I think would be better is to redirect them to the actual source of the archived edge docs on GitHub.