ProjectBuild an Agentic Content Studio: the explanation · Module 6: Sign-in, sessions and brand onboarding · part 8 of 22
Part 8 · Module 6: Sign-in, sessions and brand onboarding

Module 6: Sign-in, sessions and brand onboarding

23 min read·
About 45 minutes · Needs: Module 5 (the tables and the API) · Code: backend/app/core/security.py, backend/app/api/routes/auth.py, backend/app/api/deps.py, backend/app/schemas/brand.py, backend/app/services/brand.py, frontend/src/pages/Onboarding.tsx, frontend/src/lib/auth.tsx

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
This module (blue) covers who you are (sign-up, sign-in, the session cookie) and what your brand looks like (onboarding, brand kit, uploads).

Before anyone can generate a deck, the studio needs two things: to know who is asking, and to know what their slides should look like. The first is sign-up, sign-in and the session cookie. The second is the brand kit, filled in by a five-step questionnaire. Both are small, but every other feature depends on them.

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