community page amp error: The tag 'img' should be replaced with an equivalent 'amp-img' tag.

[fifieldt]

[matrinox]

This isn't straightforward to fix. Either the whole site needs to be AMP-compatible or we just ignore this one page, the only page with images. But making it AMP-compatible has its own problems, like the FB chat bot we added, search, and more. It's very restrictive.

Another option we can try is to have 2 versions of the community page (AMP and non-AMP), but that would make maintaining that page more difficult down the road.

What would be the more preferable solution? Ignore or duplicate?

[erickhun]

@matrinox the effort doesn't worth the reward. I'd ignore it

[fifieldt]

I saw an article recently where Google was talking about removing the priority given to AMP sites anyway. Did that apply only to news, or is that something we should consider too?

[matrinox]

From my understanding, they've always said they've prioritized on speed, not AMP; AMP is just one way to create fast loading pages