I was very pleased when testing out all the blocks that they almost all worked just fine when viewed in the AMP plugin's Standard or Transitional modes. Thus, making CoBlocks AMP-compatible appears to be pretty straightforward for the various blocks:
Accordion: Perhaps consider using amp-accordion, though the use of details works just fine as it stands.
SVG: Various blocks are writing out SVG with an attribute fillrule. This is not valid SVG and so it the AMP validator is not recognizing it (and thus stripping it). It should rather be fill-rule, AFAIK. Simply doing a search/replace for s/fillrule/fill-rule/i. I'm afraid this could cause block validation problems, but if not, this is an easy fix.
Share: These could potentially use amp-social-share component.
Carousel Gallery: Make use of amp-carousel on the front-end rather than using flickity.
thebud15
commented
4 years ago
I was very pleased when testing out all the blocks that they almost all worked just fine when viewed in the AMP plugin's Standard or Transitional modes. Thus, making CoBlocks AMP-compatible appears to be pretty straightforward for the various blocks:
amp-accordion, though the use ofdetailsworks just fine as it stands.fillrule. This is not valid SVG and so it the AMP validator is not recognizing it (and thus stripping it). It should rather befill-rule, AFAIK. Simply doing a search/replace fors/fillrule/fill-rule/i. I'm afraid this could cause block validation problems, but if not, this is an easy fix.amp-social-sharecomponent.amp-carouselon the front-end rather than using flickity.