-
Notifications
You must be signed in to change notification settings - Fork 656
Start to add lots of documentation #899
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Start to add lots of documentation #899
Conversation
Hey @carols10cents, here are my cleaned up notes from going through the layout of my working directory. I have this as Repo File LayoutBackend
Front End
Deployment - Heroku
Development
Other
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm... could we look at removing "The" in front of the headers in docs/ARCHITECTURE.md
that refer to backend modules? There's a lot of them :)
docs/ARCHITECTURE.md
Outdated
|
||
#### The `utils` module | ||
|
||
### Code having to do with managing a registry of crates |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, not quite sure where you're referring to with this?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure why you're not sure :) What are the possible interpretations that you're deciding between? Note that this has an h3
, and the h4
s from line 102 to 126 are under this heading, does that help? What would be a better heading?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was trying to figure out how this fit into one module, yes I didn't see the h3
for it compared to the h4
's that refer to specific modules :)
Thanks for starting on this @carols10cents, the structure of the document itself looks good, though I think we should mention that it's specifically for the backend. Maybe we could look into having a similar document for the front end too? Also, maybe we could look at adding a diagram of the database schema? |
Yeah, I have a heading in there for backend and I think I just got tired before making a corresponding frontend heading :)
🤷♀️ That's how I'd talk about them though... "Where's the code to do x?" "it's in the
I'd be into that, if there's a tool we can use to automate creating the diagram and if we keep it up to date :) Do you know of a good one? |
6c831d6
to
380704b
Compare
380704b
to
4c43811
Compare
Ok -- I've incorporated @jtgeibel's repo layout docs and took @vignesh-sankaran's suggestion to break this out into separate backend and frontend documents-- I could see this getting long :) WDYT? |
docs/ARCHITECTURE.md
Outdated
|
||
[conduit]: https://crates.io/crates/conduit | ||
|
||
These files have to do with the backend: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
How about "these files and directories"?
|
||
Documentation about the codebase appears in these locations: | ||
|
||
* `LICENSE-APACHE` and `LICENSE-MIT` - the terms under which this codebase is licensed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like package.json
only lists MIT. I'm not sure if that is an oversight or if we need to word this more carefully. We should probably explicitly call out dual licensing in README.md
I've addressed the two things yinz pointed out, and in the interest of getting this merged so that we can all start working on this, and because this is all just docs, I'm going to merge my own PR 😎 bors r+ |
899: Start to add lots of documentation r=carols10cents I started this a while ago, but an email from @vignesh-sankaran prompted me to get what I have out there rather than bitrotting on my machine. I'd love a review of what I have so far, @vignesh-sankaran! What do you think of the outline of the architecture document? What kinds of things would make that document a more useful high-level overview? The doc comments should hopefully make the docs at https://docs.rs/cargo-registry/ better, I don't think the little bit I've added here warrants a version bump and publish yet, though.
Build succeeded |
I started this a while ago, but an email from @vignesh-sankaran prompted me to get what I have out there rather than bitrotting on my machine.
I'd love a review of what I have so far, @vignesh-sankaran! What do you think of the outline of the architecture document? What kinds of things would make that document a more useful high-level overview?
The doc comments should hopefully make the docs at https://docs.rs/cargo-registry/ better, I don't think the little bit I've added here warrants a version bump and publish yet, though.