-
Notifications
You must be signed in to change notification settings - Fork 9
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
Package Documentation Brainstorm #6
Comments
For the record, I've come to the conclusion that it's a bad idea to host package version coqdoc inside a GitHub repo, e.g., in a
|
I don't think we need to do anything about documentation. Most (all?) packages already have a Also, limiting the platform documentation to only the things generated by coqdoc would be a net regression, especially for people who actually bother writing some structured documentation, e.g., https://flocq.gitlabpages.inria.fr/theos.html |
Fine by me if some packages generate their own documentation and make it available through But for Platform packages, I think documentation should be handled in a consistent way, e.g., |
IMO the best option is to let git*.com host the doc, and provide tools and templates to help people set things up. |
We need to think about how we want to handle package documentation and linking to it from the website
The text was updated successfully, but these errors were encountered: