Comment by angled
6 days ago
My pipeline for this is vscode + prompts + markdown templates + GitHub copilot -> markdown docs -> pandoc to produce.docx -> copilot in word for “nice” formatting -> copilot in ppt for nice decks. LLMs all the way down.
I find it’s easier to version control and diff the .md artefacts, those remain my authoritative source.
Wow. Seems like a headache compared to how I make slides the old fashioned way: copy and paste my figures into blank powerpoint.
I was doing something like this, and then realized at least with claude that it’s so much better at HTML that it’s better to get an HTML-first deck together, which could then be turned into a PPT template and/or PDF directly, depending on needs.
It saved me a fair number of design-tweak steps in the md -> pandoc part of the workflow. Realistically, hand editing claude’s HTML is also easy in most cases, so I didn’t feel like I lost much (for the generative cases). Similarly if it’s mostly what I’ve written directly that’s the source it’ll be in markdown, and I’ve found it’s a faster path to have md -> (LLM-translated HTML deck) -> pdf.