How xrrca/creativecoding works
Project type and purpose
• This is an open-source, static content repository (“CreativeCoding”) serving as an online guide and resource collection for creative coding.
• It provides runnable examples in four main domains: JavaScript (p5.js & vanilla), PureData patches, Python scripts, and TouchDesigner projects.
• There is no dynamic backend or database; the site is hosted via GitHub Pages (static hosting), and the examples are either executed client-side in the browser or run locally by the user.
File structure
• Top-level folders:
• js/ – all browser-based demos (each subfolder is a self-contained HTML/CSS/JS sketch)
• puredata/ – .pd patch files and related assets or Python OSC handlers for PureData
• py/ – Python scripts with their own requirements.txt and example ZIPs
• touchdesigner/ – .toe project files (TouchDesigner) plus models, textures, or Python scripts
• Root files (README.md, LICENSE, CONTRIBUTING.md) describe the site, contribution process, and licensing.
• There are no build scripts or server code—this is purely static content.
README for additional insights
• The README confirms that you download or navigate to specific example folders and open the HTML, .pd, .py, or .toe files locally or via a live demo link.
• It links to a site (xrrca.github.io/CreativeCoding/) and a Wiki for more structured documentation.
a. Main components
• Repository (GitHub) – source of truth for content
• Build/Publish Pipeline – GitHub Pages (Jekyll or default Pages engine)
• Hosting – GitHub Pages serving static files via HTTPS CDN
• Content Categories – four logical groups: JS examples, PureData patches, Python scripts, TouchDesigner projects
• End Users – developers or learners who browse the site, clone/download the repo, and run examples
• External Dependencies – p5.js or other JS libraries (via CDN), Python packages (PyPI), PureData engine, TouchDesigner application
b. Relationships and interactions
• Developers push commits → GitHub repo
• On push → GitHub Pages automatically builds/updates the static site
• End user’s browser requests pages from GitHub Pages CDN → serves HTML/CSS/JS → loads JS examples in‐browser
• For PureData/Python/TouchDesigner examples, user downloads or clones repo → runs patches or scripts locally with required runtimes
• JS examples reference external libraries (p5.js CDN or local includes)
c. Architectural patterns or design principles
• Static site model (no backend, CDN-served assets)
• Content modularity: each example is self-contained in its own folder
• Separation of concerns: grouping by technology domain for discoverability
d. Key technologies/frameworks/libraries
• Git/GitHub for version control & hosting
• GitHub Pages for static site deployment (Jekyll or plain HTML)
• p5.js or vanilla JavaScript for browser sketches
• PureData for audio/visual patching
• Python + OpenCV/OSC libraries for scripting examples
• TouchDesigner for real-time visual projects
Detail
• Every critical step: commit, build, deploy, host, serve, run.
• Four content domains individually so reviewers can see parallel example tracks.