We should look into trying to shirk the svg before we make this change. The png in 20k, the svg is 128k. The whole site is currently ~300k and we are worrying about 160k per font in#15516 .

I've compressed the svg from 128k to 11k usinghttps://vecta.io/nano (precision level 2). That includes a slightly lossy compression (nodes are slightly moved), but you won't notice unless really flipping back and forth on larger magnifications.

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

$ git checkout v3.1.x$ git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

$ git cherry-pick -m1 2184402cf7fcccb25c24566c190655319f22837a

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

$ git commit -am 'Backport PR #15533: Use svg instead of png for website logo'

4. Push to a named branch :

git push YOURFORK v3.1.x:auto-backport-of-pr-15533-on-v3.1.x

5. Create a PR against branch v3.1.x, I would have named this PR:

"Backport PR#15533 on branch v3.1.x"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free tosuggest an improvement.

Owee, I'm MrMeeseeks, Look at me.

There seem to be a conflict, please backport manually. Here are approximate instructions:

1. Checkout backport branch and update it.

$ git checkout v3.1.1-doc$ git pull

2. Cherry pick the first parent branch of the this PR on top of the older branch:

$ git cherry-pick -m1 2184402cf7fcccb25c24566c190655319f22837a

3. You will likely have some merge/cherry-pick conflict here, fix them and commit:

$ git commit -am 'Backport PR #15533: Use svg instead of png for website logo'

4. Push to a named branch :

git push YOURFORK v3.1.1-doc:auto-backport-of-pr-15533-on-v3.1.1-doc

5. Create a PR against branch v3.1.1-doc, I would have named this PR:

"Backport PR#15533 on branch v3.1.1-doc"

And apply the correct labels and milestones.

Congratulation you did some good work ! Hopefully your backport PR will be tested by the continuous integration and merged soon!

If these instruction are inaccurate, feel free tosuggest an improvement.

I spoke with@dorafc about this. Her only concern was if all browsers would support this. According tohttps://caniuse.com/#feat=svg everything but dangerously out of date IE does. There is a handful (~130 / 276,000 in the last week) of users who would be hit by this but it is probably but it is not enough to worry about.

I'm working on backporting this to the 3.1 series.

Backported directly to v3.1.1-doc as7830e26 and will get onto v3.1.x by merging v3.1.1-doc into v3.1.x before tagging v3.2.0.