Fast by default: AMP powering WordPress (AMP Conf 2018)

Fast by default: AMP powering WordPress (AMP Conf 2018)

Show Video

Yeah so my name is Alberto I. Work. And the web content, assistance team at Google and we'll, tell. You in this session how, it is possible today for, publishers. To take advantage, of. The. Benefits. Of using amp when they are publishing content with WordPress but, first let me put, this work, it. Was the first slide, let. Me put this work, in the context of what my team at Google does so, you think about okay. What. An ecosystem is basically, it's a community of interacting, part. And, organisms, and their, environment, and, the important things here is that every member of that ecosystem. Is. Important. To, all the other members so you cannot get rid of the trees and then, have birds for, example right so that's, a big deal with global warming right so this, is the, essence of what an ecosystem is and this thing happens with content, ecosystem a, content ecosystem is, a. Community. Of content, creators and content, consumption. Participants. Interacting. Between themselves and, their environment, and. There, are many. Of these ecosystems. Continuous. Systems in the web and I like to think about. The. Web as a sort, of like a Federation, of this. Continent, of systems and for. The purpose of my team there. Is one, important. Thing that is all these ecosystem, share, one, goal, the. Experience, that the users get when accessing, consuming, or polishing content in the Aussie consistent, ecosystem, should be an awesome. Experience. And. Since, amp is all about, achieving. An awesome experience for all users we. Are interested, in seeing how can we bring the, power of and to. As many of these ecosystems as possible, so. One. Of the most relevant content ecosystem arguably, and we're gonna see why of. Content. Ecosystem in the web today is WordPress, WordPress I can, be fine it as a content. Management system for for, websites and. As. Multa said it was. One of the early earth of the earliest, adopters of am. Historically. When, people hear, the word wordpress usually, used. To associated. With a, platform, that enables bloggers. To, polish the content an easier way but WordPress. Has been evolving steadily, since it, started, back in 2003, and, nowadays is like basically. Powered, website across, a wide variety of verticals, you know you name it blogging, the. Initial. One travel ducation real estate you. Name it so it's, a very very powerful platform in this sense and, it's. Reflected, by. Definitely. The largest contain. Management systems in the out, there right now with 59%, of the open source content. Management systems market share so that, is impressive and what is more impressive is that nowadays, 1/3, of websites, are powered by WordPress. So, these stats are very very, impressive, but, again. They tell me one, thing so. 1/3 of the web is a lot of the, web so there are many many many many users both publishing, and consuming. Content via. WordPress, and my, goal is all, of them should get an awesome, experience when they are doing that so. One. Of the. You. Know may. Your strength of the WordPress platform is the flexibility, that they offers, and that is reflected by a very, very large, and ever-expanding. Ecosystem. Of plugins and themes ok so there are like this many on each of those. Sites. You. Can use themes and plugins to basically customize, your WordPress site in a myriad of way you, in any way you can imagine it now. This, virtual. Also. Can be turned into one of the major challenges of the platform, right because even. If you take into account plugins, that are code. It perfectly, there are very performance, and they behave nicely. You. Know the, probability, of having two. Plugins or more that collide, when installed, at the same time in aside or, affecting, the performance of a site is this is not negligible, and. This. What. I like to think about this duality between a virtue. And a challenge, it, is parallel to the, very challenging, in the open web right so in the open web nothing. Prevents, a developer. To. Basically, screw the performance of a site by, following. Development.

