This repository has been archived by the owner on Mar 14, 2024. It is now read-only.
I/O 2019: Speed at Scale blog post recap #931
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
khempenius
approved these changes
May 23, 2019
TimvdLippe
previously requested changes
May 23, 2019
Meggin
reviewed
May 23, 2019
|
|
||
| During the "Speed at Scale" [talk](https://www.youtube.com/watch?v=YJGCZCaIZkQ&feature=youtu.be) at Google I/O 2019 we announced three things that we hope will improve web performance over the coming year. | ||
|
|
||
| <iframe width="560" height="315" src="https://www.youtube.com/embed/YJGCZCaIZkQ" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
There was a problem hiding this comment.
The video is a little bit lost with so much white space. This may be something to fix on infra-side but still worth calling it out.
There was a problem hiding this comment.
Good catch. I'll see if playing around with the width/height would still work for the responsive layout for this post, but can otherwise defer to infra if I can't do better :)
There was a problem hiding this comment.
You can copy what the portals folks did maybe?
<div style="width:100%; padding-top: 56.25%; position: relative;">
<iframe style="width:100%; height: 100%;position: absolute; top: 50%; left: 50%; transform: translate(-50%,-50%);" src="https://www.youtube.com/embed/Ai4aZ9Jbsys?start=1081" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
|
|
||
| The Google Fonts documentation has been updated to include `font-display` in the default code embeds. We hope this will encourage more developers to try out this exciting addition. | ||
|
|
||
| <figure class="w-figure"> |
There was a problem hiding this comment.
What is this image showing? It's not entirely clear to me. Maybe it could be better introduced?
There was a problem hiding this comment.
The image is showing the default embed code window from Google Fonts. I've tried to update the text to note that the embed we are referring to is in the image below it. Does that help?
robdodson
suggested changes
May 23, 2019
| @@ -1273,4 +1273,4 @@ | |||
| "github": "rowan-m", | |||
| "glitch": "rowan-m" | |||
| } | |||
| } | |||
| } | |||
|
|
||
| During the "Speed at Scale" [talk](https://www.youtube.com/watch?v=YJGCZCaIZkQ&feature=youtu.be) at Google I/O 2019 we announced three things that we hope will improve web performance over the coming year. | ||
|
|
||
| <iframe width="560" height="315" src="https://www.youtube.com/embed/YJGCZCaIZkQ" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe> |
There was a problem hiding this comment.
You can copy what the portals folks did maybe?
<div style="width:100%; padding-top: 56.25%; position: relative;">
<iframe style="width:100%; height: 100%;position: absolute; top: 50%; left: 50%; transform: translate(-50%,-50%);" src="https://www.youtube.com/embed/Ai4aZ9Jbsys?start=1081" frameborder="0" allow="accelerometer; autoplay; encrypted-media; gyroscope; picture-in-picture" allowfullscreen></iframe>
</div>
Co-Authored-By: Rob Dodson <[email protected]>
Co-Authored-By: Rob Dodson <[email protected]>
Co-Authored-By: Rob Dodson <[email protected]>
Co-Authored-By: Rob Dodson <[email protected]>
Co-Authored-By: Rob Dodson <[email protected]>
into speed-at-scale * 'speed-at-scale' of https://github.com/GoogleChrome/web.dev: Update src/site/content/en/blog/speed-at-scale/index.md Update src/site/content/en/blog/speed-at-scale/index.md Update src/site/content/en/blog/speed-at-scale/index.md Update src/site/content/en/blog/speed-at-scale/index.md Update src/site/content/en/blog/speed-at-scale/index.md Update LightWallet image for Speed at Scale blog post
robdodson
approved these changes
May 23, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a post summarizing three takeaways from the Speed at Scale talk @khempenius and I gave at Google I/O. As most of our talk focused on case studies, we're going to do this first round-up and follow up later with individual write-ups as needed.
This pull request adds a new:
Have you read the wiki on writing a guide or a codelab?
Does your content reference any Glitch projects?
Have you read the wiki on working with Glitch?
Have you added the Glitch project to our team page?