tl;dr: I think most of those links are good, and they would easier to use if you organized them into a numbered outline or checklist that corresponds to the tasks people need to accomplish: shopping, building, software setup, and growing. You could omit the notes about revision dates.
Long version: As a starting point, rather than eliminating stuff or starting on a massive editing project, I would recommend picking one place–perhaps the readme on github, a wiki page, or whatever seems best–to organize the existing links with hardware and software documentation for the MVP. Then, once you have that, you could edit other places where those links are currently duplicated to just say something like, “for build, setup, and growing instructions, please refer to the documentation at [link to your official documentation place]”. Then, going forward, you would have one place to maintain rather than several. Maybe that’s what you meant by a “one-stop shop”–if so, that sounds good to me.
To take it a step further, you could organize the links into an outline (or checklist?) format with numbered sections. Your existing documentation is pretty good already, it’s just a bit challenging to navigate through it and talk about on the forum. As an example of something that’s working great, the slide numbers on your software installation slide deck are very helpful for conversations on the forum. Maybe you could extend the numbering concept to cover the whole procedure of shopping, hardware, software, and growing.
As for revising, reformatting, consolidating, etc. for the existing documentation after the old links are organized, I don’t have any strong opinions about it.