Practice Development practices that are counterproductive, like you. Know loading script. Synchronously. Or like. Not optimizing, images and things like that and even, if you, know the developer, does an impeccable, work and codes. An aside that is extremely, efficient, and. Optimized. Installing. One third-party, JavaScript, could spell I perform, a disaster, for the side so. So. You. Think about it and emerge, as, a response, to that reality and bringing. To, the. Ecosystem. A set, of design principles and, control mechanisms that allow us to create. Sites, that offer predictable. Performance and, since. Both amp and the. Output, of WordPress, are just, web. Content, WordPress. Publishers, can, also benefit. From the power of M in, order to, offer. Radicular, performance, on their sites. So. When. We talked about and in, WordPress we basically talked about two things one is, a capabilities, enabled, by a plug-in and also. The integration of that log in with, the other components, of a site like the underlying theme and the, other plugins, that provide. Functionality for whatever the, side does, so. The, plug-in as well mention, the. Plug-in work for, enable, and in. WordPress, was pioneered, by WordPress, by, automatic, and, and. It. Was. It. Was developed, to satisfy the needs of, after. You have heard about the VIP platform. Vlp. Plasm is. A. Fully. Managed cloud platform, provided, by automatic, and that. Basically they offer full solutions, to their clients, they, offer support customer. Advice and so on and so on and the. Interesting thing for me is that it has a diverse diverse. Partner, ecosystem around, them and there are basically two type of partners. There are agency, partners that is where most, of the advanced WordPress. Development takes place and then, there are technology, partners, that basically team up with automatic to integrate, technologies. To. The, VIP, platform, Google, is one of those partners for example if you want to integrate and a Google. Drive to, the viable platform then, we, qualify. As a technology partner. Now. The. Plug-in definitely. Satisfies. The need that, they set for themselves. For. The VIP plasmon you know they report like around, 700, million pageviews per month, both, across

And The VIP platform, and, the plug-in also has been. Adopted. You. Know relatively. Good, size you have 200 more. Than 200 thousand installs, and, it also has been used as the core of other plugins that have been built around it, okay, but, thinking, about the, initial, goals of the plug-in that it, was basically satisfied, in it so the VIP platform, that usually have agency, partners working with them the. Characteristics, of the initial plugin implementation, make sense basically, it's a developer, oriented, plug-in basically. You, offer minimal, functionality. With. A set of core abstraction. That, enable, amp but, all but then allow, developers. To extend, in a custom IC to satisfy the needs of specific sites. But. You. Know that means also that for, sites that do not have strong, engineer support the, plug-in was very difficult to adopt because. You. Got you get play is that I'm going to show you in a second that makes, it difficult, as. Barb so yes I mentioned to the, plug-in enabled, millions of pages in thousands, of sites in WordPress. And on. The outside we heard a lot of feedback about we. Generated pages and most. Of the feedback that we heard was like well but all the amp pages, looked the same and they, looked a little bit kind of lame right so here, on the Left we have. You. Know so-called canonical on the original, sorry, the canonical side original, content, and, on the right is a page. That was generated using. The plug-in version, point zero point four and. Here. You can see two problems one is that there is, you. Know doesn't. Matter how the page on the left looks like the. Page on the right is going to look pretty much like this right, I know, the second thing you can see how we basically. That's what I call a, visual. Gap, right, so there is a little difference between them and then you see for example here there is no the hamburger menu the. Low updates, button with. Not present, here and there, is a lot of functionality that is is gone and the reason for this is that you, know you, can take this output. Tweak, the plug-in and then make it look nicer but if you don't have engineering support then, you cannot do it and your pages are going to look like this. So. Google. And automatic, started collaborating, around. Meet last year with. The purpose, of taking the plug-in and evolving. It to a point in which budget can, be adopted, as scale so, we, started working and we release, version. 0.5, a little while after we started collaborating and, this, release brought support. For new embeds for example via SoundCloud. Pinterest. We. Also changed the the. Original version of the plug-in use a black list sanitizer, or preprocessor. That basically you. Know take. You know you have to get rid of things that are not and we change it for the preprocessor that add a lot of intelligence to it and also, allows the plug-in to stay in sync with the amp specification. So everything that the UM projects evolve the plug-in stays up to date with. It you know whatever, use of code. And documented. Documentation. Improvements, and we added a basic UI to. Analytics. To the sides, short. After, we finished. That we were okay up on top ok sloths let's move you. Know towards the path to getting an old ant experience, and by. Mere chance, somehow. We, came across with the awesome fox with the or the xwp, engineering, team and. We start the talking yet we are doing this we are doing that and it should turn out that we shared a lot, of our visions and we decided to start working together so we join forces together with automatic and we, not. Long after our collaboration, started we released 0.6. And 0.6 is loaded, with a lot of new things but. I'm very excited about, I'm. Going to show each of them here. For example you can, see before, in, the previous version of the plugin you, could only preview, the, latest, pose that, you were working. In amp you know did you want to see how the amp version look you had you can only preview the last post and the, preview functionality, was separate from the integrated. Or the normal workflow in, WordPress, for doing. The previews here you can see. You. Know this is just a regular WordPress, role flow and now you can see they can preview the, changes in. The normal WordPress, and next. To it you have the little lamp icon, they say okay preview how the amp version looks like so. This is pretty cool because then the developer doesn't have to leave the normal workflow in WordPress to see how amp is behaving, or the, version of ambe's looking at, other. Thing is that the initial version of the plug-in only supported the post content type you know in WordPress there are different, type, of content. That you can create post.

