processing/p5.js

Use random() more in p5.strands examples

Open

#8,776 opened on May 10, 2026

View on GitHub
 (4 comments) (1 reaction) (1 assignee)JavaScript (3,178 forks)batch import
Area:WebGLDocumentationEnhancementHelp Wantedp5.js 2.0+p5.strands

Repository metrics

Stars
 (20,784 stars)
PR merge metrics
 (Avg merge 9d 8h) (56 merged PRs in 30d)

Description

Increasing access

Previously, we didn't have random() supported, so many examples use noise() as a source of randomness. This works, but is a little less familiar from how one would use p5 outside of strands, so switching to random() makes these examples a little easier to understand.

Most appropriate sub-area of p5.js?

  • Accessibility
  • Color
  • Core/Environment/Rendering
  • Data
  • DOM
  • Events
  • Image
  • IO
  • Math
  • Typography
  • Utilities
  • WebGL
  • Build process
  • Unit testing
  • Internationalization
  • Friendly errors
  • Other (specify if possible)

Feature enhancement details

e.g. in the second example in https://beta.p5js.org/reference/p5/buildStrokeShader/, it uses noise for dithering. We probably need to look through all the strands reference items to get a full list of what might need to be updated.

Contributor guide

Research direction
Replace noise() calls with random() in p5.strands examples, focusing on the buildStrokeShader reference example. Test that the output remains aesthetically similar.
Tech stack
javascript
Domain
frontenddocumentation
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
1
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
80