Fix documentation formatting, code clarity, and layout issues #1059
+50
−50
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #1057
Summary
This PR fixes multiple small documentation and layout issues across the p5.js website to improve clarity, accuracy, and usability for learners.
Changes included
Replaced obsolete Google Color Picker references with generic guidance to use any online color picker
Corrected incorrect canvas height values in the Conditionals & Interactivity tutorial
Improved code clarity and variable declarations in the Repeating with Loops tutorial
Fixed broken/outdated forum link in contributor guidelines
Resolved layout overlap on the p5.sound reference page by removing negative positioning and using proper spacing
Why this change is needed
Broken links and incorrect values can confuse beginners
Small documentation inaccuracies compound learning friction
The p5.sound reference page had overlapping UI elements that affected readability and accessibility
Testing
Ran npm run dev
Verified the following pages locally:
/tutorials/get-started/
/tutorials/conditionals-and-interactivity/
/tutorials/repeating-with-loops/
/reference/p5.sound/
Confirmed no overlapping elements and correct content rendering on desktop and mobile viewports
Notes
Changes are intentionally small and scoped
No functional or API behavior is altered
Happy to split into smaller PRs if preferred by maintainers