HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
google
WebFundamentals
JavaScript2014–2019
google / WebFundamentals · Archived

WebFundamentals

Former git repo for WebFundamentals on developers.google.com

Web DevelopmentDeveloper ToolsLearning & ReferenceMobile & Desktop
Explore on GitHubRead Hacker News discussions
8Distinct people
18Mentions
0Explicit recommenders
13.9KGitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Former git repo for WebFundamentals on developers.google.com

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 1:49:46 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by year18 dated mentions

Observed mentions: 2014-04-30 20:01:24 UTC to 2019-02-03 23:37:40 UTC.

0369122014-01-01 00:00:00 UTC to 2015-01-01 00:00:00 UTC (exclusive): 11 mentions; 0 submissions, 11 comments20142015-01-01 00:00:00 UTC to 2016-01-01 00:00:00 UTC (exclusive): 2 mentions; 2 submissions, 0 comments2016-01-01 00:00:00 UTC to 2017-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments20162017-01-01 00:00:00 UTC to 2018-01-01 00:00:00 UTC (exclusive): 2 mentions; 0 submissions, 2 comments2018-01-01 00:00:00 UTC to 2019-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019-01-01 00:00:00 UTC to 2020-01-01 00:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2019

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
20142014-01-01 00:00:00 UTC2015-01-01 00:00:00 UTC11011
20152015-01-01 00:00:00 UTC2016-01-01 00:00:00 UTC220
20162016-01-01 00:00:00 UTC2017-01-01 00:00:00 UTC101
20172017-01-01 00:00:00 UTC2018-01-01 00:00:00 UTC202
20182018-01-01 00:00:00 UTC2019-01-01 00:00:00 UTC101
20192019-01-01 00:00:00 UTC2020-01-01 00:00:00 UTC101

What Hacker News says

18 sources
kaycebasques·Feb 3, 2019
I work on the same team (Web DevRel) as the "service worker guy" you mention (Jake Archibald). Alex Russell (who introduced the "PWA" and is now advocating for the "Never-Slow Mode" idea you may have heard about recently) works on Chrome but collaborates with us frequently. > When I first heard someone talking about "Progressive Web Apps" I thought they were talking about "Progressive Enhancement" Progressive enhancement is indeed where the P in PWA comes from. The core idea is to ship great sites for all users, and progressively upgrade with the latest web capabilities (service workers for offline, manifest for adding to homescreen and full-screen displays, and so on) when a user's device supports it. If the user's device doesn't support it, they should still get a good, traditional web experience: fast, secure, usable. > Turns out doing
Read the rest
a PWA is just basically about using the "Service Workers" API [2] and the practices around that. Your first impression about progressive enhancement was closer to the mark. The PWA Checklist [1] is the canonical document about what constitutes a PWA. We created that doc in November 2016 [2] to try to clear up the massive confusion about the definition of a PWA, but apparently to no avail. Under the "Baseline PWA" checklist you'll notice that there's mention of service workers and manifest files, but there's also mention of loading fast on 3G, having mobile-friendly design, being secure, supporting all browsers, and so on. Again, the core idea is to ship good experiences for all users, and progressively enhance the UX when possible. It'd be an interesting postmortem to study why the "PWA" term has been so notoriously confusing. IMO part of the problem was that we as a team weren't 100% crystal-clear on the definition at the start. But to be fair, I think we did straighten out our messaging pretty early on. The PWA Checklist that I linked to which has been out since November 2016 is evidence of this. But by that time it was already too late. PWA became a buzzword, and the blogging community seemed to conflate "PWA" with "promising new web platform capabilities" (service workers and manifests). I don't mean to shift blame. We (Web DevRel) most likely caused that conflation. I think the takeaway is that this is a lesson on what can happen when you're not 100% clear on messaging right from the start. [1] https://developers.google.com/web/progressive-web-apps/check... [2] https://github.com/google/WebFundamentals/commits/master/src...
In Tiny PWAs and why I keep building them
kinlan·May 2, 2017
I lead the DevRel team for Web and Chrome so please take anything I say with a hint of bias.... I've found it pretty easy to use so far - https://paul.kinlan.me/chrome-on-home/ and got it deployed in a number of environments including AppEngine. We are planning on getting this deployed in our [WebFundamentals](https://github.com/google/WebFundamentals/blob/master/.travi...) Travis script to run automated testing on our dev docs site. Some things that I found hard: no documentation on how to get it running in a CI yet - some devs (Justin Ribeiro - https://hub.docker.com/r/justinribeiro/chrome-headless/) got a docker file all set up which helped a lot, the devtools protocol whilst it has docs wasn't quite as simple as I had hoped and I had to guess of how to call the node library.
In Getting Started with Headless Chrome
kinlan·Aug 13, 2014
Urgh, that is a url encoding error on our site. I have raised a bug (https://github.com/google/WebFundamentals/issues/664). With regards to the study, that data was ascertained by working with direct user studies and taking feedback from them, I think we can certainly make this a lot clearer in the those set of documents. re:sparse. Yes it is as we are still building this section out and fleshing out the guidance more, but we have worked with the team that did produce the study (It also turns out I am pretty good at making the bad examples of the sites). I do have one follow up question: Would you like to see code that espouses the principles that we are saying are good. re: relying on your own data. I am curious, what do you look for?
In Google Web Fundamentals: Monetization
maxhe·May 1, 2014
Thanks for taking a look! We soft launched yesterday; this is definitely still a work in progress. >the icons symbolizing the different topics are not clickable https://github.com/google/WebFundamentals/issues/1 >headlines/h2s https://github.com/google/WebFundamentals/issues/52 >they actually enlosed their <video> elements inside a <a> tag Are you referring to the video on this page? https://developers.google.com/web/fundamentals/documentation... Clicking the non-control parts of the video opens a demo page with the responsive HTML/CSS demoed in the video. The controls still work, at least in Chrome 34 on Mavericks. If you're talking about something else, could you file an issue on GitHub? https://github.com/google/WebFundamentals/issues/new
In Web Fundamentals: A handbook for best practices
kinlan·Apr 30, 2014
Hi, We will get these sorted. I was surprised that this got picked up so early as we were just starting to canvas feedback from developers, so it still a work in progress. Multi-screen/Multi-device was the term we chose because mobile-first is a very very loaded and our goal is to target mobile as a base but ensure everyone builds up from that experience. But you are correct, it needs to be introduced. [Edit] - adding bugs https://github.com/google/WebFundamentals/issues/17 https://github.com/google/WebFundamentals/issues/18
In Web Fundamentals: A handbook for best practices
Braunbart·Apr 30, 2014
The icons are broken in firefox because you used a webfont wich is hosted on another domain. Edit: Just saw that you already know about this: https://github.com/google/WebFundamentals/issues/13 --- Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at https://web-central.appspot.com/web/essentials/icons/icons.w.... This can be fixed by moving the resource to the same domain or enabling CORS.
In Web Fundamentals: A handbook for best practices

Showing the 15 most recent of 18 sources. Enable JavaScript to search and browse every indexed mention.

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.