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 tools #384
Comments
This is very cool. I would be most curious about the settings people are using and getting a better feel for how people are using things. Compile time would be super useful and tracking that over releases. Is it going up or down? |
This would be cool! (2), (3) and (4) would be especially useful for me. |
@scottkellum @zellwk interesting. Compile times would have to be tracked externally, but everything else here could be done in Sass. I love the idea of tracking how settings are used — and making some effort to collect that data (it would be a self-selecting sample, but still interesting). We could think about two audiences: the developer working on a project, and the broader Susy/Sass communities learning from what we've done. |
Definitely! Although Susy is great with the flexibility, we should probably start documenting down best practices and how to use her. It gets difficult for people to learn otherwise. Insights into how a developer works on a project can be very very helpful indeed |
This should be done as a plugin and not part of the core I think. Also I am worried about the potential overhead it might introduce, especially in regard to performance.
You will be facing the Observer Paradox here. To track compile time, you are loading extra code which are resulting in longer compile time. :) |
Yeah, I think the data is interesting - but in the end it would be easier to collect manually with a survey. |
Was talking with @aaronagray about the potential for Susy to track your usage, and report back. This would be limited to things we can actually track — nothing related to the actual DOM. A few things we could potentially track:
span(3 of 12)
16 times)&
now in Sass-script)Would that be useful? What other ideas do you have? What would you want to see in a report? Discuss!
The text was updated successfully, but these errors were encountered: