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

Design and UI discussion of subscription/follow features, nomenclature #2693

Closed
jywarren opened this issue May 3, 2018 · 3 comments
Closed
Labels
break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration design issue requires more design work and discussion (i.e. mockups and sketches) more-detail-please issue lacks proper description and perhaps needs code links or the location of the problem

Comments

@jywarren
Copy link
Member

jywarren commented May 3, 2018

Copying in from #2104 --

Design discussion

Patterns

  • Let's standardize our use of the term "subscribe" and "follow".
    • We also use subscribe when we suggest that people "subscribe to the Community Science Forum". However, this page is terribly out of date: https://publiclab.org/subscribe
    • Just for reference, we use "sign up" in relation to the newsletter and the website itself.
    • "Follow" isn't really used anywhere else and I suggest we change all instances of "Follow" to "subscribe"
    • What do you think?
  • There are an emerging set of ideas about pinning main research areas to the top of the dashboard Dashboard overwhelmed with just a few posts on a single topic #2076, and about showing clusters of related tags to help people see the dimensions of a research area tag visualization of all tags #1502
  • what are other patterns we could aspire to?

Overview of how people are presented with information about and control over their subscriptions

The places on our site where one can control subscriptions vary widely:

Primarily:

screen shot 2018-01-24 at 5 05 07 pm

screen shot 2018-01-24 at 4 34 45 pm

  • on the tag page where all tags are listed https://publiclab.org/tags, you have the option to "follow" AKA subscribe and to see how many people are already following that tag. You can also sort by "subscription to bring all the tags you already follow to the top.

screen shot 2018-01-24 at 4 34 01 pm

  • on tag pages such as https://publiclab.org/tag/kite-mapping, you are offered the option to "Follow" the tag, and are also offered the unique opportunity of getting the RSS feed (is this shown anywhere else? should it be?)

screen shot 2018-01-24 at 5 51 35 pm

@jywarren jywarren added design issue requires more design work and discussion (i.e. mockups and sketches) break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration more-detail-please issue lacks proper description and perhaps needs code links or the location of the problem labels May 3, 2018
@jywarren jywarren added this to the Email notifications overhaul milestone May 3, 2018
@chanjess
Copy link
Contributor

chanjess commented May 9, 2018

This is very cool and interesting to read. What are the updates on this? I think that the consolidation of "follow" and "subscribe" makes sense and is intuitive.

@ebarry
Copy link
Member

ebarry commented Oct 5, 2018

Here's an update that makes great progress toward this, a new listing of the largest research areas on publiclab.org in the sidebar:
screen shot 2018-10-05 at 6 17 03 pm
Clicking on a blue topic offers the ability to "Follow" right from the dashboard.

@jywarren
Copy link
Member Author

Closing, as we've made tons of progress and are now using "follow" everywhere!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
break-me-up break up for cleaner code separation, discrete tests, and, easier and iterative collaboration design issue requires more design work and discussion (i.e. mockups and sketches) more-detail-please issue lacks proper description and perhaps needs code links or the location of the problem
Projects
None yet
Development

No branches or pull requests

3 participants