Content. Type is one set of the of them and it was the only one supported, by the plug-in in, this version we had the support for pages that was one of the things that the community was asking, the most you know we need support for pages, here. There's not much to show only that this is a page and then it's been converted. To amp. And. The, other thing that we added is like because. Of the plug-in was. Evolving, we, wanted to give the user the power to say for, this particular, piece of content I want em to. Be disabled, for whatever reason, they have a functionality, that is, not supported for any reason so they have now they really. Need to say for, this particular post disable amp or vice. Versa you can see the Sonam tin which is actually very good to give the users the capability although. You're gonna see soon that this is not one IV needed and. It's very nice it, is gonna tell you all about it and another. Thing that was very cool it's like also, in WordPress, you have the ability to create what is called post. On post types you can create your own layout. And you define up a account, in time that you'd if you, create and before. In the initial versions of the plug-in in order to add an support, then you have to go to the code like, in the lower side. Of this slide, and you had to manually you, know say okay, I'm gonna put you, know this specifically. I want am support, for this content. Type now on, the upper part you see now you can't do it in the seed 0.6 version you can just click, and say I want an support for this post for this post content time and so on so, this is very good because adds a lot of flexibility, and don't require, the user to go to the code. Now. Beside. Those you, know the seed 0.6 has many. Of the things we. Added Auto loading capabilities. That basically allows to simplify the code because, you don't have to be including, all classes, and interfaces manually. We. Integrated, the ant customizers. With the regular customizer in the regular WordPress. Workflow, a lot, of you know one of the this, is important, because one, in, the content ecosystem team, one of the thing that we want to do is to, bring coding. And performance based practices, to. The WordPress, ecosystem, and we are applying those, principles in. The plug-in by, adding a lot of code quality checking in the build process of the plug-in itself and. You. Know the zero point six version also enhance the preprocessor a lot, added, a lot of intelligence, and actually fixed some box that, prevented. The plug-in to be actually, completed, in sync, with the amp specification. Now. Since. The beginning when, we started this work. We. Had, our site in an, all. And experience, in WordPress we can call it native and or all amp and it's. An experience in we're not. Per mode is needed but, if, there are you. Know no, visual gaps and not functional. Gas between the regular, version and the on version then you don't need two versions, and. I'm. Gonna invite theory, my colleague and friend from xwp, to, tell you the progress that we have made towards, this goal with. Version 0.7, of the plug-in. The. 0.5 and 0.6. Included. Great. Features, no. Doubt about that but like, any. Early. Versions, of software's, it, also came with its, limitation, and. By. That I mean. Until. Today the, WordPress M plug-in, only. Converted, certain. Type of pages. Imagine. A user coming, from Google, search and landing, on. The WordPress amp article, what. They would get is the, default styling, that, the WordPress plug-in provides and, that would, be the same across all WordPress, websites. Which. Uses, the. M plug-in. Not. Only that but when this user is done reading, the article, and goes.

