We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently there are two places actions and events for each components are documented.
1- Majority are in https://www.ampproject.org/docs/interaction_dynamic/amp-actions-and-events 2- Some components duplicated or sumemrized a version in their own .md file in addition to above.
.md
Some suggestions: 1- https://www.ampproject.org/docs/interaction_dynamic/amp-actions-and-events to focus on how to use events and actions. 2- Separate documentation for common actions ( similar to common attributes) 3- All components to document their actions and events inside their own .md file. 4- Maybe https://www.ampproject.org/docs/interaction_dynamic/amp-actions-and-events can point to common and component actions as links? 5- Maybe the table on top of each component file can list attributes, events and action names same way it does for layouts for a quick overview?
The text was updated successfully, but these errors were encountered:
//cc @CrystalOnScript we definitely should look into how we can improve this.
Sorry, something went wrong.
CrystalOnScript
No branches or pull requests
Currently there are two places actions and events for each components are documented.
1- Majority are in https://www.ampproject.org/docs/interaction_dynamic/amp-actions-and-events
2- Some components duplicated or sumemrized a version in their own
.md
file in addition to above.Some suggestions:
1- https://www.ampproject.org/docs/interaction_dynamic/amp-actions-and-events to focus on how to use events and actions.
2- Separate documentation for common actions ( similar to common attributes)
3- All components to document their actions and events inside their own
.md
file.4- Maybe https://www.ampproject.org/docs/interaction_dynamic/amp-actions-and-events can point to common and component actions as links?
5- Maybe the table on top of each component file can list attributes, events and action names same way it does for layouts for a quick overview?
The text was updated successfully, but these errors were encountered: