Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Add better documentation for how to build hosted documentation
See original GitHub issueCopying from another issue ticket, we can improve our static documentation for how to build our generated documentation
The only thing that might be more helpful is updating the instructions a bit under Building documentation with Docker to let contributors know they have to rebuild with the --docs command after changes and the index.html file has to be dragged and dropped into the browser.
_Originally posted by @ari-hacks in https://github.com/arviz-devs/arviz/issues/1155#issuecomment-662350572_
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:16 (14 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I think we can do it in the same PR, but I don’t have strong preferences on this
Indeed, https://github.com/arviz-devs/arviz/blob/master/scripts/container.sh#L38 should be:
The conf.py file used to be on
doc/but was moved todoc/sourceso now it’s not found anymore by the script because it’s still looking at the old location.Azure CI script was updated https://github.com/arviz-devs/arviz/blob/master/.azure-pipelines/azure-pipelines-docs.yml#L60-L61 and can serve as an example to compare against when things don’t work