New Zine: Coding Train Zine
Maintainers usually reply within 1 day
A pull request for this has already been merged.
- #349 by @github-actions — merged
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 1/100
- Issue type
- Feature
- Clarity
- Clearly specified
- Activity status
- Stale
- Domain
- content
Research direction
The issue describes adding a zine entry and provides the zine’s title, creators, descriptions, PDFs, cover image, and activity details. An open linked pull request (#349) is already working on it, so there is no useful next step for a new contributor until that work is resolved.
Written by the indexing model from the issue text.
Description
Title
Coding Train Zine
Topic
p5.js code examples
Tags
p5.js
Language(s)
English
Creator(s)
Dan Shiffman, Cy X
Creator URL
Short summary
Curated and produced by Dan Shiffman, Coding Train founder, and Cy X, Coding Train Community Manager.
Full description
Curated and produced by Dan Shiffman, Coding Train founder, and Cy X, Coding Train Community Manager.
This zine was originally published for the 2019 Processing Foundation fundraiser. Republished (with permission) on the PCD Zine Library for Processing Community Day 2026.
Some code examples are intentionally incomplete. Readers are encouraged to follow the corresponding Coding Train tutorials at thecodingtrain.com for the full sketches and explanations. This zine can be used for a self-guided activity or as support material for a creative coding workshop with a facilitator.
To assemble your copy, print double-sided on US Letter paper (A4 works too, but you might end up with extra margins, not a big deal). Fold the sheets in half, stack them together (making sure to preserve the page order), and staple along the fold. See this WikiBook page for instructions, especially the sections on folio folding and stapling.
Reader-order PDF
codingtrainzine_dan_031520.pdf
Print-ready PDF
codingtrainzine_dan_031520_imposed.pdf
Cover image
Additional files
No response
Activity type
Coding tutorials
Zine format
Half page, Folio, 40 pages
Duration of the activity
1-2 hours
Materials
Computer, Internet connection
Preferred attribution
No response
Maintainer notes
No response
License consent
- I own or have permission to license this material under CC BY-SA 4.0.
- Dominant language
- Vue
- Stars
- 5
- Forks
- 5
- Avg merge
- 20h 13m
- Merged PRs (30d)
- 71
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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.
More from processing/processing-community-day
-
Day of the weekOpen
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
processing/processing-community-day#337 ·
Maintainers usually reply within 1 day
-
Edit data for **PCD @ Karachi**Possibly taken @github-actions claimed this 1 day ago. Openedit event needs review
Difficulty 1/5 Under an hour Newbie friendliness 18/100
processing/processing-community-day#354 · 1 comment ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 35/100
processing/processing-community-day#212 ·
Maintainers usually reply within 1 day
-
Use Schema.org event data typePossibly taken @SableRaf claimed this 10 days ago. Open
Difficulty 3/5 1-2 days Newbie friendliness 55/100
processing/processing-community-day#173 · 1 comment ·
Maintainers usually reply within 1 day
All issues in processing/processing-community-day
Similar issues
-
content
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
cosimochellini/one-piece-zero-spoiler#516 ·
Maintainers usually reply within 1 day
-
area:space-accuracy good first issue track:data
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
Sara-Managed-Projects/space-radar#903 ·
Maintainers usually reply within 1 day