banatie-service/docs/labs
Oleg Proskurin 00ef8b969d doc: collect Banatie Lab documentation in docs/labs
- extract Lab design system from feature/lab-frontend branch
- move legacy workbench and expanded-image-view docs from apps/landing
- add overview README with planned pages, API scope, and design direction

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
2026-06-11 01:08:13 +07:00
..
README.md doc: collect Banatie Lab documentation in docs/labs 2026-06-11 01:08:13 +07:00
design-system.md doc: collect Banatie Lab documentation in docs/labs 2026-06-11 01:08:13 +07:00
legacy-expanded-image-view.md doc: collect Banatie Lab documentation in docs/labs 2026-06-11 01:08:13 +07:00
legacy-workbench.md doc: collect Banatie Lab documentation in docs/labs 2026-06-11 01:08:13 +07:00

README.md

Banatie Lab

Banatie Lab is the browser UI for working with the Banatie API: generating images, browsing the gallery of created images, managing prompts, aliases, and flows. It is referenced on the landing page as "Web Lab".

The Lab will be built from scratch. This folder collects everything that was previously designed or documented, so the ideas are not lost.

Documents in this folder

Document Origin Purpose
design-system.md feature/lab-design / feature/lab-frontend branches (apps/landing/src/app/(lab)/CLAUDE.md) Full design system and layout architecture for the Lab UI
legacy-workbench.md apps/landing/WORKBENCH_DOCUMENTATION.md (main) Text-to-Image workbench — predecessor of the Generate page (MinimizedApiKey badge, PromptReuseButton)
legacy-expanded-image-view.md apps/landing/src/components/shared/EXPANDED_IMAGE_VIEW.md (main) Full-size image modal with metadata — building block for the gallery

Planned feature set (from design-system.md)

Pages that were planned in the abandoned feature/lab-* branches:

  • /lab/generate — generation workbench (prompt, references, parameters)
  • /lab/images — gallery of generated images with filters
  • /lab/live — live URL / prompt-URL testing
  • /lab/upload — file upload interface

Additional concepts mentioned in the design doc: alias management and flow control.

API capabilities the UI must expose

The functional scope is defined by the existing API documentation:

Design direction (summary)

  • Work-focused tool, not marketing — compact typography, tight spacing, like Google AI Studio
  • Dual color system: zinc for layout chrome, slate for forms/cards; purple→cyan accent gradient
  • Lucide React icons only, no emojis
  • Scroll-aware collapsing header, left filter sidebar, contextual footer
  • Responsive 768px1920px+

See design-system.md for the complete spec.

What does NOT exist

There is no PRD with a detailed feature list (gallery filters, prompt list, flow list behavior). The pages above plus the API docs are the only recorded ideas. A proper PRD should be written here before implementation starts.