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
Following up from issues discovered when authoring and merging #678
images/*.png, .eps, ...
.md
.png
.pdf
.eps
There is no real reason that we should have low-resolution rasterized graphics like the following, when they were created by ANL folks: https://docs.alcf.anl.gov/aurora/images/aurora_node_dataflow.png
at a minimum, user higher resolution PNGs
aurora_node_dataflow.png PNG 1134x565 1134x565+0+0 8-bit sRGB 64032B 0.000u 0:00.001
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Following up from issues discovered when authoring and merging #678
images/*.png, .eps, ...
that are currently stored in the repo are linked to by an.md
file. Related Need better solution for storing large/many binary assets that arent hosted on main ALCF site #533.png
diagrams with vector graphics.pdf
or.eps
versions when possible, especially node diagrams (Add node diagrams to "Machine Overview" pages; move Aurora to top of Machines section in sidebar; move Machine Overview to top of each system dropdown before/after Getting Started page #657)There is no real reason that we should have low-resolution rasterized graphics like the following, when they were created by ANL folks:
https://docs.alcf.anl.gov/aurora/images/aurora_node_dataflow.png
at a minimum, user higher resolution PNGs
The text was updated successfully, but these errors were encountered: