ProjectBuild an Agentic Content Studio: the explanation · Module 7: The deck spec and the templates · part 9 of 22
Part 9 · Module 7: The deck spec and the templates
Module 7: The deck spec and the templates
25 min read·
About 50 minutes · Needs: Module 5 (the low-level design and data model), Module 6 (the brand kit) · Code: backend/app/schemas/deck.py, frontend/src/render/renderer.ts, frontend/src/render/text.ts, frontend/src/render/brand.ts, frontend/src/render/slides.css
Where this fits
This module (blue) covers the deck spec stored with each project and the one renderer that draws it in the studio and on the /render page.
Module 5, the low-level design, showed the deck spec as one JSON document in each project's row. This module opens it: what each field may hold, how the backend cleans it, and how one TypeScript renderer turns it, plus the user's brand, into slides in three templates and two formats. Every slide the user ever sees, in a thumbnail, the editor or a PDF, comes out of this code.
The rest of this project is yours to keep
This project is bought on its own, once, and stays readable afterwards, including the parts added to it later.