-
Notifications
You must be signed in to change notification settings - Fork 346
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
Document use cases #846
Comments
I know @TanviHacks was working on this, some of this is also in my post and some of why we can't do things are here: https://github.com/mozilla/testpilot-containers/wiki/Moving-between-containers |
Also #428 |
I reached out to @dustindriver about producing a couple how-to videos for this. Turns out Dustin's team has some goals that relate to producing content that sends people to AMO, hooray for serendipity. Dustin's goals relate to publishing on Hacks, as I understand it. And @jonathanKingston has a Hacks post in the works, as I understand it. Let's get on the same page about all that. @TanviHacks has a list of user stories that we can pull the most common, general cases from as a starting point for scripts. I can help Dustin refine those for screencast. I'm not convinced that Hacks audience is the exact audience we need to hit with "how-to" content, but once the videos are made and hosted, we can link to them from the AMO page and hopefully convert some of those 1-star reviewers. |
@hoosteeno can we close this off or do we need to keep tracking this / documenting it? Is there worth in writing down where we thing containers could be improved for use cases? And use cases we think are explicitly out of scope? |
I think we can close this, the gears are in motion. |
The extension gets rave reviews from almost everyone. Most of the poor reviews are 1-star reviews by people who are unclear on one of these questions:
We should document use cases. The fastest path to comprehension for most is probably a screencast showing a specific use case (e.g. start from vanilla profile and take users through the use case, "I always want LinkedIn to open in a LinkedIn container"). It would be great if superfans of containers would consider submitting screencasts of their own use cases for potential inclusion on the addon page.
The text was updated successfully, but these errors were encountered: