Restructure documentation for components by 3p providers


All these extensions in amp don't work the amp.dev examples


The media category is full of external providers, which for me the only thing that has given me is confusion in the amp system, I know that amp is free but when you have to learn something new, you first have to focus on the core.

I propose the separation of external providers, of the amp core, in all kinds of extensions.
It would be something like that other similar systems are already doing.
AMP CORE
amp extensions
amp experimental extensions
amp extensions external providers

I have also seen that external providers have given me errors in javascript, when loading the page.

External providers to which access to their prices or their sales web pages has cost me a lot to find them in the google search.

Honestly, after having tried all the external providers, they have not transmitted confidence to me except the official ones like dailymotion, yotube, viqueo.

But as I said, it is important to start differentiating the core from the providers so as not to waste time for developers who want to implement only AMP.

apester example no run

errors and 404

more errors

more errors

more errors

Many xhr requests

First extension that has no errors

It seems to me a good implementation by redbull that although the requested resource is not error-free

A correct implementation of vimeo, without any errors

more error

error and 404

more error

I sincerely love that the amp is free and that anyone can develop an amp block, but you also have to be very clear about what the core is and what parts are in the extensions or everything can turn into chaos in the long run.

Start by reviewing the AMP documentation's media category and the provider extension examples referenced in the issue, including Apester, Dailymotion, YouTube, Vimeo, and Red Bull. Done would require a documented, agreed separation between AMP core, extensions, experimental extensions, and external-provider extensions, with the reported example errors addressed or clearly scoped.

Written by the indexing model from the issue text.