Known bugs and intended new features are tracked using GitHub issues. If you'd like to start working on an existing issue, comment on the issue that you plan to work on it so other contributors know it's being handled and can offer help. Once you have completed your work on this issue, submit a pull request (PR) against the p5.js main branch. In the description field of the PR, include "resolves #XXXX" tagging the issue you are fixing. If the PR addresses the issue but doesn't completely resolve it (ie the issue should remain open after your PR is merged), write "addresses #XXXX".
If you discover a bug or have an idea for a new feature you'd like to add, begin by submitting an issue. Please do not simply submit a pull request containing the fix or new feature without making an issue first, we will probably not be able to accept it. Once you have gotten some feedback on the issue and a go ahead to address it, you can follow the process above to add the fix or feature.
We recognize all types of contributions. This project follows the all-contributors specification. Add yourself to the p5.js repository readme by following the instructions here!
If you've contributed to this website (or any other part of the p5.js project), add yourself here. Instructions to do this can be found at the bottom of the section.
Stewards are contributors that are particularly involved, familiar, or responsive to certain areas of the project. Their role is to help provide context and guidance to others working on p5.js website. If you have a question about contributing to a particular area, you can tag the listed steward in an issue or pull request. They may also weigh in on feature requests and guide the overall direction of their area, with the input of the community.You can read more about the organization of the project at contributor_docs/organization.md, p5.js Contributor Guidelines, and p5.js Steward Guidelines.
✨Anyone interested can volunteer to be a steward! ✨There are no specific requirements for expertise, just an interest in actively learning and participating. We can start with 1-3 stewards for each area. If you’re familiar with one or more areas of p5.js website, please reply to this issue to volunteer as a steward!
Once added, a steward's username will remain in the stewards section of the readme until they request to be removed. If a steward is unresponsive for an extended period of time, we may ping them to ask about their status. And you can always take a break as a steward and come back!
Area | Steward(s) |
---|---|
Overall | @Qianqianye, @limzykenneth |
Reference | @Divyansh013 |
Example | GSoC 2022: @Malayvasa (Contributor), @tyler-yin(Mentor); @3ru |
Teach | GSoC 2022: @Gracia-zhang (Contributor), @yinhwa(Mentor); @SarveshLimaye |
Showcase | GSoC 2022: @anniezhengg (Contributor), @raclim(Mentor) |
Learn | @nickmcintyre |
Libraries | @Qianqianye |
Community/Books/Social Media | @Qianqianye |
Contributor Docs | SoD 2022: @limzykenneth |
Other suggested area? |
Language | Steward(s) |
---|---|
Overall | @Qianqianye, @limzykenneth |
Spanish | @Guirdo, @Andreu-G, @dnd-alv, @holomorfo |
Chinese | @unicar9, @Gracia-zhang, @pentalei |
Korean | @yinhwa, @almchung, @jhongover9000, @sssueing, @GeryGeryGery, @sosunnyproject |
Hindi | @adarrssh, @Divyansh013, @deepchauhan, @SarveshLimaye |
Other Language Steward(s):
git clone https://github.com/processing/p5.js-website/
in terminal.p5.js-website
directory in the terminal and type npm install
.Once you've setup the site, type npm run watch
to run the website. This should open a window in your browser with the site running at http://localhost:9000.
src/
– All the pieces for generating the built site. Edits should be made here.
assets/
– All static files (imgs, css, fonts, js, p5_featured homepage sketches)data/
– translation filestemplates/
layouts/
– default.hbs is main page templatepages/
– Contains each of the pages of the p5 site, these get inserted in {{> body }}
tag of default layout. Note that for some pages (ex: learn, teach, and libraries) the hbs files are built from ejs files in the data/
folder. When this is the case, you will find a README file inside that page's folder with notes about how this works.partials/
– These are reusable pieces that can get added to any page or layout, they correspond to other {{> filename }}
tags in the pages or default layout.dist/
– Where the rendered files are stored, this gets generated via grunt server
but does not get added to pull requests as it is auto-built online.Gruntfile.js
– This file contains all the tasks for using assemble and YAML to generate the final, static site. It uses the taskrunner grunt.Regarding website translation, we are rolling out new languages slowly to be absolutely sure that we can support the full translation and maintenance of each language. We want to avoid the situation where we have many languages and it's beyond our means to support. So for this reason, we are holding now with Spanish, Chinese, Korean, and Hindi and getting those fully complete before we take on others.
We very much welcome translations that are hosted elsewhere. For example, https://p5js.jp/ - 日本語 (Japanese), translated and hosted by Katsuya Endoh. Please feel free to translate any of the website content and host it on an external blog or site. All of the website content is licensed under Creative Commons which makes it possible to reuse this content for non-commercial purposes if it is credited. We would be happy to share links and make connections so others can find and use this material.