processing / processing/processing-website
Automate adding/updating libraries list on the website
Open
Nobody has claimed this yet.
- Dominant language
- MDX
- Stars
- 90
- Forks
- 122
- Avg merge
- 1h 43m
- Merged PRs (30d)
- 3
Description
The list comes from the processing-contributions repo.
Notes from @runemadsen :
- There's a
npm run updateContributionsscript that needs to be run in the processing-website repo while the processing-contributions folder is in the same parent folder. That will move the JSON files to the website repo, and then a commit just needs to be made with the new files. - The website is deployed to AWS S3 and AWS Cloudfront via a GitHub action in the processing-website repo.
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
Start with the processing-website repository's npm run updateContributions entry point and the processing-contributions sources directory, keeping both repositories under the same parent folder. Review the existing GitHub Action that deploys to AWS S3 and CloudFront. Done means the library list is updated from the source repository and the resulting website changes are committed and deployed automatically.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, github-actions
- Domain
- cloud, devops
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100