-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
we need to make a plan for automating the publishing of the documentation website #913
Comments
and #489 |
ok, great, looks like this is already covered, I'm not surprised, but since this came up during the typelevel summit, I wanted to make sure it was captured. Looks like snice we have good coverage on this, I'll close this one |
oh, however all those are closed. I'm reopening :) |
@stew, yep, those links were for reference only and this is definitely unfinished, so is an open issue. As a side note, there may also have been some discussion on documentation tools in general ( always have a TOC, use tool X instead of Y, align tools with org Z, etc); if so, this issue should most definitely be part of of that larger epic, IMHO of course. [ Hmm, I originally had a typo ^^ "As a snide note,....". What a difference that 'n' would have made ;) ) |
Fixed as of #4160. |
as brought up by @longcao we need to
[ ] automate the publishing of the documentation website with the build
[ ] publish multiple versions of the website
The text was updated successfully, but these errors were encountered: