similar to #12520

Ok, I see. @franz-wohlkoenig can you explain what politics are mentioned there?

i remembered that AMP was discussed before, so i searched for it.

May be @mbabker could give some explanations or links to issues that were mentioned there and stopped this effort?

I stopped purely based on the backlash people were having with supporting an opt-in Google effort.

AMP is not just adding a template to core. AMP basically requires an additional view format because it has separate output requirements than a normal HTML document.

Ok, so it's basically about AMP issues and Joomla Code, and not some Joomla Community politics?

If you get past the politics some people have with using Google services or standards, then yes, it is entirely code structure related. We basically need a JDocumentAmp and each component that would support AMP output would need a view.amp.php view class for each view that would support AMP. And that's barely the tip of the iceberg. We'd still have to sort out dispatching plugin events, figure out if modules could be supported and how that would be integrated, and address some of the AMP requirements related to loading CSS and JavaScript.

I would also probably note that there wouldn't be enough time to do this as it would take a serious amount of work to do it properly.

Luckily, it wouldn't require any B/C breaks in the existing architecture, unless telling plugins they have to check the view format and return early if they don't support it is a B/C break (which they should be doing anyway, especially if #14176 gets followed through on). Most of the changes would be introducing new architecture, so it doesn't have to be a 4.0 item if the resources just aren't there.

is still AMP a thing?

Pardon me, just too curious to not ask as templates are being descussed - does frontend in Joomla now are completly free from any markup from backend (bootstrap2) in layouts that views generate for example in blog or other parts in frontend?

The core layouts are all built based on Bootstrap 2 in 3.x and will be Bootstrap 4 in 4.x. But, aside from a couple of edge cases now, everything that produces markup in core can be overridden in some form (either through the use of JLayout and its override system, the existing layouts and override system for components and modules, or in the case of JHtml the use of its ability to register callbacks for the various keys). Hopefully that helps to answer your question.

Thanks a lot, @mbabker
that definitely helps me to understand some points

If we were to go down the route of adding AMP support then we should probably add Facebook Instant Article support at the same time

I think all this (amp, facebook etc) is work for 3d extension developers.
Joomla! just need to make such thing easier for them.

The biggest problem is modules imho. Components can have AMP support and adding a JDocumentAmp is a bit time consuming but not impossible. What makes things really hard is the fact that modules are by design only outputting full HTML. And there would be large b/c breaks to modules in order to get them supporting non-HTML output formats.

@wilsonge but if we go with AMP template like the solution:

• any component output can be overrided to match AMP requirements
• any module can be overrided
• 3rd party extension builders can ship AMP layouts of their extensions as add-on that would place file to the template

AMP output requirements are different than normal HTML requirements and as such we cannot just simply add a template layout to existing core templates, a full AMP template to core, or AMP specific layouts in extensions, and call the task complete. If you take a look at the wbAMP extension, you'll see all the extra effort it has to go through to work with our default HTML views. This is why architecturally it is required to have a completely separate view format.

i'm not saying no to the idea. What I'm saying is that it's a significant piece of work and depending on how hard it impacts backwards compatibility in modules one that will take a opt-in approach from modules (because even in Joomla 4 we can't force people to rewrite every module in the ecosystem to get amp support). We'd need to assemble a team to work on it - and given the amount of work involved in it it probably isn't something that would be ready in time for 4.0

I am going to close this at this time. As @wilsonge says it is not a small piece of work and in the many months since this issue was created no one has come forward to work on it. Also since this issue was created there has been significant reduction in the usage of amp as a desired format