Closed joewheaton closed 5 years ago
Just to clarify... one quick thing to fix this is simply take every image in the assets folder and run through tinyPNG. You can only do 20 at a time (for free), but this will reduce each one on order of 50 to 80% filesize... which helps a lot.
@BrittGraham I am assigning you with this task that Joe has defined above. Let's make this your highest priority. Don't worry too much about the beaver dam censusing because I'm planning on hiring Work Study Techs to this work. Please confirm that you we'll take this task on and let us know if you have any questions. Thanks!
Will do!
Hi @BrittGraham, I noticed that you were working on this task. Please provide a status report when you get a chance. Thank you.
@wally-mac I have resized all the images and used tingPng on them. Tomorrow I'm going to work on putting the three different sections of images on a different webpage, and make the images clickable. Then the users can see them in full screen.
I have finished putting all the images into different sub-pages, and are now clickable to view them in full.
Nice work!
On Thu, Jan 31, 2019 at 1:37 PM BrittGraham notifications@github.com wrote:
I have finished putting all the images into different sub-pages, and are now clickable to view them in full.
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/Riverscapes/pyBRAT/issues/259#issuecomment-459497214, or mute the thread https://github.com/notifications/unsubscribe-auth/AU-QUvZzhIEOaqQgUAG_RJEr40cNbBAtks5vI1P1gaJpZM4aUZUG .
-- Sent from Gmail Mobile Sorry for typos and brevity courtesy of my phone.
Hi guys, After browsing this Burnt River page, I noticed how poorly the performance of site is. The reason for this is you guys are uploading way too many full resolution versions to one page. There are two ways around this, 1) split out things to more subpages, and 2) tinify the images!
So its great we're getting our documentation sorted out. However, you guys need to follow the Documentation Standards. I didn't write these for my sake! Read them. One of these documentation standards, is to use tinyPng for ALL images that we host on site (and found in Assets folder). These gitHub hosted pages ARE NOT meant to be dumping grounds for large files and images. If you want the full resolution versions, post them on AWS and provide a URL to them such that when someone clicks on image, the full resolution version opens from AWS. Also, use sub-pages to break up all the scrolling.
The content is getting up there, which is good and appreciated, but lets make sure we don't slow down site by not following those documentation standards.
Best Wishes, Joe