And Click on the logo to go back to the home page then. They land to a non M version. Which. Provides a completely, different visual, experience, and that. Is because until, today, the. Zero-point-six, version, of the plug-in did, not convert, the, home page by default. Now. We've. Thought with the team how can we come over these, limitations, and we, brainstorm, and we, came to the conclusion, that we. Needed to combine this, non M version of the website with. The M version, into. One beautiful, native. M experience. When. Building beautiful WordPress. Websites, users, and site owners have, accessed, your large built in libraries, of, components. The, WordPress components, but. These are not all am compatible. Now. This. Obviously expose. Great, challenges, and. What. We wanted to do is take the power of these WordPress components. And, make. Sure that, what powers. One-third of the web today is AM valid, and in. Order to achieve that we had to completely rethink, the. Way the amp integration. In WordPress, was, done. Well. I'm, so proud to announce that through. Collaboration. With the Google aim team as, well as our friends at automatic, we, overcame. These. Challenges, and that. Via, the new version. 0.7. Beta, of the. Wordpress and plugin. Not. Only does it convert, all WordPress components, and make, them n valid it. Also allows WordPress, developers, to, continue, coding. The WordPress way and let, the plug-in do the rest and I think the best way to put this in context, is to, actually look, at the real world, example. Before. We do that we're, going to look at a website without. The, EM plugin, and that, is a beautiful, news websites, and it's. A non amp website. And it, has a fairly complex, layout, with, a drop-down and on. The right we have a search which, animates, our click and of, course this website looks beautiful, and mobile we, say with, the hamburger, menu nobody. Knows, why why is it hamburger but everybody, knows what it does. Now. At this stage before, 0.7. People would install the 0.6. Version, of the plug-in and what they would get when they activate, the plug-in is the, same looking homepage, an. On M version, of the homepage and then, they would have the, same nan M version of all the articles and on top of that another version with, a completely, different styling. Now. With 0.7. And we're. Going to activate the plugin in the admin. We. Were able to provide, this native, amp experience, and let's, look at the same website again. This. Is native amp in WordPress. We. Still have our drop-down we.

Still Have our search the mobile looks as beautiful and we see the amp live list in action allowing us to click and see, the. Latest, article. And we obviously still, have our drop-down and, while developing, these sometimes I found myself wondering, am i indeed amp is the plug-in activated, and look at the console powered. By amp. Passing. Validation, indeed and to, give you an idea of the speed that, this website is providing, what using right now is me browsing, the website and. Just recording, my screen that's. What we are getting helped us out of this WordPress website. Now. Let's. Recap, there. Is no longer a need for paid mode there. Is only one, beautiful, version of the website there is no longer need to maintain two version of it and, then. From a development, perspective. People. Or, companies, like we have heard the, Washington Post early on don't, have to put this hard work into, converting. WordPress. Components, and make them M valid, it is done out of the box with the zero-point-seven release, I. Mentioned. Early on it, doesn t convert, the M components, it. Also allows, developers, to continue, coding. The WordPress way and. What. We see on the screen is a typical, wordpress website, wordpress snippet. That we will find on any, wordpress website today and what. It does is it, just tells wordpress please anchor, stylesheet. In my, HTML. Head. Like. We see on the screen right now now. Obviously. Link. Stylesheet. Are not valid. And WordPress, developers. Would have to convert, that into, in light inline, H inline, CSS the, employ and now it is no longer need to do that because, with. The plug-in is done automatically, and we, can see the difference here WordPress. Developers, do not have to change the code snippet, we saw early on, the, M plug-in does that for them and it. Imprints. The CSS, inline the, M valid way, now. We didn't stop there we. Want to make it better and we working. In the prototype. Which. Analyzed. The HTML, Dom and. Compares. It with the CSS, that's, loading, on the page and make, sure that only the CSS, needed, for. This page is printed, in the in the. Custom, style, HTML, tag, now that really much aligns with. The EM philosophy. Of keeping, CSS, under, 50, kilobytes. As. I mentioned, earlier on WordPress is made out of multiple. Components, and one. Of the components are. Widgets, they are small, blocks that, users, can place in the web sites in multiple areas, and. If. We look at the backend, of WordPress we're, dropping a gallery widget and selecting. Images, which. Is the, standard WordPress experience. And we're. Going to be adding this widget in our sidebar and change, the categories, widget. To. Be drop-down. And you'll see why now. So. When. We look at the front-end, and we scroll down to, our sidebar this, this, is the non without. The M plug-in, right there is a list of images. And if we inspect the drop-down will. See this inline, JavaScript, and this. JavaScript is obviously not invalid, and instead, of developers, converting, that by, themselves we, activate, the M plug-in and the first thing we see is that we have a beautiful image. Gallery, and that's, leveraging. The. Amp carousel. Component. Of course and then. For. The JavaScript issue it has been replaced with the M bind components, and that, allows users, to just, select a category and, get. The expected, behavior. Now. At xwp, while, working on some of the major publishing, websites in the world we, have identified, that very often they, end up replacing. The, WordPress comments. Where alternative. Solutions, and we, believe that one of the reason, is because out of the box the WordPress comments experience. Is aging. A little bit it's, requiring, the page to reload and. While. Converting.

