frc-docs
frc-docs copied to clipboard
KOP Item resources
Copied from #25.
I would appreciate any thoughts on @firecrafty's original questions:
Feedback on how to organize this/where to put things would be great, I thought putting them in their own large section would be the right move but I'm not sure anymore as I don't want the sidebar to get too cluttered.
- [x] vmx-pi
- [x] Mechanical
- [x] motors
- [x] pneumatics
- [x] robot quick build (put in benchtop section?)
- [x] sensing (combine with @Oblarg's sensors section?)
- [x] software
- [x] wiring/connections
- [x] other
Edit: I'll be away from the internet for two weeks (back on August 11th) and I plan to continue working on this PR when I return.
@Daltz333 Should kop-item-resources move from docs/hardware/kop-item-resources to docs/kop-item-resources?
Definitely keep it in hardware
Can someone help me figure out why the build is failing? Is it an Azure thing or something to do with this PR?
Some mathematical symbol that is included that the PDF generation doesn't like. Try to use the UTF versions of symbols and minimize latex usage
(This page is the Multisim page, not the whole PR)
The Kop should be a section under hardware. Adding each individual (hardware related) section to the main toc makes the sidebar substantially longer with little gain. Looking at things further, I see no need to even call it "Kit of Parts" (this will still make the sidebar longer, but with a benefit at least). My thoughts are, with your current organization scheme, that things can then be added to each section. (motors to motors).
@Daltz333 Anything else?
@AustinShalit Please review.
@Daltz333 How do you feel about moving the content located inside of the zip files out of the zip files?
We're getting those zip files moved to other locations, and then this should be ready for merge.
Can someone rebuild this PR?
The pull-request failing is accurate, kauai-kabs with the sub-domain vmx-pi no longer exists (the http version will redirect, and the https will fail with an invalid certification error).
The kauai labs webpage keeps going offline. I'll be contacting them about this. However, I don't see any issues with the links any more. @AustinShalit would you mind retriggering this build?
It seems to have succeeded. Would you mind fixing the last couple of redirects?
I think I fixed all the redirects and added links to https://first.wpi.edu/FRC/roborio/Docs/ where applicable. Could you also upload L4TMultimediaAPIReference.zip to https://first.wpi.edu/FRC/roborio/Docs/? It belongs in docs/hardware/sensors/jetson-tx1-developer-kit.rst line 65.
Was that link previously hosted on ScreenSteps as well?
The file was linked on NVIDIA's website. The link label is "Multimedia Guide" and you can find it under the Documentation heading on ScreenSteps.
Just use the original link then
Sounds good. Any other suggestions?
Waiting on review from the individuals who put together the kit of parts.
Can someone rebuild this PR? I tried running make linkcheck locally and I don't see any errors.
@Daltz333 Any updates on this PR?
This is waiting on more information from the KOP team.
I was just reviewing the changes this PR makes to the navigation sidebar. Would it be better to move all the Kit of Parts resources to one super-folder which has an index for all the KOP sub-categories (Sensors from the KOP, Control, Mechanical, Motors, Pneumatics, Robot Quick Build, Wiring & Connections and Other) to avoid adding too much to the navigation bar?
@yellowjaguar5 now with the revision, I agree.
One of the LintCheck builds failed, but not the other one. Huh.
Is this all fine to merge then?
Will probably have merge conflicts though.
I want to add source files for the illustrations I created per @Daltz333's comment in #200 and then I think it will be mergeable. It would be great if this PR could get a review, though.
We are planning on adding a lot more KoP content this season and the people doing it are more comfortable doing so in Screensteps than in RTD so our current plan is to leave all KoP content on Screensteps for this season.
@yellowjaguar5 Mind updating this for the current season?