-
Notifications
You must be signed in to change notification settings - Fork 12
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
Documentation hosting #31
Comments
Hello, When you say documentation you mean the doc generated by tools like rustdoc ? |
Yes |
It's not easy to do because if I'm not wrong Meuse would have to:
|
Hello, @mcorbin are you sure this is the case? I think that Meuse already has the required access in its crate storage - the file stored there is just a tar.gz archive that can be extracted. Cargo dependency is a bit less fortunate but still, it could be optional. To be honest, I don't think meuse should serve documentation, but still this way it could extract and render README.md if present. What do you think? |
The README content is actually available in the metadata passed alongside the crate when it is published, I just do nothing with it today. |
Do you think it could be a nice issue for a new contributor, like me for example? |
I think so. I reread the code, and the README is actually already stored in the DB. These metadata are already retrieved and available to be used in the frontend. It's how we show the crates dependencies in the frontend today: https://github.com/mcorbin/meuse/blob/master/src/meuse/front/pages/crate.clj#L120 adding an html block containing the readme if defined (which is stored into the metadata in the Btw, I'm not a frontend developer so at some point I would like to find some dev specialized in frontend work to rewrite the Meuse frontend from scratch ;) |
Hello again,
It's more a question, but can be a great feature ...
Do you think meuse can generate and host the Rust documentation of projects ?
Marc-Antoine
The text was updated successfully, but these errors were encountered: