Create subcategories. So in the explanation for step 1, create point 1.1, 1.2, 1.3 etc for every separate step. This makes it much easier to follow each step, is easy for your own use while creating the guide and helps for users to backtrack and ask questions about a (then numbered) subject. Also it helps for receiving feedback and improves readability.
Implement pauses between some of the steps to make people wait. I noticed during setup that sometimes things were not updated on the server yet, which made me think I did something wrong or I did not follow the guide well and then I already started looking for errors or wanting to correct things, while all was actually done correctly and in good order after waiting a minute or so for the server to update.
Additions:
At step 1.1 (unpacking tar) for me, using 7-zip, it was necessary to unpack the download and then unpacking the .tar file. So actually, with windows, it is necessary to unpack twice.
At step 1.5 (creating .cpk and .key) it might be handy already renaming the .key file into consensus.keys? In that case, people don't have to backtrack to that step and the consensus.keys file is already there.
At step 2.7 (or so, the one where Filezilla is used). It is easier to start with the download, install and running of Filezilla and after that, give the instructions. The way it is now it's kind of confusing. Also, if my second tip is good to implement, the consensus.keys file is already there so that would make it a very easy step.
One last suggestion: in the final edit, I would advise not using the fatprinted word every new alinea. It serves no purpose when using subcategories (1.1, 1.2 etc); multiple alineas can fall under under category which makes it way more uncluttered
Not much, just some small suggestions. Very well done guide @HDauven, very clear!
Improvement ease-of-use of node setup guide
Create subcategories. So in the explanation for step 1, create point 1.1, 1.2, 1.3 etc for every separate step. This makes it much easier to follow each step, is easy for your own use while creating the guide and helps for users to backtrack and ask questions about a (then numbered) subject. Also it helps for receiving feedback and improves readability.
Implement pauses between some of the steps to make people wait. I noticed during setup that sometimes things were not updated on the server yet, which made me think I did something wrong or I did not follow the guide well and then I already started looking for errors or wanting to correct things, while all was actually done correctly and in good order after waiting a minute or so for the server to update.
Additions:
At step 1.1 (unpacking tar) for me, using 7-zip, it was necessary to unpack the download and then unpacking the .tar file. So actually, with windows, it is necessary to unpack twice.
At step 1.5 (creating .cpk and .key) it might be handy already renaming the .key file into consensus.keys? In that case, people don't have to backtrack to that step and the consensus.keys file is already there.
At step 2.7 (or so, the one where Filezilla is used). It is easier to start with the download, install and running of Filezilla and after that, give the instructions. The way it is now it's kind of confusing. Also, if my second tip is good to implement, the consensus.keys file is already there so that would make it a very easy step.
One last suggestion: in the final edit, I would advise not using the fatprinted word every new alinea. It serves no purpose when using subcategories (1.1, 1.2 etc); multiple alineas can fall under under category which makes it way more uncluttered
Not much, just some small suggestions. Very well done guide @HDauven, very clear!