processing / processing/p5.js-website

Usability & Design Improvements - start here!

Open
#1,221 5 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Discussion
Dominant language
MDX
Stars
96
Forks
322
Avg merge
5d 22h
Merged PRs (30d)
8

Description

Start here for:

  • Ideas on design or user experience improvements, including usability bugs
  • Research and discussion for implementing larger design changes or ideas
Topic

During the first few months of 2026, two groups of students from a graduate course on usability studies are working on usability research for the p5.js website. This analysis includes user studies. The result will inform what work will be prioritized on the website, and opened to contribution.

Updates will be shared on this issue, so you can "watch" it if interested. Many thanks to all who have already participated in the user studies, and everyone who is interested but has not yet shared their experience will be invited to discuss the outcomes of the research when they are shared.

If you're a designer, educator, and/or anyone who uses the website and would like to be part of this effort, I hope you stay tuned here!

Another way to get involved and help right away is to look through past open issues or PRs, especially ones that got stuck in review and/or are proposing significant changes to design or function of the site (for example: related to the "search" function), and mention them in the comments below.

Research Reports

(more coming soon, both reports and further detail, analysis, and data)

[1] Presentation by Abdulrahman Alobaid, Bill White, Chad Brandon, Su Min Kim
[2] Report by Lina Wang, Nara Ho, Riti Upadhyay, Sifan Xue
[3] Report by Abdulrahman Alobaid, Bill White, Chad Brandon, Su Min Kim

Besides analyzing the site as it is, I hope these reports can help us test usability in the future. Additional to reports the students have also shared their protocols and other materials, which we can reuse, and which I will link.

Please reference the reports in the comments using "[1]" or "[2]". I'll keep the numbers above consistent. Thank you!

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the linked usability research reports [1], [2], and [3], then review the discussion and related website issues or pull requests mentioned in the issue. This issue is gathering research and ideas rather than naming a specific change, so completion depends on future prioritization and separate actionable issues.

Written by the indexing model from the issue text.

Assessment

Domain
design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.