Re-factor and re-launch a new version of amp-carousel to address a number of user & developer needs, including dynamic & responsive content, UX updates, and using amp-carousel outside of the context of valid AMP
Fix some low-hanging fruit for amp-carousel UX
Support dynamic and responsive content
Make amp-carousel function well when outside of the context of a valid AMP document
More TBD — the above description includes requirements based on initial discussions
/cc @nainar for edits/updates as the scope is developed & refined
(Note: this issue and the initial comments applied just to "dynamic and responsive" content in amp-carousel)
@ericlindley-g Eric, here's a preliminary attempt to do some of what you describe: https://afdsi.org/test/amp_list_carousel/. We had help from @jpettitt John Pettitt and @sebastianbenz Sebastian Benz here. How can we improve this approach? What does it fail to do that you want to do? We had to 'hard-wire' your second bullet and would like to fit a series of images - perhaps with different widths - into a viewport
Looks great! (though on mobile I'm not seeing any carousel content)
/cc @aghassemi for thoughts/feedback on the approach.
It's hard to tell what's missing given the issue seeing what loads on mobile, but my bet is that by adding straightforward declarative markup to the components themselves we could make this process a lot easier.
What I'd love to see is something that looks like the snippet below which feels like "obvious" way I'd try to do it as a page developer after reading the amp-list doc.
<amp-list template="slides" ...></amp-list>
<amp-carousel ...>
<template id="slides">
<amp-img src="{{slideLocation}}" ...>
<template>
</amp-carousel>
This issue hasn't been updated in awhile. @nainar Do you have any updates?
closing as dup of #20595
Most helpful comment
What I'd love to see is something that looks like the snippet below which feels like "obvious" way I'd try to do it as a page developer after reading the
amp-listdoc.