Improve docs on howto join devnet about networks

[aditya-manit]

I wrote a guide, could be helpful: https://stakeking.notion.site/Join-Celestia-Devnet-2-d4c08af1d0534b3faca7aaa8c1e9266d

[Bidon15]

Now, we are only left with a guide for a standalone network setup for celestia application. 🥳

[Bidon15]

Super glad and excited that @yelllowsin is volunteering for the point 2
I'll be working mainly on point 1 and 3

[yelllowsin]

So, I created a new initial Node Setup MD file and sent the PR here: #55
I already tested it in a new VPS, so the instructions should be working. Since we will have a troubleshooting section that is separated, I am still thinking where I should add the extra commands for staking, checking validator, etc. Maybe here via another pull request or in the troubleshooting section.

[yelllowsin]

@Bidon15 I have made many improvements to the PR responding many if your comments. Also added an index :) Let me know what you think.

[Bidon15]

How the further docs will look like

1. We need to split the readme.md file to separate md files.

The initial readme will be a high-level overview of how things are interconnected to each other and contain links to other md files

2. It is clear that celestia-appd guide should be a separate md doc

---

What will be changed

1. After installation, Phase X should be standing first (not phase 1/2/3 as it is now) as most of the users are willing to join devnet-2 and not deploy their own network
2. Phase X should be divided into 3 categories
   2.1. Explanation part
   We need to make it clear that running a non-validator full celestia-appd node is much more preferable as the user doesn't need to put much attention into resolving validator type full nodes and focus on celestia node part later
   2.2. Running a non-validator full node (this is more then sufficient to play around later in celestia node part)
   what to add/change:

• how to delegate stake (where to find active validators and etc.)
• link to a troubleshoot section if the delegation of the stake is not working (we will think about this part later on)
  2.3. Running a validator full node (cart blanche)
  what to add/change:
• create-validator command

3. Legend + Phase 1/2/3
   TBH, I am proposing that we can separate this point into a standalone md file (for the brave ones 😅 )

---

3. Separate celestia-node into a separate md doc

Unprepared audience is having a hard time with how to work with celestia-node stuff (Full Nodes/ Light Clients), so we need to separate it to the other readme.md file

4. Troubleshooting and F.A.Q should be a 4th file

[liamsi]

how to delegate stake (where to find active validators and etc.)
link to a troubleshoot section if the delegation of the stake is not working (we will think about this part later on)

This ideally should also be somewhere at the top or very visible at least. As it is a very easy way to interact with the testnet. Same with "Running a non-validator full node".

[Bidon15]

I think checking validator should be in the troubleshoot section. Please add another PR 🙏
Same goes to sending funds from 1 addr to another (if through CLI)

[Bidon15]

Legend + Phase 1/2/3
TBH, I am proposing that we can separate this point into a standalone md file (for the brave ones 😅 )

I think we need to separate this point to a .md doc itself as history has shown that the small minority has been going through creating the own validator network