studio waves
studio waves

Site Log • The Waveform Generation

A concise, rolling documentary of the website’s structure, code, and evolving objectives.

Purpose: keep a living synopsis of how the site is built (Eleventy, GSAP, Tailwind styles), why decisions were made, and what we’re targeting next.

Format: brief entries. Highest signal, minimal fluff.

Jump to latest updates
studio waves

Rolling updates

Key architecture notes, objectives, and changes. Latest first.

New entry helper

Paste into a new file under /src/diary/entries/ (e.g., YYYY-MM-DD-your-title.md), then commit and push.

---
title: Your title here
date: YYYY-MM-DD
---

- Point one
- Point two

Notes:
- Optional context here.

New entry editor

Previous entries

Copy into editor

    Recent GitHub commits

    View on GitHub
    • Loading commits…

    Creative prompts

      Sun Nov 30 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

      Gallery Multi-Row System & Site Enhancements

      • Gallery: 5 scrolling rows on homepage, 3 on subpages with alternating directions
      • Variable animation speeds per row (15s–27s), hybrid real images + generative canvas
      • All gallery cards clickable with modal view, 75×60px with wavgen-yellow borders
      • Homepage now aggregates images from ALL section folders (art, music, video, data)
      • Ken Burns effect slideshow cycles through combined images
      • Fixed video player auto-scroll on load (added skipScroll parameter)
      • Fixed code playground Monaco Editor stealing focus on page load
      • Removed duplicate hero sections from music subpages (ambient, melodic, breaks)
      • Removed unnecessary dark overlay divs, consistent 2×2 grid layout

      Technical:

      • GSAP startRowMarquee() for individual row animations
      • Scroll position save/restore pattern for Monaco initialization
      Mon Aug 25 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

      Save Markdown Diary entry to local site

      This comment will be saved to the site using a local application. One question is, how this will run in the browser when deployed to Github Pages?

      Mon Aug 25 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

      Save Markdown Diary entry ON WEBSITE

      This comment will be saved to the site using a local application. One question is, how this will run in the browser when deployed to Github Pages? Here is the test :-)

      Mon Aug 25 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

      Untitled

      • Point one
      • Point two

      Notes:

      • Context or links.
      Mon Aug 25 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

      Email MD

      Email MD

      Mon Aug 25 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

      Email MD

      Email MD Local test

      Sun Aug 24 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

      Project overview seeded from README

      • Eleventy-powered, teaching-grade portfolio with comprehensive commenting and GSAP-driven visuals.
      • Sections: Music, Video, Data & Tech, Art; responsive navigation; purple/yellow theme.
      • Real multimedia: SoundCloud (10 tracks) and YouTube (5 videos) with robust UX and error handling.
      • Interactive Code Playground: Monaco Editor with modes (Tailwind, GSAP, Eleventy, Site Snippets).
      • Tech stack: 11ty, Nunjucks, Tailwind, Node, GSAP, GitHub Actions/Pages.
      • Purpose: living reference and playground blending creative tech, pedagogy, and portfolio.
      Sun Aug 24 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

      Generated by Page

      • Point one
      • Point two

      Notes:

      • Context or links.
      Sun Aug 24 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

      Dev + Deploy flow (convenient reference)

      • Local dev options:
        • Two terminals: npm run build-css and npm run serve.
        • Or one command (recommended): npm run dev using concurrently.
      • Production build check: npm run build runs Tailwind then Eleventy.
      • Deploy via Git:
        • git add ., git commit -m "…", git push origin main.
        • GitHub Actions builds: Node setup → npm ci → build-css → eleventy → deploy _site/.
      • Quick cheatsheet:
        • npm run dev → edit → commit → push → wait for Pages.
      Sun Aug 24 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

      Codebase commenting project summary

      • Scope: every meaningful line across templates, JS, CSS, config, docs, and data is commented for teaching clarity.
      • Native comment styles: Nunjucks ``, JS // and /* ... */, CSS /* ... */, Markdown <!-- ... -->.
      • Teaching blocks at file tops explain structure, purpose, and decisions.
      • Heavily documented systems:
        • GSAP gallery (hero slideshows, background slideshow, infinite marquee, modal gallery).
        • Media players (SoundCloud, YouTube) with robust UX and error handling patterns.
        • Interactive Code Playground (Monaco) with 4 learning modes.
      • Result: a beginner‑friendly, maintainable, and pedagogically strong codebase.
      Sun Aug 24 2025 00:00:00 GMT+0000 (Coordinated Universal Time)

      Generated Manually

      • Point one
      • Point two

      Notes:

      • Context or links.
      How to add entries
      • Create a Markdown file in /src/diary/entries/ with front matter: title and date.
      • Commit and push via GitHub; GitHub Pages auto-deploys. Entries are auto-listed here, newest first.