Skip to content

Multiple small documentation issues found while learning p5.js (broken links & code clarity) #1057

@skyash-dev

Description

@skyash-dev

Most appropriate sections of the p5.js website?

Tutorials

What is your operating system?

Linux

Web browser and version

Firefox - 146.0.1

Actual Behavior

While going through the p5.js documentation and tutorials over the weekend, I encountered several small issues across different pages, including:

  • Broken or outdated links
  • Minor inconsistencies in tutorial values
  • Code examples that could be clearer or follow better practices
  • A layout issue where an input box overlaps text

These issues are independent but all occur within the p5js-website documentation.

Expected Behavior

Documentation links should be up to date, examples should be accurate and beginner-friendly, and page layouts should not obstruct content.

Below is a checklist of the specific issues encountered, with links and suggested fixes.

Steps to reproduce

  1. Broken Google Color Picker link
    Page: https://p5js.org/tutorials/get-started/
  • Google Color Picker link is broken
  • The same broken link appears twice

  1. Incorrect height value in Conditionals & Interactivity tutorial
    Page: https://p5js.org/tutorials/conditionals-and-interactivity/
  • In Step Four (“Add grass to hide the sun”), height is set to 400
  • Canvas height is 400 and horizon is starting from center i.e the height of rect should be 200.
  • Suggested fix: replace 400 with 200

  1. Input box overlaps text in p5.sound reference
    Page: https://p5js.org/reference/p5.sound/
  • Input field overlaps documentation text
  • Likely a CSS/layout issue
Image
  1. Broken forum and Discord links
    Page: https://p5js.org/contribute/contributor_guidelines/

  1. Code clarity improvements in Repeating with Loops tutorial
    Page: https://p5js.org/tutorials/repeating-with-loops/
  • Loop length should use the segments variable instead of generic length keyword.
  • Variable move should be declared with let

Would you like to work on the issue?

Yes. I grouped these small issues into a single issue for convenience, but I’m happy to split them if preferred.

Metadata

Metadata

Assignees

No one assigned

    Labels

    BugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions