First pass at documentation for adding/changing hero images#402
Conversation
Per Phil. He stated that such documentation should be in markdown on circuitpython.org itself. In this PR, no accompanying images are used. If images are desired, we will need to determine where to put them. Under /assets or under /doc or somewhere else.
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 32.6%, saving 4.07 MB
Some images were already optimised
|
|
I didn't ask GitHub to do anything with the images, must be automatic..... |
|
It is! And it's ok for this PR I think, it's simply optimizing the file sizes (the new heroes are much smaller). The issue I think is that normally it doesn't run properly as we push forked PR from our own repositories, so it suddenly has a bunch of images to optimize from previous pull requests. I'll look into that, as I'd like it to optimize images on each PR that comes in with new images. |
|
Added reviewers as PT stated he would look at it after merge in a basecamp message. |
kattni
left a comment
There was a problem hiding this comment.
Looks good! One formatting note below.
|
Images automagically compressed by Calibre's image-actions ✨ Compression reduced images by 78.8%, saving 601.10 KB
Some images were already optimised
|
|
@TheKitty You'll need to deal with the merge conflicts but otherwise this is ready to merge when you're ready. |
Per Phil. He stated that such documentation should be in markdown on circuitpython.org itself.
In this PR, no accompanying images are used. If images are desired, we will need to determine where to put them. Under /assets or under /doc or somewhere else.