The setup guide has been implemented and a lot of changes in different places have been made, this includes old and inaccurate guides made more clear with images and better explanations in the wiki.
Issue: Make the setup guide more user-friendly (on wiki, optionally also pdf and a video) #9
Type of change
[X] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
How Has This Been Tested?
Followed the setup guide for the wiki and it kept updating each time a new change was detected therefore issues in the cmd would not let the page load which never happened.
Checklist:
[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas, if necessary
[ ] I have made corresponding changes to the documentation, if necessary
[X] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works, if necessary
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules
[ ] I have Acceptance Tested this on an iOS device
[ ] I have Acceptance Tested this on an Android device
Description
The setup guide has been implemented and a lot of changes in different places have been made, this includes old and inaccurate guides made more clear with images and better explanations in the wiki.
Issue: Make the setup guide more user-friendly (on wiki, optionally also pdf and a video) #9
Type of change
How Has This Been Tested?
Followed the setup guide for the wiki and it kept updating each time a new change was detected therefore issues in the cmd would not let the page load which never happened.
Checklist: