TL;DR
In this article, you will learn how to build an AI-powered PowerPoint application using Nextjs, CopilotKit & OpenAI. We will c...
For further actions, you may consider blocking this person and/or reporting abuse
Great article!
I wonder if it's possible to use also dalle 2 or midjourney to generate the slides pictures
Yup. In the latest version of the demo it is doing that.
Great article!
Another learning experience for me, thanks for sharing. I'm looking forward to the next one.
Thanks for checking it out!
Cool!
I liked your last article. Looking forward to going through this one this weekend!
Yup, definitely a weekend kind of project...
Thanks!
We worked really hard on this one and I think it's very cool so I hope you enjoy!
Nice! Is CopilotKit open source? It might be a great fit for Open SaaS (an open-source, free alternative to $300+ boilerplate starters) then
github.com/wasp-lang/open-saas/
There is a lot of natural fit between open SaaS and CopilotKit. Let's talk!
Can you alter the presentations after the AI made them?
It seems like you can through the chat...
Yeah exactly ^
Sounds like a cool project. Kind of a long read though, so saved it for later.
Hope you enjoyed!
Great walkthrough. The CopilotKit + Next.js approach is smart for interactive editing — having the AI assist while you're in the app is a nice UX.
One thing I've been thinking about is the other end of the spectrum: fully programmatic generation where there's no UI at all. Think CRM webhooks that auto-generate client decks, or CI pipelines that produce weekly report presentations from data. In those cases you need an API you can POST structured JSON to and get a .pptx back.
The challenge is that most solutions (including python-pptx and PptxGenJS) require the caller to handle layout — calculating where each element goes. When you're generating hundreds of decks with varying content lengths, that gets painful fast.
Has anyone here tried separating the "what goes on the slide" (content/structure) from the "where it goes" (layout/positioning)? Curious if there are good patterns for this in the Next.js ecosystem or if it's mostly a backend concern.