We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
What do you think about using readthedoc instead of gh-pages?
It's possible to trigger doc updating from the github repo to readthedocs.io.
readthedoc will automatically retrieve the doc source and build and publish the new one from github without manual handling:
readthedoc
Originally posted by @4383 in #21 (comment)
The text was updated successfully, but these errors were encountered:
@haraldh what's your opinion?
Sorry, something went wrong.
My main concern is, can we continue to use custom domain like https://varlink.org/python/?
https://varlink.org/python/
Apparently if I understood it correctly the answer is yes:
Then we will have a similar result than gh-pages, without the manual deployment part.
Maybe we will have a more recent CSS by default and anyway I suppose we can customize it somewhere and continue to display the current CSS if needed.
No branches or pull requests
What do you think about using readthedoc instead of gh-pages?
It's possible to trigger doc updating from the github repo to readthedocs.io.
readthedoc
will automatically retrieve the doc source and build and publish the new one from github without manual handling:Originally posted by @4383 in #21 (comment)
The text was updated successfully, but these errors were encountered: