Web studio for the edit2docs engine — generate & chat-edit PPT · Word · Excel in the browser. English-first UI with full Korean support (KO/EN toggle).
| Stack | Next.js 15 (App Router) · React 19 · TypeScript · Tailwind CSS |
| basePath | /edit2docs (override with NEXT_PUBLIC_BASE_PATH) |
| Engine | EDIT2DOCS_SERVER_INTERNAL_URL (default http://edit2docs-server:8000) + EDIT2DOCS_SERVER_API_KEY bearer |
| Health probe | GET ${basePath}/api/health (reports this UI's build commit and build time) |
| Build info | EDIT2DOCS_WEB_GIT_SHA, EDIT2DOCS_WEB_BUILT_AT (set by the image build, reported by the health probe) |
| i18n | dependency-free EN/KO dictionaries, header toggle, Accept-Language + job lang follow the active locale |
Generate (/generate): upload PDF / DOCX (and legacy DOC) / PPTX / XLSX /
HTML / EPUB sources, up to 200 MB (Unicode filenames round-trip intact), paste your Anthropic key (BYOK, forwarded per request and never persisted; OpenAI / Pexels / Pixabay keys are forwarded the same way), pick the output format and options (language, style
general / consultant / consultant-top, page-count range, narration,
image generation, and for PPTX uploads a restyle-or-extend template mode), and watch every pipeline stage stream in over
SSE. Result page ships the editable file plus design-spec / spec-lock /
quality-issue viewers and a cost summary.
Co-edit (/studio): open any PPTX / DOCX / XLSX and edit it by chatting.
The canvas shows the engine's addressable preview — per-slide SVG for decks,
data-e2d-*-tagged HTML for documents and spreadsheets — and while a turn
streams, the exact paragraph / cell / slide each operation touches is
highlighted live, then flashed once the refreshed preview lands. Undo steps
back through the revision chain; untouched content is byte-identical by
engine contract. Double-click inline text editing on slides is sent as direct, no-LLM edits.
The model picker is fetched live from the engine with your key.
MCP guide (/docs/mcp): connection instructions so AI agents
(Claude Desktop / Claude Code / Cursor) can drive the same engine directly.
cd frontend/src
npm install
EDIT2DOCS_SERVER_INTERNAL_URL=http://localhost:8000 \
EDIT2DOCS_SERVER_API_KEY=<engine bearer token, if the engine requires one> \
npm run dev
# → http://localhost:3000/edit2docsRun the engine locally first: pip install "edit2docs[server]" && edit2docs serve.
The default basePath is /edit2docs. next.config.ts falls back to it when
NEXT_PUBLIC_BASE_PATH is empty, so an empty value does not serve the app at
/; set a different non-empty value to mount it elsewhere.
Other scripts (in frontend/src): npm run build, npm start (port 3000),
npm run typecheck, npm run lint. There is no test suite.
hr_blog2.0's compose stack runs this
app next to the engine behind nginx (/edit2docs → this UI, /edit2docs-api
→ engine REST, /edit2docs-mcp* → engine MCP). Its edit2docs-web/
Dockerfile clones this repo at build time — see that repo for the full
service topology.
The UI defaults to English and resolves the visitor's locale client-side
(saved preference → browser language), so Korean-browser visitors land on a
fully Korean UI automatically; a header toggle switches any time. The active
locale rides every engine call as Accept-Language and seeds the job lang,
so generated documents and the engine's live-edit labels match the UI
language. Korean is a complete translation with compile-time key-shape
enforcement.
See PLAN.md for the original design — service topology, URL surface, screens, Unicode-filename round-trip, and BYOK handling.
Engine: edit2docs (Apache-2.0; its PPTX core is derived from ppt-master, MIT-licensed). Pattern: Edit2me.