Sort out assets in Community directory #14

Closed
opened 2023-09-05 12:55:29 +00:00 by dadofsambonzuki · 4 comments
dadofsambonzuki commented 2023-09-05 12:55:29 +00:00 (Migrated from github.com)

Sort out large and missing assets.

No more than 150x150.

Useful tool: https://github.com/imagemin/imagemin-cli

Sort out large and missing assets. No more than 150x150. Useful tool: https://github.com/imagemin/imagemin-cli
dadofsambonzuki commented 2023-09-05 12:58:37 +00:00 (Migrated from github.com)

@bubelov - Pls could you get a complete list of missing or inappropriately large community assets?

@bubelov - Pls could you get a complete list of missing or inappropriately large community assets?
bubelov commented 2023-09-07 04:45:06 +00:00 (Migrated from github.com)

@dadofsambonzuki they aren't in the DB so there is no easy way to find the missing assets. As for the large images, I think @secondl1ght has a script which is supposed to handle that

@dadofsambonzuki they aren't in the DB so there is no easy way to find the missing assets. As for the large images, I think @secondl1ght has a script which is supposed to handle that
secondl1ght commented 2023-09-07 13:20:04 +00:00 (Migrated from github.com)

An easy way to check for missing assets is to go to the Directory page on the site and go through each community section with the browser console open. You will see the 404 requests in there. imagemin is a good CLI tool to reduce the file size of images but it doesn't do any resizing of dimensions AFAIK. If not there is probably another tool we can use for that. Best way to do it would be pull assets locally and do the optimizing there rather than on the prod server I think. Then replace them when ready.

An easy way to check for missing assets is to go to the Directory page on the site and go through each community section with the browser console open. You will see the 404 requests in there. imagemin is a good CLI tool to reduce the file size of images but it doesn't do any resizing of dimensions AFAIK. If not there is probably another tool we can use for that. Best way to do it would be pull assets locally and do the optimizing there rather than on the prod server I think. Then replace them when ready.
dadofsambonzuki commented 2024-05-07 13:57:47 +00:00 (Migrated from github.com)

Automated via the netify CDN tools.

Automated via the netify CDN tools.
Sign in to join this conversation.
No description provided.