search

ampproject / wg-stories

Responsible for implementing and improving AMP's story format (amp-story). Facilitator: @newmuis
Creative Commons Attribution 4.0 International
28 stars 11 forks source link

wg-stories Meeting 2021-06-01 #68

Closed newmuis closed 3 years ago

newmuis commented 3 years ago

Meeting date/time (UTC)

2021-06-01 at 17:00 GMT

Instructions for joining the meeting

Stories Working Group Meeting Tuesday, June 1 · 1:00 – 2:00pm Google Meet joining info Video call link: https://meet.google.com/mdz-axok-ndz Or dial: ‪(US) +1 515-599-6696‬ PIN: ‪560 064 923‬# More phone numbers: https://tel.meet/mdz-axok-ndz?pin=2360109061691

Agenda Note: Add a comment on this issue to propose items for the agenda.

Beethoven commented 3 years ago

Roadmap for the amp-story-player [amp version] to implement the features present on the non amp version, buttons, events...

processprocess commented 3 years ago

Meeting notes

Attendees: Pratik Ghela, Beto Garcia. Jon Newmuis, Gabriel Majoulet, Wei Hong, Matias Szylkowski, Philip Bell, Ryan Warrender

Story as landing page from Google ads

[Beto] Web Stories as landing pages for search ads has been a successful experience. [Jon] We’ve seen that stories are a good content format for landing pages. We’re happy to hear about experiments and findings. Good use cases and examples can help us build the best experiences.

Roadmap for the amp-story-player [amp version] to implement the features present on the non amp version, buttons, events

[Beto] Is there any update on adding those features to the version of the player in AMP documents? [Jon] For the format to be as performant as possible we reduced the amount of features in the player loaded in an AMP document. We are interested in adding features to the player but need to be sure the use-cases for a feature can be widely usable.

Data collection component / Lead generation

[Pratik] Is there any update on a data collection component? We made a valid experience using amp-story-player and amp-form. [Jon] Forms in the body of the story have UX limitations. Forms in the page attachments is possible and we’re working it into our roadmap.

Web Stories CTA Updates I2S

[Jon] This will provide a common user experience to make things clear of what is clickable and set user expectation of post-click behavior.

[Pratik] Will amp-story-page-outlink have the same API as amp-story-page-attachment? [Philip] It’s changed so that it accepts a child a tag. This will allow SEO optimization and all native browser benefits.

amp-story-cta-layer I2D

[Pratik] When do you plan on deprecating cta layer? [Jon] Fairly long depreciation window of at least 3 months. Where possible, we will automatically migrate from the old CTA layer to a amp-story-page-outlink. If there is a CTA layer that contains one link, we will convert it to a button. We will do the best we can to migrate the whole ecosystem.

Sidebar in amp-story

[Pratik] Is the sidebar deprecated in amp-story? [Matias] we’re turning it off soon, bookend is deprecated already. We have an example of an amp-story-player with a sidebar. [Jon] We’re aiming to find a balance of elements that are specific to the story or the context in which the story is being displayed. We want to better understand features that allow publishers to link back to content.

Amp Story Desktop One Panel I2I

[Jon] This will allow a more consistent UX and resolve accessibility issues. [Philip] This will also allow removal of the viewport warnings so stories are supported on all screen sizes. Page transition components will also work on all different stories.

[Pratik] Do we know how many users view on desktop? [Jon] We don’t track data on what size screens users.

[Pratik] Will the half and half template be brought back? [Jon] We’re not currently developing half and half layouts. Pre-created templates within the format have not seen usage in the community. Some tools have integrated ways to design between both views.

[Ryan] In player context, are there any changes to the supports-landscape story? [Jon] supports-landscape will be unchanged. We’re thinking of ways we can give a visual hint of next story when supports-landscape stories are in the player.

[Pratik] Visual indication of next page and not next story. [Jon] The forward and back buttons next to the story are a visual affordance for page navigation. We’re looking for ways to make multi page story experiences as available as possible. Most of the time people want to see more stories and not just one. This is a way for us to open up that possibility.

[Beto] How would the like and comment buttons work? [Jon] We would allow publishers to add buttons that can control actions such as liking and commenting. (design is WIP)