UX Tools (W.I.P.)

Feb. 2019


Work Type
Open Source Project
My Role
Project Management / UX Designer
Time Frame
April 2019 - In Progress


While in school studying UX I realized a problem that alot of students were facing: too many resources. There are too many tools, articles, and books to keep up with. How do you know which ones are worth the time? Well, I decided to UX this problem.

Why Open Source?

I genuinely believe everything is better with collaboration. Open source software project seem to be pretty common place but I haven't seen many design projects be open source, so I decided to create one. I want to give all designers an opportunity to contribute and gain experience.


Check out the Minutes from meetings to get up to speed the progress of the project and our thoughts so far. See what tasks you can start working on now on our Trello. Get access to the files on our Google Drive.

Join the conversation on Slack or you can share your thoughts, questions, or ideas by emailing: ux-tools@emilioharrison.com

Ground rules & expectations

Before we get started, here are a few things we expect from you (and that you should expect from others):

  1. Be kind and thoughtful in your conversations around this project. We all come from different backgrounds and projects, which means we likely have different perspectives on "how open source and design are done." Try to listen to others rather than convince them that your way is correct.
  2. Please read the Code of Conduct before contributing. By participating in this project, you agree to abide by its terms.

Code of Conduct

Our Pledge

In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to making participation in our project and our community a harassment-free experience for everyone, regardless of age, body size, disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.

Our Standards

Examples of behavior that contributes to creating a positive environment include:

  • Using welcoming and inclusive language
  • Being respectful of differing viewpoints and experiences
  • Gracefully accepting constructive criticism
  • Focusing on what is best for the community
  • Showing empathy towards other community members

Examples of unacceptable behavior by participants include:

  • The use of sexualized language or imagery and unwelcome sexual attention or advances
  • Trolling, insulting/derogatory comments, and personal or political attacks
  • Public or private harassment
  • Publishing others’ private information, such as a physical or electronic address, without explicit permission
  • Other conduct which could reasonably be considered inappropriate in a professional setting

Our Responsibilities

Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.

Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, or to ban temporarily or permanently any contributor for other behaviors that they deem inappropriate, threatening, offensive, or harmful.


This Code of Conduct applies within all project spaces, and it also applies when an individual is representing the project or its community in public spaces. Examples of representing a project or community include using an official project e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event. Representation of a project may be further defined and clarified by project maintainers.


Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at code-of-conduct@emilioharrison.com. All complaints will be reviewed and investigated and will result in a response that is deemed necessary and appropriate to the circumstances. The project team is obligated to maintain confidentiality with regard to the reporter of an incident. Further details of specific enforcement policies may be posted separately.

Project maintainers who do not follow or enforce the Code of Conduct in good faith may face temporary or permanent repercussions as determined by other members of the project’s leadership.


This Code of Conduct is adapted from the Contributor Covenant, version 1.4, available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html

For answers to common questions about this code of conduct, see https://www.contributor-covenant.org/faq


Thanks to all of our contributors for lending their valuable input and expertise on this project


This went from a closed source idea to an open source project by the info at The github Open Source Guide.


This work is licensed under a Creative Commons Attribution 4.0 International License.

View More Case Studies

What do you think?

Designers are nothing without critique and feedback,
so let me know what you are thinking.