@Cadhage, @kakshay21, let me explain you the scope more carefully: as mentioned before, collective.behavior.amp is a package that provides some limited support for Accelerated Mobile Pages in Plone.
Dexterity is a new content type framework that is included in Plone 4.3 as optional and is the default in Plone 5; a Dexterity-based content type can be modified through what is called a "behavior"; behaviors adapt a content type adding features like new fields or, in our case, more metadata and a new view.
so, let's say I apply the behavior to the News Item content type in Plone 5; after that I will have 2 things on instances of that content type: a meta tag in the default view (which is called
view) adding metadata information about the availability of a new view for this object, and that new view which is called
if you open an instance of your News Item object and you check the HTML you'll see the meta tag on top; and if you visit the instance of your object adding
/@@amp at the end of the URL, you will see the AMP view of that item.
collective.behavior.amp at this moment only provides that view for Dexterity-based content types with the behavior applied.
besides implementing other tags, I would love to see some other enhancements to integrate the package better with Plone itself; why? because currently there's no way to navigate the site in AMP mode: when you arrive to the view, you'll see only the content and there's no way to view listings or to make searches.
take a look at this, for instance:
there's a menu on the AMP view but when you select any item on it you go back to the normal view.
so, what I would love to see in the beginning is 2 things: we need to image a way to display listings (even if they don't have an AMP behavior applied, in AMP view; or maybe we have applied the behavior to the Folder and Collection types also and provide a listing in AMP format.
the second thing is having a search form that returns content that is available in AMP format; let's say we want to search all content that mentions BRICS on this site:
as you can see, the results are in normal format; so I was thinking on the possibility of enable a search button on the AMP view to make that new search form available.
the other stuff I think is pretty obvious, but what I really want is you to imagine how a CMS like Plone could benefit from the ideas and current features of the AMP specification.
don't dig deep into the details, because we will have time for that later. as I said before, try to understand what problems AMP solve and what use cases can benefit for this approach.
don't hesitate to contact me in case you have further questions.
good night and good luck!