Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Some of the PNGs in assets/images are not optimized #298

Closed
Protectator opened this issue Oct 8, 2020 · 2 comments
Closed

Some of the PNGs in assets/images are not optimized #298

Protectator opened this issue Oct 8, 2020 · 2 comments
Labels
engineering Will involve Docs Engineering

Comments

@Protectator
Copy link
Contributor

Protectator commented Oct 8, 2020 •
edited
Loading

What article on docs.github.com is affected?

Multiple articles display PNG images that have not been optimized/losslessly compressed.

What part(s) of the article would you like to see updated?

Using lossless compression on all of these PNGs could reduce their size, saving bandwidth and accelerating their loading time. Most of them are fine already, but some could really benefit from a pass of lossless compression.

Additional information

Lossless compression doesn't take away any quality of the image, so I don't see any drawback at all replacing unoptimized PNGs with optimized ones.
@welcome
Copy link

welcome bot commented Oct 8, 2020

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Oct 8, 2020
@Protectator Protectator mentioned this issue Oct 8, 2020
Merged
4 tasks
@janiceilene janiceilene added engineering Will involve Docs Engineering and removed triage Do not begin working on this issue until triaged by the team labels Oct 9, 2020
@Protectator
Copy link
Contributor Author

It's been resolved by #299

@snyk-bot snyk-bot mentioned this issue Jul 30, 2021
Open
@zipzip225 zipzip225 mentioned this issue Nov 25, 2023
Open
@ramsemune ramsemune mentioned this issue Nov 25, 2023
Open
@bee22193 bee22193 mentioned this issue Nov 26, 2023
Open
@shga1993 shga1993 mentioned this issue Nov 27, 2023
Open
@Verdinjoshua26 Verdinjoshua26 mentioned this issue Nov 27, 2023
Open
@makombelajob makombelajob mentioned this issue Nov 27, 2023
Open
@smilers smilers mentioned this issue Nov 27, 2023
Open
@muratkalenderoglu muratkalenderoglu mentioned this issue Nov 28, 2023
Open
@Oleksandr1201vsp Oleksandr1201vsp mentioned this issue Nov 28, 2023
Open
@DSBUGAY2 DSBUGAY2 mentioned this issue Nov 28, 2023
Open
@Sarrac3873 Sarrac3873 mentioned this issue Nov 28, 2023
Open
This was referenced Nov 28, 2023
Open
Open
@kabat87 kabat87 mentioned this issue Nov 28, 2023
Open
@francissimo francissimo mentioned this issue Nov 28, 2023
Open
@abood640 abood640 mentioned this issue Nov 28, 2023
Open
@kaocher82 kaocher82 mentioned this issue Nov 29, 2023
Open
@Verdinjoshua26 Verdinjoshua26 mentioned this issue Nov 29, 2023
Open
@Manny27nyc Manny27nyc mentioned this issue Nov 29, 2023
Open
@qmutz qmutz mentioned this issue Nov 29, 2023
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
engineering Will involve Docs Engineering
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@Protectator @janiceilene