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

Consider redesign of Get Involved page #344

Open
kgodey opened this issue Jul 19, 2019 · 2 comments
Open

Consider redesign of Get Involved page #344

kgodey opened this issue Jul 19, 2019 · 2 comments
Assignees
Labels
🕹 aspect: interface Concerns end-users' experience with the software 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work 🏷 status: label work required Needs proper labelling before it can be worked on

Comments

@kgodey
Copy link
Member

kgodey commented Jul 19, 2019

IMO, https://network.creativecommons.org/get-involved/ has a couple of issues:

  • Users have to find the "I'm good at" text, click the dropdown, think about all the options, etc. before we show them how to get involved. I think that's too much friction.
  • We only show one way to get involved at a time, a user has to spend a lot of time if they want to see all the ways they could be involved.
  • Some of the options are confusing. e.g.
    • "I'm good at social media" links them to our newsletter, Slack, mailing list, and social media. If I wanted to find the newsletter, I would never think to click on it. Also, if I did click on "I'm good at social media" in a Get Involved page, I would expect to see how I could use social media to contribute to CC, not just follow social media accounts.
    • "I'm good at sharing" is also confusing. It's got way too many links in it (also there's no link to the FAQs despite mentioning it) and I'm not sure what it means to be good at sharing.

I don't the format works for providing a smooth experience for users. Some good reading:
(1) How to reduce friction with good design
(2) Don't Make Me Think! book summary (the book is better but it's a good list of principles)

@claudiorrrr
Copy link

This is great feedback, Kriti. IMO this version is better than what we had before, but I'm happy to hear any ideas about how to better display that info.

@kgodey
Copy link
Member Author

kgodey commented Jul 22, 2019

@Claudioruiz my main feedback is that we should display the ways users can get involved in a way that's easier to scan quickly, I don't have any specific design ideas.

@kgodey kgodey assigned Juliabrungs and unassigned claudiorrrr and hugosolar Mar 24, 2020
@kgodey kgodey modified the milestones: Low Priority, Content Issues Mar 24, 2020
@kgodey kgodey added 🚧 status: blocked Blocked & therefore, not ready for work and removed not ready for work labels Sep 24, 2020
@cc-open-source-bot cc-open-source-bot added the 🏷 status: label work required Needs proper labelling before it can be worked on label Dec 2, 2020
@TimidRobot TimidRobot moved this to Triage in possumbilities Sep 10, 2024
@possumbilities possumbilities added 🟩 priority: low Low priority and doesn't need to be rushed 🕹 aspect: interface Concerns end-users' experience with the software and removed 🏷 status: label work required Needs proper labelling before it can be worked on labels Sep 30, 2024
@possumbilities possumbilities moved this from Triage to Backlog in possumbilities Sep 30, 2024
@cc-open-source-bot cc-open-source-bot added the 🏷 status: label work required Needs proper labelling before it can be worked on label Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🕹 aspect: interface Concerns end-users' experience with the software 🟩 priority: low Low priority and doesn't need to be rushed 🚧 status: blocked Blocked & therefore, not ready for work 🏷 status: label work required Needs proper labelling before it can be worked on
Projects
Status: Backlog
Development

No branches or pull requests

6 participants