Accelerated Mobile Pages (Amp) is a coding method that allows you to access the contents of your web site faster.
Google recently announced that AMP-encoded sites will be stored in Google's cache and will provide faster access if the user wants to access the site on mobile.
Google's goal is to increase the number of internet users via mobile.
By configuring the Amp page, you can normally provide users with a higher access speed and extra traffic comfort to the server. In addition, sharing applications like Facebook and Google+ will now give you a better user experience when you point to amp pages in your shares, revealing your awareness of the applications within them. Such as switching between similar headings. Now what matters in new content sharing is the user experience and the speed with which that experience has taken place. (See gif).
Come to work in the kitchen
Amp has some standards for its own. In order to serve Amp's purpose, you can think of a single page encoded in HTML that companies actually expect from you. It is compressed and edited or modified in css and java scripts. According to Amp, we will examine the structure of a google Amp page in the following example of certain plugins.
There are 4 important steps here
This is the simplest because Google wants to add what it wants (see https: //cdn.ampproject.org/v0.js)
Then send the json to the schema structure. Which is why google's library will gain functionality while running on our amp page. In this regard, google can skip this step not very strict. But it affects amp efficiency as much. In the case where these first two items work properly, the library user is in that area and in which region the priority of the promotion is that area. If you give an example, the amp page opened and you went to the top of the page and at first you are slow (according to Amp) and you will skip the pages of the page and you will see the data in the area you are in. (gif, jpg).
Amp's original css is one of the tiresome places of amp and kitchen but if we give an example; If there is such a thing as print css there is amp css here. So you're setting how your output will look. It is possible to get a good look with its own classes as google gives you several possibilities.
The most confused space for Amp is the "AMP schema". First I will write this for a flashing flash in your mind. If you use Angular, Reactive, or ionic, you have seen your own tags, and these tags are not really an element, they are written as special fields where the operations are done. They access their own fields and interpret and process them. This is exactly what the "AMP schema" looks like. Google In is the tag line you set yourself. The most prominent of these series is
Please Wait !...