ProjectBuild an Agentic Content Studio: the explanation · Module 15: Exports: PDF, PNG, ZIP and HTML · part 17 of 22
Part 17 · Module 15: Exports: PDF, PNG, ZIP and HTML

Module 15: Exports: PDF, PNG, ZIP and HTML

20 min read·
About 40 minutes · Needs: Module 7 (the renderer and the formats), Module 11 (Chromium and the /render page) · Code: backend/app/render/export.py, backend/app/api/routes/render.py, backend/app/render/chromium.py, frontend/src/api.ts

Where this fits

WHERE THIS FITS Slidesmith Studio this module BROWSER React FRONT DOOR AND API nginx, FastAPI BACKGROUND AGENTS LangGraph MODELS Ollama RENDERING Playwright DATA Postgres 17 OPERATIONS evals, Docker, Cloud Run Studio app React pages /render page same renderer nginx proxy, headers Auth sessions, CSRF Brand kit onboarding, uploads Projects deck spec, edits Job runner progress over SSE Research search, facts Strategist outline Designer slide JSON Check fit, else repair LangGraph pipeline state graph, JSON repair Ideas post ideas from pillars qwen3.8:27b Ollama, local GPU Web search Ollama API Chromium render, measure Exports PDF, PNG, ZIP, HTML PostgreSQL users, decks, jobs Uploads disk or GCS Evaluation suites, gate Insights usage, timings Containers Docker Compose Deploy Cloud Run, CI/CD
Exports (blue: this module) use the server's Chromium to draw the studio's own /render page, then turn that page into files.

The deck is only useful once it leaves the studio. LinkedIn takes a carousel as a PDF document; a newsletter wants images; a colleague wants one file that opens anywhere. This module is the last step: the export menu in the editor, one API route, and the code that turns a rendered deck into four kinds of file.

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.

Or open everything with a plan