Create project documentation in markdown using `mdbook` about rust-pip HOT 4 OPEN

@John15321 Hey John! Just want to clarify the difference between this and and writing comments in the code and running cargo doc

Also, do I just create the general structure first or is there already information you would like to be inside?

Thanks!

https://youtu.be/tXWscUSYdBs

You can watch the first 17 minutes to get a better understanding.

In short the documentation generated by cargo doc is a so called API documentation or reference documentation or whatever people like to call it. It's minimalistic and purely based on the source code. On the other hand the one by mdbook is meant to be more abstract and fully carted to a human reader. It should perform the role of a usage guide, a guide in general, etc

You can look at the cargo-generate project to get a feel

from rust-pip.

I'll work on this! Will get it done by this week.

from rust-pip.

I'll work on this! Will get it done by this week.

Thanks. No rush, its not a race. Noone is trying to chase us with their own rewrite of pip in Rust, the point is to do this right not fast ;)

from rust-pip.

@John15321 Hey John! Just want to clarify the difference between this and and writing comments in the code and running cargo doc

Also, do I just create the general structure first or is there already information you would like to be inside?

Thanks!

from rust-pip.