Storyboard Studio v0.2.0

What changed

• Inline editing for titles, summaries, bullets, layouts, blocks, and slide order with add/duplicate/delete plus undo/redo.
• Local JSON import/export and deterministic Markdown interchange.
• Source/evidence/owner fields become native PowerPoint speaker notes marked author-supplied and unverified.
• Native comparison, decision, timeline, and metric blocks; six documented themes.
• Named storyboard CLI, /api/v1 aliases, asset-manifest validation, synthetic gallery, and viewer QA tooling.

Verification

• CI matrix: Python 3.10, 3.11, 3.12, 3.13, 3.14.
• 14 local tests, make smoke, clean wheel install, and sample export passed.
• LibreOffice 26.8.0.3 rendered the reference fixture; mean visual error 6.22 under tolerance 12.
• Microsoft PowerPoint on macOS 26.0 opened the 4-slide fixture.
• Release artifacts carry GitHub build provenance attestations.

Migration

Existing /api/content and /api/presentations remain compatible. New integrations should use /api/v1; the v1 schema adds optional block, sources, and speaker_notes fields.

Storyboard Studio v0.1.1

Storyboard Studio v0.1.1

A verified installation and CI reliability patch for the first public release.

Fixed

• Every documented make target now uses the .venv created by make setup. A new clone can install, run, test, lint, format-check, and export without relying on globally installed project dependencies.
• CI now exercises that exact documented workflow, builds a distributable wheel, and uses current GitHub Action runtime releases.

Quick start

git clone https://github.com/OthmaneBlial/Storyboard-Studio.git
cd Storyboard-Studio
make setup
make run

Open http://127.0.0.1:8000, add a brief, review the outline, and export an editable PowerPoint deck. For a non-interactive example, run make export-sample.

Validation

• A fresh public clone completed make setup and make export-sample successfully.
• The release commit passed CI, covering the Make-based development workflow, wheel build, tests, formatting, linting, and PPTX export.
• The live Storyboard Studio showcase remains available for the public product walkthrough.

Compatibility

No breaking API or export changes. v0.1.1 is a drop-in update for v0.1.0 users.

Important note

The repository intentionally has no open-source license yet; reuse rights are not granted until the owner selects one.

Storyboard Studio v0.1.0

Storyboard Studio v0.1.0

The first public release of a local-first studio for turning a clear brief into a concise, editable PowerPoint deck.

Highlights

• Create structured presentation plans locally, with an optional Gemini-assisted mode and a deterministic local fallback.
• Export native, editable 16:9 .pptx files with six visual themes and practical content layouts.
• Work through a polished, responsive studio interface with a safe, inspectable preview before export.
• Run a deliberately narrow FastAPI service with validated requests, isolated export IDs, expiry cleanup, rate limiting, and security headers.
• Get started quickly with documented Python, Docker, API, contribution, security, and release guidance.

Quick start

git clone https://github.com/OthmaneBlial/Storyboard-Studio.git
cd Storyboard-Studio
python3 -m venv .venv
source .venv/bin/activate
pip install -e ".[dev]"
uvicorn server:app --reload

Open http://127.0.0.1:8000 and build your first deck. A runnable example is also available with:

python generate_pptx.py --input examples/product-brief.json --output output/product-brief.pptx

Privacy and security

The default planner is local and does not require an account or an API key. Gemini use is opt-in through GEMINI_API_KEY; it is never bundled in the project. Please read SECURITY.md before reporting an issue.

Validation

• The release commit passed the CI workflow, including linting, formatting, tests, and a runnable export.
• Explore the live showcase for the public product walkthrough.

Important notes

• This repository intentionally has no open-source license yet; reuse rights are not granted until a license is selected.
• Docker configuration is included, but it should be built in your own Docker-enabled environment before deployment.