You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If this is done for every revision (i.e., new documentation deployment), the repo can grow to the point of becoming very inconvenient to clone, which has happened to https://github.com/HoTT/HoTT
Hence, the compromise we use in coq-community is to advocate deployment of documentation only for releases of a project, or putting documentation in a separate repo. Here is one example of a landing page: https://coq-community.github.io/lemma-overloading/
Any preferences here @chdoc, is the standard landing page OK with you?
The text was updated successfully, but these errors were encountered:
Deployment for every release should be sufficient, and the standard landing page looks fine for me. Indeed, the mathcomp landing page looks very similar. Once I have a bit more time, I might extend it with a library graph with clickable nodes (cf. our graph theory development), maybe even though an extended alternative template.
As per #7, we can use the
gh-pages
branch of the repo to deploy static HTML, which will then appear at the URL https://coq-community.github.io/reglangIf this is done for every revision (i.e., new documentation deployment), the repo can grow to the point of becoming very inconvenient to clone, which has happened to https://github.com/HoTT/HoTT
Hence, the compromise we use in coq-community is to advocate deployment of documentation only for releases of a project, or putting documentation in a separate repo. Here is one example of a landing page: https://coq-community.github.io/lemma-overloading/
Any preferences here @chdoc, is the standard landing page OK with you?
The text was updated successfully, but these errors were encountered: