deck-builderlisted

# Deck & Doc Builder A battle-tested workflow for producing **beautiful, consistent slide decks and Google Docs as code**, iterating fast, and shipping them straight into Google Drive without the link ever changing. The golden rule: **generate → render to image → look at it → fix → upload.** Never claim a slide looks right without rendering it and viewing the PNG. ## When to use - "Make/update a deck / PPT / briefing / one-pager" (customer, exec, internal). - "Turn these notes / meeting minutes into a clean Google Doc." - "Put this into our Drive folder" / "update the slides I shared earlier." - Anything where layout quality + brand consistency matter. ## The loop (do this every iteration) 1. **Generate** the artifact with code (never hand-place by guessing): - Slides: a python-pptx script using `scripts/deck_helpers.py`. - Docs: rich HTML → uploaded as a Google Doc (see `reference.md`). 2. **Render to PNG and LOOK**: `scripts/render.sh deck.pptx 3 5` renders pages 3–5. Read the PNGs. Check overflow, alignment, color, crops, fit. 3. **Fix** the code and re-render until it's right. 4. **Upload / update** to Drive with `scripts/gslides.py`: - First time: create (returns a fileId; **save it** to a dotfile). - Every later iteration: **PATCH the same fileId** → the share link is stable. 5. Render the *uploaded* result once more (export Slides/Doc → PDF → PNG) to confirm Google's conversion matches your intent. Render is cheap and the only source of truth. A