Getting started update milestone 3

[pavlenex]

Alternative to #190
Closes #186

[netlify]

✅ Deploy Preview for startling-capybara-2231ea ready!

Name	Link
🔨 Latest commit	f7a1ab5
🔍 Latest deploy log	https://app.netlify.com/sites/startling-capybara-2231ea/deploys/65b7a1ff807f810008feeb5f
😎 Deploy Preview	https://deploy-preview-191--startling-capybara-2231ea.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[pavlenex]

Linkcheck is false (twitter firewall blocks the checker)

@plebhash @GitGab19 feel free to take a look when you get a chance. I am not sold on sidebar naming.structure but I guess we can rename those easily, structure-wise I am happy how things are nested.

[plebhash]

added a few suggestions

aside from them, LGTM

[plebhash]

CI seems broken though

[pavlenex]

Thanks for a thorough review and catching inconsistencies @plebhash! CI are triggered by false linkcheck since Twitter blocks it, as mentioned here good on that end, it's never reliable.

[pavlenex]

One thing missing in Google Doc and existing on a current guide is how to run a CPU miner. While we certainyl don't want to prioritize it, perhaps I could add it under "customization" or anywhere else. Up to you guys @plebhash @GitGab19

[GitGab19]

I made some suggestions to clarify better, a typo and other little things

[GitGab19]

Do we want to use SV2 or Sv2 here?

[pavlenex]

I think on the website we use SV2, so that's why, did we have a discussion around this, what's a preferred way?

[GitGab19]

I think on the website we use SV2, so that's why, did we have a discussion around this, what's a preferred way?

It seems to me that we are mixing it also on website.
In docs we use Sv2 and Sv1, everywhere else is SV2 and SV1.
I don't have an opinion on this, the important thing is to have it in a uniformed way imo

[pavlenex]

I think we should file a separate issue for it and fix it once there's consensus, Sv2 sounds good to me, but wouldn't block the progress of this PR over the linguistic.

[GitGab19]

I think we should file a separate issue for it and fix it once there's consensus, Sv2 sounds good to me, but wouldn't block the progress of this PR over the linguistic.

I agree with you.
Let's merge it 👍