-
Notifications
You must be signed in to change notification settings - Fork 3.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Master feature] Increase component support for Stories #16522
Comments
This is a high priority issue but it hasn't been updated in awhile. @newmuis Do you have any updates? |
Work for this will start right after #16521, which is in design phase at the moment. |
This is a high priority issue but it hasn't been updated in awhile. @newmuis Do you have any updates? |
1 similar comment
This is a high priority issue but it hasn't been updated in awhile. @newmuis Do you have any updates? |
This is a high priority issue but it hasn't been updated in awhile. @newmuis Do you have any updates? |
This is a high priority issue but it hasn't been updated in awhile. @newmuis Do you have any updates? |
Lowering the priority of this; this issue covers dozens of components and will not be completed in a timely manner. For priority of specific components' implementations, see the issue linked in the "Issue" column for that component. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
This is still under consideration, we may do some work on this next quarter |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
Currently
<amp-story>
supports few AMP elements as descendants. We should improve the component support for stories. There are over 100 AMP components, but they can be broken down into only ~10 buckets of work to support the vast majority of them. By grouping these components by their intended user experience, we can greatly improve the support for these components, and help make AMP Stories feel more like it is a part of the AMP ecosystem.Legend
amp-story
.amp-story
within the next few releasesamp-story
.amp-story
is currently being designed.amp-story
.amp-story
, but similar functionality is provided by another component.amp-story
.List of desired components
Last updated Nov. 27, 2018Launched Components
TBD
video-interface videos
These videos will autoplay when shown in the story, but may still have player chrome shown in the user interface, depending on the options made available by the third party player API.
Other media players/viewers
TBD
Interactive third-party content
TBD
Paywalls
TBD
Live blogging & dynamic content
TBD
Forms
TBD
Animations
TBD
Lightboxes
TBD
Miscellaneous
The remaining components will be considered/implemented on a component-by-component basis.
Other components
Last updated Nov. 7, 2018Advertising
Advertising in stories is handled through story ads, which are launched. As such, other advertising components are not used within stories.
Social sharing
TBD
User consent
amp-story-consent handles all user consent for stories, including integrating with amp-geo.
Interaction handlers
TBD
Miscellaneous
The remaining components will be considered/implemented on a component-by-component basis.
The text was updated successfully, but these errors were encountered: