-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Conversation
✅ Deploy Preview for developer-chrome-com ready!
To edit notification comments on pull requests, go to your Netlify site settings. |
Hello! This is an automated review by our custom reviewbot. It updates automatically when code or GitHub comments in this pull request are created or updated. Requested changesIf there are any common problems with the content files you created or modified, they will be listed here.
|
1 similar comment
Hello! This is an automated review by our custom reviewbot. It updates automatically when code or GitHub comments in this pull request are created or updated. Requested changesIf there are any common problems with the content files you created or modified, they will be listed here.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I haven't had a chance to review this entire PR yet, but I wanted to share some initial comments.
@devnook @harleenkbatra08, a comment for both of you is that there are image files checked in as part of this PR. We normally try to use our image CDN for this sort of thing (and I know that the files being checked in aren't optimized).
How should we handle images needed for this project?
Re: images optimization - all images have to go through our uploader pipeline: https://developer.chrome.com/docs/handbook/how-to/add-media/ You might need a @google account to use the uploader - in this case please work with Harleen to upload the images and get the urls for them. |
The reason that preview is not working is because you deleted the workbox-migration.svg icon, while it is actually used by this page: https://github.com/GoogleChrome/developer.chrome.com/blob/main/site/en/docs/workbox/migration/index.md Is this icon related in any way to the /100 project? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've gone through most of the remaining files, and offered feedback.
A high-level comment about the experience when viewed on a device with a mobile viewport: it's very easy to get into a situation in which there is no highlighted year on the left hand side (and also, in which the very bottom of the year is just visible under the Chrome logo, instead of fully scrolled off screen). I don't know exactly what part of your One way or another, this animation needs to be tested and fixed on mobile viewports. |
In the first line of the description on the landing page can we change "Take a stroll down..." to "Take a scroll down memory lane..."? It's a great pun that Jeffy just pointed out. :) |
I think the arrows on each card should also be clickable to their respective links. Can we update that universally please? |
Agreed about Jeffy's "year not being highlighted throughout on mobile" comment. I think we should keep the year highlighted until the first card of the next year shows up in the viewport. |
Again, on desktop, when you scroll with keyboard, there's a weird jump between the years 2008 & 2009. Can you please check? |
For the keyboard config, couple of things:
|
Thanks. Reverted that particular image and Preview is working now. |
thumbnail: image/x1Los57vDga6OEMNi1dIJwZ0qvp2/1gyOFYMC1sFOBkC5csD3.png | ||
alt: 'Chrome 100' | ||
layout: 'layouts/chrome-100.njk' | ||
type: landing |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please add draft: true
to the YAML frontmatter? We want to be able to merge this PR without /100/
going live until we're ready.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When we added this in our index.md file, our Preview link stopped working so did not add it right now.
Actually, really sorry about this one but can you please update this to what's written here: https://docs.google.com/document/d/1ptIDUs93120ErZBAwR9tu4WXA0VD9xI6h61puDt62C8/edit?resourcekey=0-n-YwI5nmD1gIy2GpLJAeUg#heading=h.pvx544albuy5 |
@omkar-google @neha-google Omkar, I don't think we'll launch the likes functionality in this PR. Can you please remove all firebase logic (so firebase.js, script.js, meta.njk, gitignore rules) and leave just the UI? Once we get the UI in the right shape, we can re-enable likes functionality. Otherwise we wont get this Pr checked in before deadline. |
Make Sundar video related changes (check email to Omkar & Neha) |
In 2017, for the Photopea card, update the description to say: "A design editing web app, built by a single developer." |
I managed to find where the chrome-100 icon was used - in the commented out code for the side navigation. @harleenkbatra08 do we plan to use that navigation (icon in the sidebar next to home,docs,blog)? If yes, please bring back the icon and make sure the commented out code works. |
@harleenkbatra08 confirmed we don't need a link in the sidebar - please remove commented code. |
es: 'Versiones' |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Drive-by:
es: 'Versiones' | |
es: 'Lanzamientos' |
See, for example, https://es.wikipedia.org/wiki/Ciclo_de_vida_del_lanzamiento_de_software.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We are not supposed to make any changes in the existing content hence leaving it as it is!
Done. |
Done |
Done |
Removed the Firebase logic and kept the UI as it is! |
Done! Please verify the same. |
I believe the team has @google accounts as they're an embedded team but let
me know if you need help with uploading images, Rutuja/Omkar
…On Fri, Mar 25, 2022 at 11:20 AM Ewa ***@***.***> wrote:
Re: images optimization - all images have to go through our uploader
pipeline: https://web.dev/handbook/markup-media/
The uploader outputs html code to use image as a nunjocks shortcode ("{%
Img ... %}") but you can also just use the image's URL from the generated
output to embed an image in a different way.
You might need a @google <https://github.com/google> account to use the
uploader - in this case please work with Harleen to upload the images and
get the urls for them.
—
Reply to this email directly, view it on GitHub
<#2415 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ALHVD56TQUBGKXWPEN55CZDVBWOO3ANCNFSM5RR6N7MA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
--
* • **Harleen Batra*
* • *Developer PMM
*•* Chrome/Web Platform
|
Fixes #SOME_ISSUE_NUMBER
Changes proposed in this pull request: