You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It's important to provide clear documentation of the Ignite Chain for the launch coordination part to support the network commands documentation under https://docs.ignite.com/network/introduction for advanced users to understand how the commands work
I propose to integrate the documentation we have in Whitepaper-1 file into a section Ignite Chain under https://docs.ignite.com/network
We keep the section named Network, this is the documentation for the ignite network commands.
The first subsection is Ignite Chain, this introduces the ignite network commands by presenting the Ignite Chain, the "backend" for the commands, then the second subsection introduces the actual commands.
In the future, when the whitepaper will start to look like an actual whitepaper for a chain, we can move the content for the chain into a dedicated page for it with the full whitepaper
It's important to provide clear documentation of the Ignite Chain for the launch coordination part to support the
network
commands documentation under https://docs.ignite.com/network/introduction for advanced users to understand how the commands workI propose to integrate the documentation we have in
Whitepaper-1
file into a sectionIgnite Chain
under https://docs.ignite.com/networkI would prefer not to break the https://docs.ignite.com/network/introduction link shared in many place, so what I'm thinking about is:
We keep the section named
Network
, this is the documentation for theignite network
commands.The first subsection is
Ignite Chain
, this introduces theignite network
commands by presenting the Ignite Chain, the "backend" for the commands, then the second subsection introduces the actual commands.In the future, when the whitepaper will start to look like an actual whitepaper for a chain, we can move the content for the chain into a dedicated page for it with the full whitepaper
@fadeev @aljo242 @ilgooz @scottcarterco
The text was updated successfully, but these errors were encountered: