It's so interesting to see how these random Google websites differ. For instance, this website has been made with Bootstrap and jQuery. Weird choice already given the internal tools they have at their disposal.<p>Weirder still, the grid of videos doesn't use the Bootstrap grid at all. The elements are set to <i>display: inline-block</i> and then their width (and height, which we'll get to) is adjusted every time the window resizes using JavaScript.<p>This is presumably to maintain square blocks, because that's the design they've opted for and grid systems do not give you much control over height of the grid cells.<p>But using JavaScript to try and ensure squareness of grid cells is totally unnecessary. You just need CSS, as I shall demonstrate:<p><a href="http://codepen.io/amdouglas/pen/eBddBd" rel="nofollow">http://codepen.io/amdouglas/pen/eBddBd</a><p><a href="http://codepen.io/amdouglas/full/eBddBd" rel="nofollow">http://codepen.io/amdouglas/full/eBddBd</a><p>Sometimes JavaScript is the best tool, especially in terms of accessibility; in this case, it adds nothing, only an expensive event handler. The resize event is really an awful way of achieving responsive web design. Media queries are the best option in 99% of cases.<p>* * *<p>Returning to the original thought, Google seems to have very different teams working here and there on their various marketing websites.<p>If you look at gv.com, their site also uses jQuery (with Slick and Velocity plugins).<p>If you look at duo.google.com and allo.google.com, they're Angular sites — which is what you'd expect from Google. A lot of their websites are based on Angular, it's a framework they're invested in (along with Polymer) and so on.<p>More recently, some of their marketing sites are being made with MDL. Usually small, less significant ones, not for apps but for random initiatives and projects that few people are going to look at. Which seems rather telling.<p>Polymer is in use, but seems to be reserved for applications like Youtube Gaming or Play Music. I think the Google PDF Reader is Polymer-based was well. That makes sense, Polymer is barely supported in browsers other than Chrome without a hefty bunch of polyfills.<p>There's also the Closure JavaScript libraries/tools, which Google used to use a lot for things like GMail (blog.google is the most recent instance I think).<p>For some reason, I find it odd that they don't have a unified internal toolkit for this sort of work. I'm not actually critical of this fact, I'm no critic of pragmatism. I'm just surprised.<p>I wonder though: does this indicate that these sites were outsourced to an agency?