Skip to content
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

Analytics best practice in Thinkmill design systems #10

Open
gwyneplaine opened this issue Nov 6, 2019 · 0 comments
Open

Analytics best practice in Thinkmill design systems #10

gwyneplaine opened this issue Nov 6, 2019 · 0 comments
Labels
help wanted Extra attention is needed

Comments

@gwyneplaine
Copy link
Contributor

We've identified the reasons to capture analytics in the style guide, however there are a lot of ways to do this poorly, we need to outline what the recommended method is for adding analytics to design system components at Thinkmill, this might include answers to the following questions:

  • Is React.Context the best place to propagate analytics events? Why?
  • If yes, what is the best method for exposing this context to all our components
  • If no, what alternative mechanism should we use and why?
  • Should there be an analytics package, if yes what should it contain?
  • What patterns do we leverage to effectively propagate events for each component in their differeing usage contexts?
@gwyneplaine gwyneplaine added the help wanted Extra attention is needed label Nov 6, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
Development

No branches or pull requests

1 participant