These WordPress. Components, to be am valid we also wanted, to improve the user experience by. Leveraging some. Of the M components, such as the. AMPA mustache the, M form, the. M by Nat the amp live list so. On the page. We're, going to scroll down to the list of comments and I'm. Going. To add a V useful, comments, very good feedback as usual. My. Name and an email and then when I post the comments, then. The M from Eustache displays, the success message and, the amp live list goes and fetched the comment in the back end and tell, us immediately there is a new comment, which, I can obviously click, on and then we scrolled up and we see the new comments, we, haven't, left the page and, developers. Didn't. Have to do anything on this team other than wrapping the, core comments. Function, with the amp live list HTML. Deep they. Get that out of the box this new, WordPress. Comments. Experience. Now. We have seen the style conversions, we've seen the widgets we've seen the comments but, 0.7. Includes. A lot more than that there. Is pretty. Much all the WordPress embeds are now converted, to BM valid liberate leveraging, some of the M components. Such as the M Facebook, M Twitter, M video. And so, much more. Wordpress. Cool components, are predictable. We. Know what to expect from WordPress and so. We. Could easily, convert, that to be an valid but. With WordPress powering, one third of the web and a huge ecosystem. Of plugins, and custom integrations. Is really, difficult to predict what's going to be rendered on the page and. While. This. Will be part of the future phases. What. We wanted to make sure of is that anything. Which is random. And the page is M valid and for. That we took what was before the sanitizer, and what we what we would want to call it the preprocessor and it. Essentially, it takes whatever, is rainin on the page puts. It through your funnel and, outputs. It in the M valid, way. While. Doing that we obviously saw, an opportunity to make things even better and. Since. We had access to this rendered. Or this output, we. Thought why, not automatically. Including, the M components, on this page we, see at the bottom it uses for M components, and, under. This content, we'll. Add a snippet, a code, snippet using github gist in. The backend we. Just use our snippet, and when. We reload the page if. We look at the console right now we. Can see that the M gist component, javascript has already been added. To the page, without. The implosion. Site. Owners would have to call developers, and say hey on page ID 54. I'm using a gif snippet could you please add the gif component, and that's, no longer needed. During. The panel talk there was a question about what. About the content, creation experience. Well. Now, we have turned WordPress, to be WordPress, M. But. We. Also wanted, the people editing, the content to be made aware when. They actually, add something which is not M compatible, on the page and.

That. Was. Really tired with the editorial notification. Of the editorial, workflow, so. In the WordPress admin, we, see that there is a script tag and an on click event which. Is not allowed an amp and if we save the draft and we see there's a notification saying. Hey this, content, will fail invalidation, it will be stripped out anyway, but you, should really remove it and then. We remove the, event. In the, disallowed. Script, and when we save again the notification. Is gone. So. Editors, in WordPress, now. Know when they're doing something wrong and the technology, behind that. Is, actually. Quite cool, is using, the preprocessor and, we have a prototype, using. The WordPress, REST API to. Which we can send content to and it, gives us a report of what the priests process has stripped out from the HTML, that will, open the door for so much and so, and, actually, even outside of the WordPress. Context. Also maybe, you know other people using. This NPAPI, endpoints, and that. Would also allow us to. Inform. Users when. Some of the plugins may not be good citizens at, this, stage and they, will be one. Day. When. Doing such, improvement, on an existing software. Backwards. Compatibility come. In mind of course and, that's. Really dear to the WordPress community it's. Really dear to us as well, well. 0.7. Is a hundred percent backwards. Compatible, and. That, is because to get this new native amp experience, seems. Have, to add one line of code telling the plug-in hey I'm M native, ready when, they diff am pretty and if they don't do that then, the legacy paid mode will, just be, rendered as usual, so. Site owners, can upgrade to zero point seven with a peace of mind that their website will not break. Now. Before, continue as, you. Would imagine this. Is a huge step forth and is. That it has taken a tremendous amount, of work to get there and I. Would like you to give a round of applause for the team was been put. In an outstanding, job or, to, do that. This, is not. Like any release this is a huge, step, fall for, the WordPress, world and actually, for anybody, trying. To create native, amp websites, this. Allows, WordPress, to now power these websites, and I haven't spoken. Much about Gutenberg, and more. Stuff really, exciting, stuff coming and for that I like, to invite Alberto, back on stage to tell you more about it, thank. You man super. Exciting. I'm. So excited about this I can hide. It so. I'm glad that you mentioned um. Gutenberg. Because something. That we want, to do as I mentioned before the. WordPress platform has been evolving steadily. Since the beginning and the. Latest. Thing that they is, coming for, them is Gutenberg. Which is a new content, creation experience. That, is going to be rolled out if I am not mistaken with, WordPress 5.0. Basically. Gutenberg is based on the concept of blocks, for content creation right now in WordPress if you want to create different, type of content you have many ways to do it you have like short code you have embeds, you have custom post types you. Have made a box that you have widgets you, have many. Ways to do things with, Guttenberg, everything, is going to be a block. So, I believe. That were a Gutenberg is gonna revolutionize the, way that, WordPress is used because you wanna streamline, the creation, of content. And. Because. Of this you. Know notion, of blocks is at the core of Gutenberg. I think, that there is strong. Synergy, between em and and. Gutenberg, and let's see why this. Is an example of Gutenberg, in action basically. You. Know everything, is a blog here we see that you have different. You know blocks for layout. Format, in. Standard. And so on so, for example here you know let's create an image you, can go select. From the media library. That's, it and that's a block and then here. You can create a paragraph this also a block. And. So. Now we can create a, embed. Let's suppose that we want to add a tweet to, our post so when you put the URL and boom that's, it and here on the right side you, can see that. There. Is the. Blog section, on there to see how the blog is configured that you can see how the block is laid out, and. So on. And. Then, Gutenberg. Is, extensible. You know it comes with this block but you can say well let's add new blocks, to the editing experience they. Suppose that I would like to add a lightbox and, get them to Gutenberg right so the lightbox is this functionality I click and that appears if, I want to do it the standard way I'm gonna have to do the decorative part and I also have to then put the JavaScript, that supports that functionality, but, what about if we use and components. To create Gutenberg blocks right, the.

