-
Notifications
You must be signed in to change notification settings - Fork 38
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
images in package descriptions not imported/ rendering #77
Comments
Good catch! Yes, I think this would have to be caught and processed on https://github.com/pysal/notebooks/blob/master/lib/build.py#L216 Maybe that method should also include a check for |
Since we are likely to uncover other issues that should be standardized across subpackages, we should document these here. |
+1 i was going to say something similar since we dont have any conventions currently as to where those images are stored. Would make things easy if we can just grab the |
Yes, it might be worth sorting out those standards first and then pulling them into the notebooks project? |
There are likely to be other, similar, issues that we probably want to document in the su
I think so. We use the notebooks project to smooth the rough edges and discover best practices. Then we codify in the submodule instructions. |
I noticed that most packages have a static image in their
README.md
which is not rendered in the notebook book. I suppose due to the images not being imported in this repo/ and the image links being broken since the hard-coded image path changed.It seems like GitHub markdown does not really support absolute image paths, so maybe it is possible to pull the images in this repo as well?
The text was updated successfully, but these errors were encountered: