[p5.strands] Increasing strands' presence in the reference

[lukeplowden]

Increasing access

p5.strands is currently undocumented, with only tutorials as learning resources

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

p5.strands requires more thorough documentation so that it's more discoverable and understandable. The idea is to add p5.strands examples to the reference in places which currently have GLSL examples (keeping them side by side to show both work).

For example:

• p5.Shader.modify
• setUniform
• filter

Additional examples could be added to any WebGL functions, including primitive shapes like box.

[perminder-17]

Hi @lukeplowden, first off, hats-off for the brilliant work on p5.strands! I have a small (very silly) question.
The filter() function in p5.js typically relies on its own built-in GLSL shaders. When you mention adding examples for p5.strands under filter(), do you mean writing a custom shader that leverages strands internally and showcasing that, and then using filter() function in the whole sketch created? I’m not quite sure how best to place strands examples inside the filter() reference?

In short, are you thinking creating sketches using p5.Strands and then using filter()?

[davepagurek]

In short, are you thinking creating sketches using p5.Strands and then using filter()?

I think so, to give users another potential way to discover strands (through looking up filter) in the examples.

There's a potential separate task we could do in the future where we replace the internal filter implementations with p5.strands versions, but I'll save that for a different issue 🙂