Only Thing that we would have to do then is to do, the declarative, part and amp is going to take care of all, the rest so it's gonna be much easier to, create Gutenberg. Blocks. So. Definitely. Gutenberg. Is one thing, that we want to do in full integration with it and. Remember. That I am part of the content ecosystem team, so, the work that we do with, the unplugging, is in the bigger context, of the WordPress ecosystem, as a whole so we are, going to continue working on the unplugging, to, reach. As close, as possible to this native. All aren't experiencing WordPress, one, of the things that I am excited about is what Aundre. Talk. About services, rendering, for amp we are going to port the code that they growth to PHP and put, it also as part of the kinetics deploying so that can it be integrated. Then we WordPress caching. Plugins so that the, amp pages are already rendered so that's something that is gonna be very powerful, now. And, as. I said in in WordPress you have plugins and you have themes, so. There, is a lot of work that we want to do in the area of themes to create what I like to refer to as progressive, themes that are themes. That, integrate. Calling, and performance best practices enable. All. The new, technologies. Of the web platform and. Also, integrate, seamlessly seamlessly. With, the unplugging I mentioned. Woodinville, integration, is a big deal we're gonna continue working on that and. Another. Project that we are working coincidentally. With the X of you folks, again as well is called. Tie and. Tie. Is important, because we need to empower WordPress. Users, to, make decisions, about which plugins and things use based on concrete, quality, metrics not only on popularity okay. And the type project, is seeking, to do that and also, we want to use another, project that we you, know that. We are spearheading. And Google, that is called the HTTP archive we, want to create or. Keep. Track of the, performance. The WordPress ecosystem. And we. Do, things to it so like how is the performance today how we evolve it it's, important to keep track of how things are progressing and, and. Also we want to continue, engaging with, the WordPress community in general with, theme. And plug-in makers and everybody. In the community to. Make sure that the whole blogging, ecosystem. Is compatible, with amp there is a quite a bit of work there but I think that is very doable with, the world that we are laying out one. Particular collaboration. That I would like to call out is, with a company that is called Marshfield, Muirfield, is a it's, a very cool company based in Spain I think they have around 80 engineers, and they, have been involved with the UM project, for a quite.

A Bit and they have doing contributions. And one. Of the particular, things that I'm very interested in is what a protein, that they build that is called Muirfield press Muirfield. Press is a plug-in that was built. On top of the unplugging, that we are working on and, it. Offers, progressive. Web app capabilities. To corporate sites basically, they implemented. The amp shell model on top of the shadow API which, then allows. WordPress. Publishers. To use em as a embeddable. Data, unit, which is one of the most powerful things that I like about amp is that you can take and embed it anywhere, so, we want to have that capability ubiquitous. In WordPress something. That there is a lot of room. For us to collaborate they, did a lot of things they also have this what you see what you get kind of experience, that they implemented so that's. Something that is very exciting so. Certainly, the development, of the and. In WordPress has come a long way in the last since. I'm started, and. I want to again take. And. Acknowledge. The xwp team that have done a super, job with us and also, the collaboration that we have with several, teams in the automatic, like, the jet pack the team's team the VIP theme so, it's very very very remarkable, they. Were that, that has been happening and I'm really looking forward to the, future thank. You.

2018-02-18 16:55

Show Video


This is what AMP needs to take off the way Google hopes it will. Now what about Automattic-owned Woocommerce?

We will most probably work very closely with them in the coming months, nothing is set in stone at the moment but it is on the radar, very much so actually!

It would be great to get WooCommerce integrated seamlessly with the plugin. We want to help that happen. Stay tuned! :)

I love this, super exciting.

That was an interesting talk, Alberto & Theirry! This comments feature is pretty sick! ✅ I wish we could use these features progressively instead of having to go all in — from the very first day — since my sites have lots of JS that’ll need to be taken care of. P.S. I can see my comment in the talk LOL @ 24:37 :) was just testing the theme. Surprise!

Thanks for your suggestions Ahmad. Ongoing discussion about this topic here

I have to say v.7 is a massive leap forward in WordPress AMP usability. Overcoming the stripped down orphaned post issues caused by the initial plugin release is a huge win. We've been building our own AMP WordPress page builder framework for the past two years that has been focused on AMP only pages with a similar option to create non-AMP pages/posts when the end user wants to use an embed that is non-AMP compliant. You can see a couple example sites (AMP pages, posts, custom posts including recipes with full schema markup, as well as video, commenting, and Mailchimp form submission integrations) (AMP pages and posts, video, commenting, social sharing, form submission and ad network support.) We're currently working on AMP compliant Woocommerce stores, which should be available in March.

i don't watch this whole least for now.. and i am wondering.. AMP is google initiative.. how about "blogger"?

Toren your work is exciting, I would love to chat a bit more about it, specifically the work you are doing on WooCommerce. Linkedin invite sent!

I loved the plugin but how add ads to it!! The one by Khaled is lot easier ! but still I want to use the WordPress official plugin ! plz do reply if any1 has the answer

well done

Other news