{"id":269083,"date":"2018-04-02T11:55:40","date_gmt":"2018-04-02T18:55:40","guid":{"rendered":"http:\/\/css-tricks.com\/?p=269083"},"modified":"2018-04-02T11:55:40","modified_gmt":"2018-04-02T18:55:40","slug":"catching-up-on-amp-news","status":"publish","type":"post","link":"https:\/\/css-tricks.com\/catching-up-on-amp-news\/","title":{"rendered":"Catching up on AMP News"},"content":{"rendered":"
The big news since we last talked about AMP<\/a> is that the AMP team announced that there will be a way for non-AMP sites to make their way into the coveted Google search results carousel. Malte Ubl<\/a>:<\/p>\n Based on what we learned from AMP, we now feel ready to take the next step and work to support more instant-loading content not based on AMP technology in areas of Google Search designed for this, like the Top Stories carousel.<\/p><\/blockquote>\n You can’t do it now, nor is it clear exactly how you’ll be whitelisted, but apparently Google is open to it. The ticket in will be utilizing hopefully-someday standardized things like Feature Policies<\/a>, which, like AMP, disallow certain features in the name of… well that’s the thing. It used be be in the name of speed<\/em>, but the messaging seems to be more like in the name of privacy and security<\/em> now. Also a good goal, just funny that “Pages” is about the last thing left in the AMPcroymn. Sorry.<\/p>\n <\/p>\n This is the checklist<\/a> of related technologies. Makes my eyes glaze over a bit as I know precious little about any of them. Much of it needs to progress through standards processes and browser implementation first, and we’ll just have to see how practical it all is. If it means people stop creating amp-dot version of their websites (the new m-dot), that’d be pretty swell.<\/p>\n Tim Kadlec and Yoav Weiss got shout-outs in that AMP announcement for their idea of a “Content Performance Policy<\/a>“. As in, if a website promises and upholds the promises of being fast and not doing nefarious crap, it gets the same benefits as an AMP site.<\/p>\n