Refresh the whole docs site

[MTFT-Games]

General:

• [x] Enable auto table of contents
• [x] Enable auto2top
• [ ] Proofread all content to ensure it is readable and grammatically correct.

Cleanup:

• [x] Remove random unnecessary stuff
• [ ] Fill or remove any empty pages
• [x] Remove sections that are now redundant
• [ ] Restructure sidebar / site
• [x] Remove old library page now that it gets pulled directly from the repo

Styles:

• [x] Replace current logo with the one that has text
• [x] Set the theme back to being from a cdn
• [x] Improve the "Edit on Github" button

Content:

• [x] Add a readme to the docs site
• [x] Make the site pull readme files from the other devcade repos
• [x] Add info to the home page
• [x] Update contribution guide
• [ ] Review all content to ensure accuracy and sufficient detail
• [x] Add the docs site readme to the docs site
• [ ] Confirm all links are working
• [x] Add links to all repos (beyond the edit button)
• [ ] Add links between pages where appropriate
• [ ] Add more content to first-game.md
• [ ] Add content to cabinet.md (cad files, parts list, cost breakdown, links, etc)
• [ ] Add content to gamepad.md (parts list, cost breakdown, links, etc)
• [ ] Add pages explaining how to make a devcade game in other languages/programs/engines (at least the ones that people have made games with so far)
• [ ] Add instructions/documentation for using cargo devcade

Devcade Install Guide (@esoccoli):

• [ ] Remove all references to CSH specific aspects of the setup (ie: csh.rit.edu hostname, mentions of RTPs/Devcade Admins, etc)
• [ ] Add info about configuring openbox
• [ ] Add more headers and subheaders to make it easier to follow.
• [ ] Maybe restructure and/or reword certain things to make it easier to follow
• [ ] Make sure that the onboard will actually compile and run on this setup
  • [ ] If it doesn't, figure out why and add instructions for what needs to be done so it can run

[esoccoli]

Specific changes to make

• [ ] Add more detail to the "Making your first devcade game" page
• [ ] Update content of the onboard readme (it is comically out of date)
• [ ] Fix the link to (and possibly update content of) the "Using the Game Template" page
• [ ] Add more detail to the hardware overview page
• [ ] Add content to or remove the "Cabinet" page
• [ ] Add content to or remove the "Gamepad" page
• [ ] Add headings to the "Installing DCU" page
• [ ] Update all links in the "Internals" section
• [ ] Possibly add more detail to the "API" page
• [ ] Possibly add more detail to the "Monogame Game Template" page
• [ ] Possibly add more detail to the "Flatpakify" page

[MTFT-Games]

@esoccoli Some notes on the new install guide: In addition to adding headers as you mentioned above, I would like to see it formatted more like a walk through or guide like the old one was. Similarly, I've been trying to format the docs site with general information for anyone that might in the future want to make their own Devcade. To this point I would like to avoid specifying details specific to our instance of Devcade such as the dcu.csh.rit.edu hostname or referencing RTPs/Devcade Admins. These belong better on our wiki I think. Do we need to specify mary's fork of flatpak still? or have the changes we need trickled down to the standard package yet? We include an openbox config with the onboard, we could just add the volume control config to that... Or maybe as a separate PR.

[MTFT-Games]

@esoccoli Thoughts on not having the using-template page and instead just including that info in the readme of the template itself?

[esoccoli]

Id be fine with that. Most of the content is kinda just a repeat of what is in the readme of the template anyway

[esoccoli]

What I will say is that i can't guarantee that the onboard will actually launch after you finish following the instructions in the install guide. I was trying to test that, and it kept giving me errors, and I couldn't figure out why, and didn't really have the time to look into it too much.