-
Notifications
You must be signed in to change notification settings - Fork 1
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
[FR] Build develop
docs
#3
Comments
GitHub pages can only serve one domain, so we would need a second repository to serve the dev docs under a different domain. I forked this repo @ https://github.com/capital-G/sc-docs-dev and deployed it to https://dev.docs.supercollider.online/ We could add this repository as well into the supercollider organization if there is agreement that this should be a thing. I think this is a very nice idea, maybe we should also build it every day instead of just every week. |
Thanks! It's helpful to already have this up and running. I'll update the README to make a note of it. I think it makes sense to add it to the SC org given there's relatively little overhead with the "main" docs already there, but let's see what others say. At the moment, I don't have a preference between daily and weekly builds. Thanks! |
@mtmccrea should we transfer the dev-docs repo to the SC organization? |
I would be in favor of that! Do you see any disadvantage of having it build daily rather than weekly? Things have picked up pace lately (thanks to your efforts!) so in times like these it can be good to view/share changes from the website that are more current. |
It's great having up-to-date docs, this will be a big help!
I'm wondering if there's a solution to also serve up the latest version of docs from the
develop
branch (under a separate URL)?While this wouldn't be the primary docs to point users too, it could be useful to reference in the context of development discussions (on PRs and Issues) and communicating upcoming changes to users as it comes up in conversation on the forums.
The text was updated successfully, but these errors were encountered: