processing / processing/p5.js-website
Performance metatask
Open
Nobody has claimed this yet.
Needs Review
QA
- Dominant language
- MDX
- Stars
- 96
- Forks
- 322
- Avg merge
- 5d 22h
- Merged PRs (30d)
- 8
Description
Just making this metatask to track performance issues and notes.
- The HTML for the Reference page is quite large. The text compression on GH Pages server handles this for the most part but flagging here in case the platform is ever switched.
- CodeEmbeds appear to be loading their p5 scripts in parallel and in my browser the cache isn't catching
- As expected there is a significant loading state on the search results page. Layout placeholders should be used to mitigate dramatic shift
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the Reference page HTML, CodeEmbeds' p5 script loading, and the search results page loading state described in the issue. Determine which performance concerns remain relevant and define measurements or acceptance criteria for each; done means the selected concerns have verified improvements.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, javascript
- Domain
- frontend, performance, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100