lhumina_code/hero_videos
0
0
Fork 0
Code Issues 1 Pull requests Projects Releases 1 Packages Wiki Activity Actions

UX: make the creation flow accessible for marketing, redactors, and product managers #1

New issue
Open
opened 2026-05-19 14:11:54 +00:00 by casper-stevens · 3 comments
casper-stevens commented 2026-05-19 14:11:54 +00:00
Member
Copy link

Problem

The current workflow was designed with a developer/AI-operator mental model. For a marketing team or redactor to use it independently, several friction points block them.

1. No way to bring in context from your own files

The only input today is a single free-text "Intent" field (+ voice). There is no way to:

  • Upload or paste a campaign brief, script, or storyboard
  • Attach a brand style guide or visual reference images
  • Reference an existing document to seed the scene generation

For marketing, context is the work. A brief might be a PDF, a Word doc, or a Google Doc excerpt. Without a way to bring that in, users must manually summarise everything into a single text box — lossy and time-consuming.

2. Intent field is too narrow and unstructured

Marketing briefs have structure: audience, key message, tone of voice, call to action, platform/format. A single textarea discards all of that. The AI generates generic scenes because it lacks the context that lives in those fields.

Minimum structured brief fields needed:

  • Target audience
  • Key message / CTA
  • Tone / style
  • Platform & aspect ratio (Instagram Reels 9:16, YouTube 16:9, LinkedIn square…)
  • Duration target

3. Scene prompts are exposed as raw AI prompts

In the Planning step, each scene shows an Image Prompt and a Video Prompt textarea — raw AI generation prompts. A redactor or PM does not know what makes a good Stable Diffusion or Kling prompt. They think in terms of what the scene should show and feel, not model directives.

The interface should let them describe the scene in plain language and handle prompt engineering internally, or at minimum label/hide the technical fields behind an "Advanced" toggle.

4. No brand/campaign context at the collection level

Collections have only a Name. There is no place to attach:

  • A brand kit (logo, color palette, font)
  • A default tone/voice
  • Recurring visual style rules

Every project inside a collection starts from scratch, so brand consistency requires repeating the same context in every Intent field.

5. Pipeline step naming is technical

The steps Planning → Imaging → Video → Assembly map to the system's internal architecture. For non-technical users the natural language is closer to:

Current Suggested
Planning Brief & Storyboard
Imaging Visuals
Video Clips
Assembly Final Edit

This is a label change but it meaningfully lowers the cognitive load for new users.

6. No per-scene editorial notes

A redactor reviewing AI-generated scenes needs to leave written feedback per scene before approving. Right now the only options are "Approve" or edit the raw prompt. There is no notes/comments field, so feedback has to happen out-of-band (Slack, email).

7. No script / storyboard import

Marketing teams often arrive with a pre-written script (numbered scenes, voiceover copy, shot descriptions). There is no way to import that structure — they would have to manually create each scene and fill in the fields one by one.

A plain-text import ("one scene per paragraph" or a simple numbered format) would unlock a large share of real-world workflows.

Acceptance criteria

  • Project creation modal supports file attachment or multi-field brief input alongside or instead of the free-text Intent field
  • Collection record can store brand context (name, style notes, reference) that pre-populates new projects
  • Scene planning view hides raw AI prompts from the default view; users describe scenes in plain language; prompts accessible via "Advanced"
  • Script / plain-text import: paste or upload a structured scene list to pre-populate scenes
  • Platform/format selection (aspect ratio + duration) available at project creation
  • Per-scene notes field available in planning step
  • Step labels reviewed for non-technical audiences

Out of scope for this issue

  • Collaboration / multi-user review flows (separate issue)
  • Video export format options beyond current assembly step
## Problem The current workflow was designed with a developer/AI-operator mental model. For a marketing team or redactor to use it independently, several friction points block them. ### 1. No way to bring in context from your own files The only input today is a single free-text "Intent" field (+ voice). There is no way to: - Upload or paste a **campaign brief**, script, or storyboard - Attach a **brand style guide** or visual reference images - Reference an existing document to seed the scene generation For marketing, context *is* the work. A brief might be a PDF, a Word doc, or a Google Doc excerpt. Without a way to bring that in, users must manually summarise everything into a single text box — lossy and time-consuming. ### 2. Intent field is too narrow and unstructured Marketing briefs have structure: **audience**, **key message**, **tone of voice**, **call to action**, **platform/format**. A single textarea discards all of that. The AI generates generic scenes because it lacks the context that lives in those fields. Minimum structured brief fields needed: - Target audience - Key message / CTA - Tone / style - Platform & aspect ratio (Instagram Reels 9:16, YouTube 16:9, LinkedIn square…) - Duration target ### 3. Scene prompts are exposed as raw AI prompts In the Planning step, each scene shows an **Image Prompt** and a **Video Prompt** textarea — raw AI generation prompts. A redactor or PM does not know what makes a good Stable Diffusion or Kling prompt. They think in terms of *what the scene should show and feel*, not model directives. The interface should let them describe the scene in plain language and handle prompt engineering internally, or at minimum label/hide the technical fields behind an "Advanced" toggle. ### 4. No brand/campaign context at the collection level Collections have only a **Name**. There is no place to attach: - A brand kit (logo, color palette, font) - A default tone/voice - Recurring visual style rules Every project inside a collection starts from scratch, so brand consistency requires repeating the same context in every Intent field. ### 5. Pipeline step naming is technical The steps **Planning → Imaging → Video → Assembly** map to the system's internal architecture. For non-technical users the natural language is closer to: | Current | Suggested | |---|---| | Planning | Brief & Storyboard | | Imaging | Visuals | | Video | Clips | | Assembly | Final Edit | This is a label change but it meaningfully lowers the cognitive load for new users. ### 6. No per-scene editorial notes A redactor reviewing AI-generated scenes needs to leave **written feedback** per scene before approving. Right now the only options are "Approve" or edit the raw prompt. There is no notes/comments field, so feedback has to happen out-of-band (Slack, email). ### 7. No script / storyboard import Marketing teams often arrive with a **pre-written script** (numbered scenes, voiceover copy, shot descriptions). There is no way to import that structure — they would have to manually create each scene and fill in the fields one by one. A plain-text import ("one scene per paragraph" or a simple numbered format) would unlock a large share of real-world workflows. ## Acceptance criteria - [ ] Project creation modal supports file attachment or multi-field brief input alongside or instead of the free-text Intent field - [ ] Collection record can store brand context (name, style notes, reference) that pre-populates new projects - [ ] Scene planning view hides raw AI prompts from the default view; users describe scenes in plain language; prompts accessible via "Advanced" - [ ] Script / plain-text import: paste or upload a structured scene list to pre-populate scenes - [ ] Platform/format selection (aspect ratio + duration) available at project creation - [ ] Per-scene notes field available in planning step - [ ] Step labels reviewed for non-technical audiences ## Out of scope for this issue - Collaboration / multi-user review flows (separate issue) - Video export format options beyond current assembly step
casper-stevens commented 2026-05-21 09:23:31 +00:00
Author
Member
Copy link

Implementation Spec — Issue #1: UX for Non-Technical Users

Objective

Make the hero_videos creation flow accessible to marketing teams, redactors, and product managers by replacing raw-AI-prompt surfaces with plain-language fields, adding structured brief inputs at project creation, surfacing brand/campaign context at the collection level, adding per-scene editorial notes, enabling script/scene-list import, adding platform/format selection, and renaming pipeline steps to audience-appropriate language.

Architecture Context

  • OSchema source of truth: crates/hero_videos_server/schemas/videos/schema.oschema — changing this triggers build.rs which regenerates types_generated.rs, types_wasm_generated.rs, and osis_server_generated.rs. The generated files must never be edited by hand.
  • Parallel hand-written types: crates/hero_videos_app/src/types.rs mirrors the generated types for WASM; it must be kept in sync manually.
  • RPC layer: All business logic lives in crates/hero_videos_server/src/rpc/mod.rs. New RPC methods must also be declared in crates/hero_videos_server/openrpc.json.
  • UI: Dioxus WASM SPA in crates/hero_videos_app/src/. The create_project call currently receives only collection_id, name, and intent — this must be extended.
  • AI pipeline: crates/hero_videos_server/src/providers/ai.rs sends the project intent string to the LLM. New structured fields will be synthesised into intent server-side; no AI interface changes are needed.

Requirements

  • Add style_notes and visual_reference to Collection; display in collection card and pre-populate project brief.
  • Add structured brief fields to Project: target_audience, key_message, tone_style, platform (enum: landscape_16_9, portrait_9_16, square_1_1), duration_target_s (integer).
  • Keep intent as a synthesised string derived from structured fields; the AI interface is unchanged.
  • Add notes (editorial comment) to Scene.
  • Rename pipeline step labels in the UI: Planning -> "Brief & Storyboard", Imaging -> "Visuals", VideoPrompt -> "Video Prompts", Video -> "Clips", Assembly -> "Final Edit".
  • Hide image_prompt textarea behind an "Advanced" disclosure toggle by default; surface a plain-language "Scene Description" input instead.
  • Support script/scene-list import via a paste panel in the Planning step.
  • Platform/format selection at project creation modal.
  • Per-scene notes field in the planning step.
  • Collection creation modal gains style_notes and visual_reference fields.

Files to Modify / Create

File Action Reason
crates/hero_videos_server/schemas/videos/schema.oschema Modify Add new fields to Collection, Project, Scene — triggers codegen
crates/hero_videos_server/src/rpc/mod.rs Modify Extend create_collection, create_project, update_scene; add import_scenes RPC
crates/hero_videos_server/openrpc.json Modify Declare new/changed method signatures and updated schema components
crates/hero_videos_app/src/types.rs Modify Mirror new fields for WASM
crates/hero_videos_app/src/components/collections_page.rs Modify Add fields to New Collection modal; display on card
crates/hero_videos_app/src/components/projects_page.rs Modify Replace single intent textarea with structured brief form; rename step labels
crates/hero_videos_app/src/components/editor/planning.rs Modify Advanced toggle for raw prompts; per-scene notes; script import panel
crates/hero_videos_app/src/components/editor/mod.rs Modify Update step label display

Implementation Plan

Step 1 — Extend the OSchema definition

File: crates/hero_videos_server/schemas/videos/schema.oschema
Dependencies: none

Add style_notes: str, visual_reference: str to Collection.
Add target_audience: str, key_message: str, tone_style: str, platform: str, duration_target_s: u32 to Project.
Add notes: str to Scene.

The intent: str field stays — it is the synthesised string fed to the AI.

After saving, run cargo build -p hero_videos_server to trigger codegen before any other step proceeds.

Step 2 — Sync WASM types

File: crates/hero_videos_app/src/types.rs
Dependencies: Step 1

Add new fields to Collection, Project, and Scene structs with #[serde(default)] so existing stored objects deserialise cleanly.

Step 3 — Extend the server RPC handler

File: crates/hero_videos_server/src/rpc/mod.rs
Dependencies: Step 1 (codegen must have run)

  • create_collection: accept optional style_notes and visual_reference params.
  • create_project: accept optional target_audience, key_message, tone_style, platform, duration_target_s; synthesise intent from them when the free-text override is absent; prepend collection style_notes if set.
  • update_scene: accept optional notes param.
  • New import_scenes method: parse a plain-text numbered scene list and create one Scene per line; replace existing scenes only if none are approved.

Intent synthesis (server-side, no AI call):

Target audience: {target_audience}. Key message / CTA: {key_message}. Tone / style: {tone_style}. Platform format: {platform}. Target duration: {duration_s}s.

Step 4 — Update openrpc.json

File: crates/hero_videos_server/openrpc.json
Dependencies: Step 3

  • Add optional params to create_collection, create_project, update_scene.
  • Add new method import_scenes (params: project_id, script; result: Project).
  • Add new properties to Collection, Project, Scene schema components.

Step 5 — Collections page UI

File: crates/hero_videos_app/src/components/collections_page.rs
Dependencies: Step 2

  • Add style_notes and visual_reference inputs to the New Collection modal.
  • Send them in the create_collection payload.
  • Display style_notes (truncated to 60 chars) below the collection name on the card.

Step 6 — Projects page UI (structured brief)

File: crates/hero_videos_app/src/components/projects_page.rs
Dependencies: Steps 2, 3, 4

  • Replace the single intent textarea with five structured fields: Target Audience, Key Message / CTA, Tone / Style, Platform & Format (select), Target Duration (number input).
  • Hide legacy free-text intent in an <details> "Advanced" disclosure.
  • Rename step labels: Planning -> "Brief & Storyboard", Imaging -> "Visuals", VideoPrompt -> "Video Prompts", Video -> "Clips", Assembly -> "Final Edit", Done -> "Done".
  • Show key_message (or intent fallback) as the project card preview.

Step 7 — Planning step UI

File: crates/hero_videos_app/src/components/editor/planning.rs
Dependencies: Steps 2, 3, 4

Scene card changes:

  • Rename "Image Prompt" label to "Scene Description" with plain-language placeholder.
  • Wrap raw image_prompt VoiceInput in <details><summary>Advanced — AI prompt</summary>.
  • Add "Editorial Notes" textarea (bound to notes, persisted via update_scene).

PlanningStep changes:

  • Add "Import Script" button that shows/hides a paste panel.
  • Paste panel: textarea + "Import Scenes" button (calls import_scenes RPC) + "Cancel" button.

Step 8 — Rename pipeline step labels in editor

File: crates/hero_videos_app/src/components/editor/mod.rs
Dependencies: none (cosmetic only, can run in parallel with Steps 5–7)

Apply same step label mapping as Step 6 wherever pipeline steps are rendered in the editor tab/header.

Dependency Graph

Step 1 (schema + codegen)
    |
    +-- Step 2 (WASM types) ---+-- Step 5 (collections UI)
    |                          +-- Step 6 (projects UI)
    +-- Step 3 (server RPC)    +-- Step 7 (planning UI)
         |
         +-- Step 4 (openrpc)

Step 8 (rename labels) — independent

Steps 5, 6, 7, and 8 can all proceed in parallel once Steps 1–4 are done.

Acceptance Criteria

  • New Collection modal has "Brand / Style Notes" and "Visual Reference" fields; values are persisted and shown on the card.
  • New Project modal shows Target Audience, Key Message / CTA, Tone / Style, Platform & Format, and Target Duration; free-text Intent is hidden in "Advanced".
  • create_project synthesises intent from structured fields; existing free-text intent path is preserved.
  • Platform field is stored on the Project and visible in the project card.
  • Planning scene cards show "Scene Description" label; raw "Image Prompt" is hidden under "Advanced — AI prompt".
  • Each scene card has an "Editorial Notes" textarea; value persists via update_scene.
  • "Import Script" button opens a paste panel; importing a numbered scene list populates scene cards via import_scenes RPC.
  • Pipeline step labels read: Brief & Storyboard, Visuals, Video Prompts, Clips, Final Edit, Done — in project list cards and the editor step header.
  • All existing pipeline functionality continues to work unchanged.
  • cargo check --workspace and WASM check both pass.

Notes

  • OSchema codegen must run before Step 3 Rust code is written — the server RPC handler imports generated types.
  • types.rs is hand-written and must be kept in sync with the schema manually.
  • intent field must not be removed — the AI pipeline reads it directly.
  • image_prompt field must not be renamed — the image generation worker reads it directly; "Scene Description" is a UI-only relabelling.
  • Platform aspect ratio is advisory only in this issue; wiring it into actual image generation is out of scope.
  • import_scenes replaces existing scenes only if none are approved; otherwise appends (to prevent data loss).
## Implementation Spec — Issue #1: UX for Non-Technical Users ### Objective Make the hero_videos creation flow accessible to marketing teams, redactors, and product managers by replacing raw-AI-prompt surfaces with plain-language fields, adding structured brief inputs at project creation, surfacing brand/campaign context at the collection level, adding per-scene editorial notes, enabling script/scene-list import, adding platform/format selection, and renaming pipeline steps to audience-appropriate language. --- ### Architecture Context - **OSchema source of truth**: `crates/hero_videos_server/schemas/videos/schema.oschema` — changing this triggers `build.rs` which regenerates `types_generated.rs`, `types_wasm_generated.rs`, and `osis_server_generated.rs`. The generated files must never be edited by hand. - **Parallel hand-written types**: `crates/hero_videos_app/src/types.rs` mirrors the generated types for WASM; it must be kept in sync manually. - **RPC layer**: All business logic lives in `crates/hero_videos_server/src/rpc/mod.rs`. New RPC methods must also be declared in `crates/hero_videos_server/openrpc.json`. - **UI**: Dioxus WASM SPA in `crates/hero_videos_app/src/`. The `create_project` call currently receives only `collection_id`, `name`, and `intent` — this must be extended. - **AI pipeline**: `crates/hero_videos_server/src/providers/ai.rs` sends the project `intent` string to the LLM. New structured fields will be synthesised into `intent` server-side; no AI interface changes are needed. --- ### Requirements - Add `style_notes` and `visual_reference` to `Collection`; display in collection card and pre-populate project brief. - Add structured brief fields to `Project`: `target_audience`, `key_message`, `tone_style`, `platform` (enum: `landscape_16_9`, `portrait_9_16`, `square_1_1`), `duration_target_s` (integer). - Keep `intent` as a synthesised string derived from structured fields; the AI interface is unchanged. - Add `notes` (editorial comment) to `Scene`. - Rename pipeline step labels in the UI: Planning -> "Brief & Storyboard", Imaging -> "Visuals", VideoPrompt -> "Video Prompts", Video -> "Clips", Assembly -> "Final Edit". - Hide `image_prompt` textarea behind an "Advanced" disclosure toggle by default; surface a plain-language "Scene Description" input instead. - Support script/scene-list import via a paste panel in the Planning step. - Platform/format selection at project creation modal. - Per-scene notes field in the planning step. - Collection creation modal gains `style_notes` and `visual_reference` fields. --- ### Files to Modify / Create | File | Action | Reason | |---|---|---| | `crates/hero_videos_server/schemas/videos/schema.oschema` | Modify | Add new fields to Collection, Project, Scene — triggers codegen | | `crates/hero_videos_server/src/rpc/mod.rs` | Modify | Extend `create_collection`, `create_project`, `update_scene`; add `import_scenes` RPC | | `crates/hero_videos_server/openrpc.json` | Modify | Declare new/changed method signatures and updated schema components | | `crates/hero_videos_app/src/types.rs` | Modify | Mirror new fields for WASM | | `crates/hero_videos_app/src/components/collections_page.rs` | Modify | Add fields to New Collection modal; display on card | | `crates/hero_videos_app/src/components/projects_page.rs` | Modify | Replace single intent textarea with structured brief form; rename step labels | | `crates/hero_videos_app/src/components/editor/planning.rs` | Modify | Advanced toggle for raw prompts; per-scene notes; script import panel | | `crates/hero_videos_app/src/components/editor/mod.rs` | Modify | Update step label display | --- ### Implementation Plan #### Step 1 — Extend the OSchema definition **File**: `crates/hero_videos_server/schemas/videos/schema.oschema` **Dependencies**: none Add `style_notes: str`, `visual_reference: str` to `Collection`. Add `target_audience: str`, `key_message: str`, `tone_style: str`, `platform: str`, `duration_target_s: u32` to `Project`. Add `notes: str` to `Scene`. The `intent: str` field stays — it is the synthesised string fed to the AI. After saving, run `cargo build -p hero_videos_server` to trigger codegen before any other step proceeds. --- #### Step 2 — Sync WASM types **File**: `crates/hero_videos_app/src/types.rs` **Dependencies**: Step 1 Add new fields to `Collection`, `Project`, and `Scene` structs with `#[serde(default)]` so existing stored objects deserialise cleanly. --- #### Step 3 — Extend the server RPC handler **File**: `crates/hero_videos_server/src/rpc/mod.rs` **Dependencies**: Step 1 (codegen must have run) - `create_collection`: accept optional `style_notes` and `visual_reference` params. - `create_project`: accept optional `target_audience`, `key_message`, `tone_style`, `platform`, `duration_target_s`; synthesise `intent` from them when the free-text override is absent; prepend collection `style_notes` if set. - `update_scene`: accept optional `notes` param. - New `import_scenes` method: parse a plain-text numbered scene list and create one `Scene` per line; replace existing scenes only if none are approved. Intent synthesis (server-side, no AI call): ``` Target audience: {target_audience}. Key message / CTA: {key_message}. Tone / style: {tone_style}. Platform format: {platform}. Target duration: {duration_s}s. ``` --- #### Step 4 — Update openrpc.json **File**: `crates/hero_videos_server/openrpc.json` **Dependencies**: Step 3 - Add optional params to `create_collection`, `create_project`, `update_scene`. - Add new method `import_scenes` (params: `project_id`, `script`; result: `Project`). - Add new properties to `Collection`, `Project`, `Scene` schema components. --- #### Step 5 — Collections page UI **File**: `crates/hero_videos_app/src/components/collections_page.rs` **Dependencies**: Step 2 - Add `style_notes` and `visual_reference` inputs to the New Collection modal. - Send them in the `create_collection` payload. - Display `style_notes` (truncated to 60 chars) below the collection name on the card. --- #### Step 6 — Projects page UI (structured brief) **File**: `crates/hero_videos_app/src/components/projects_page.rs` **Dependencies**: Steps 2, 3, 4 - Replace the single intent textarea with five structured fields: Target Audience, Key Message / CTA, Tone / Style, Platform & Format (select), Target Duration (number input). - Hide legacy free-text intent in an `<details>` "Advanced" disclosure. - Rename step labels: Planning -> "Brief & Storyboard", Imaging -> "Visuals", VideoPrompt -> "Video Prompts", Video -> "Clips", Assembly -> "Final Edit", Done -> "Done". - Show `key_message` (or `intent` fallback) as the project card preview. --- #### Step 7 — Planning step UI **File**: `crates/hero_videos_app/src/components/editor/planning.rs` **Dependencies**: Steps 2, 3, 4 Scene card changes: - Rename "Image Prompt" label to "Scene Description" with plain-language placeholder. - Wrap raw image_prompt `VoiceInput` in `<details><summary>Advanced — AI prompt</summary>`. - Add "Editorial Notes" textarea (bound to `notes`, persisted via `update_scene`). PlanningStep changes: - Add "Import Script" button that shows/hides a paste panel. - Paste panel: `textarea` + "Import Scenes" button (calls `import_scenes` RPC) + "Cancel" button. --- #### Step 8 — Rename pipeline step labels in editor **File**: `crates/hero_videos_app/src/components/editor/mod.rs` **Dependencies**: none (cosmetic only, can run in parallel with Steps 5–7) Apply same step label mapping as Step 6 wherever pipeline steps are rendered in the editor tab/header. --- ### Dependency Graph ``` Step 1 (schema + codegen) | +-- Step 2 (WASM types) ---+-- Step 5 (collections UI) | +-- Step 6 (projects UI) +-- Step 3 (server RPC) +-- Step 7 (planning UI) | +-- Step 4 (openrpc) Step 8 (rename labels) — independent ``` Steps 5, 6, 7, and 8 can all proceed in parallel once Steps 1–4 are done. --- ### Acceptance Criteria - [ ] New Collection modal has "Brand / Style Notes" and "Visual Reference" fields; values are persisted and shown on the card. - [ ] New Project modal shows Target Audience, Key Message / CTA, Tone / Style, Platform & Format, and Target Duration; free-text Intent is hidden in "Advanced". - [ ] `create_project` synthesises `intent` from structured fields; existing free-text intent path is preserved. - [ ] Platform field is stored on the Project and visible in the project card. - [ ] Planning scene cards show "Scene Description" label; raw "Image Prompt" is hidden under "Advanced — AI prompt". - [ ] Each scene card has an "Editorial Notes" textarea; value persists via `update_scene`. - [ ] "Import Script" button opens a paste panel; importing a numbered scene list populates scene cards via `import_scenes` RPC. - [ ] Pipeline step labels read: Brief & Storyboard, Visuals, Video Prompts, Clips, Final Edit, Done — in project list cards and the editor step header. - [ ] All existing pipeline functionality continues to work unchanged. - [ ] `cargo check --workspace` and WASM check both pass. --- ### Notes - OSchema codegen must run before Step 3 Rust code is written — the server RPC handler imports generated types. - `types.rs` is hand-written and must be kept in sync with the schema manually. - `intent` field must not be removed — the AI pipeline reads it directly. - `image_prompt` field must not be renamed — the image generation worker reads it directly; "Scene Description" is a UI-only relabelling. - Platform aspect ratio is advisory only in this issue; wiring it into actual image generation is out of scope. - `import_scenes` replaces existing scenes only if none are approved; otherwise appends (to prevent data loss).
casper-stevens commented 2026-05-21 11:00:17 +00:00
Author
Member
Copy link

Test Results

  • Total: 4
  • Passed: 3
  • Failed: 0
  • Ignored: 1

All tests passed. The 3 unit tests in hero_videos_server cover collection CRUD, project CRUD, and all-objects retrieval. The 1 ignored test is a doc-test placeholder in hero_videos_sdk.

## Test Results - Total: 4 - Passed: 3 - Failed: 0 - Ignored: 1 All tests passed. The 3 unit tests in hero_videos_server cover collection CRUD, project CRUD, and all-objects retrieval. The 1 ignored test is a doc-test placeholder in hero_videos_sdk.
casper-stevens commented 2026-05-21 11:01:17 +00:00
Author
Member
Copy link

Implementation Summary

All acceptance criteria from the spec have been implemented.

Changes Made

Schema & types (crates/hero_videos_server/schemas/videos/schema.oschema, crates/hero_videos_app/src/types.rs):

  • Collection gains style_notes and visual_reference fields
  • Project gains target_audience, key_message, tone_style, platform, and duration_target_s fields
  • Scene gains notes (editorial comment) field

Server RPC (crates/hero_videos_server/src/rpc/mod.rs, sockets/mod.rs):

  • create_collection accepts optional style_notes and visual_reference
  • create_project accepts structured brief fields; intent is synthesised server-side from them (collection style_notes is prepended as brand context when set); free-text intent override is still accepted
  • update_scene accepts optional notes
  • New import_scenes method: parses a numbered plain-text scene list and populates scene cards (appends if any scene is already approved, replaces otherwise)

OpenRPC spec (crates/hero_videos_server/openrpc.json):

  • All method signatures and schema components updated to match

Collections page (crates/hero_videos_app/src/components/collections_page.rs):

  • New Collection modal has "Brand / Style Notes" and "Visual Reference" fields
  • Collection cards display style_notes (truncated to 60 chars) below the name

Projects page (crates/hero_videos_app/src/components/projects_page.rs):

  • New Project modal replaced the single intent textarea with structured fields: Target Audience, Key Message / CTA, Tone / Style, Platform & Format (select), Target Duration — with a collapsible "Advanced" section for a free-text intent override
  • Project card preview now shows key_message (falls back to intent)
  • Pipeline step labels updated: Planning → Brief & Storyboard, Imaging → Visuals, Video → Clips, Assembly → Final Edit

Planning step (crates/hero_videos_app/src/components/editor/planning.rs):

  • Scene cards show "Scene Description" label with plain-language placeholder; raw image prompt is hidden behind "Advanced — AI prompt" disclosure — both inputs control the same underlying field
  • Each scene card has an "Editorial Notes" textarea persisted via update_scene
  • "Import Script" button opens a paste panel; submitting calls import_scenes RPC and populates scene cards

Editor step labels (crates/hero_videos_app/src/components/editor/mod.rs):

  • Step header labels updated to match: Brief & Storyboard, Visuals, Video Prompts, Clips, Final Edit

Test Results

  • Total: 4 | Passed: 3 | Failed: 0 | Ignored: 1
  • cargo check --workspace and WASM check both clean

Acceptance Criteria Status

  • New Collection modal has "Brand / Style Notes" and "Visual Reference" fields; values are persisted and shown on the card
  • New Project modal shows Target Audience, Key Message / CTA, Tone / Style, Platform & Format, and Target Duration; free-text Intent is hidden in "Advanced"
  • create_project synthesises intent from structured fields; existing free-text intent path is preserved
  • Platform field is stored on the Project and visible in the project card
  • Planning scene cards show "Scene Description" label; raw "Image Prompt" is hidden under "Advanced — AI prompt"
  • Each scene card has an "Editorial Notes" textarea; value persists via update_scene
  • "Import Script" button opens a paste panel; importing a numbered scene list populates scene cards via import_scenes RPC
  • Pipeline step labels read: Brief & Storyboard, Visuals, Video Prompts, Clips, Final Edit, Done
  • All existing pipeline functionality continues to work unchanged
## Implementation Summary All acceptance criteria from the spec have been implemented. ### Changes Made **Schema & types** (`crates/hero_videos_server/schemas/videos/schema.oschema`, `crates/hero_videos_app/src/types.rs`): - `Collection` gains `style_notes` and `visual_reference` fields - `Project` gains `target_audience`, `key_message`, `tone_style`, `platform`, and `duration_target_s` fields - `Scene` gains `notes` (editorial comment) field **Server RPC** (`crates/hero_videos_server/src/rpc/mod.rs`, `sockets/mod.rs`): - `create_collection` accepts optional `style_notes` and `visual_reference` - `create_project` accepts structured brief fields; `intent` is synthesised server-side from them (collection `style_notes` is prepended as brand context when set); free-text intent override is still accepted - `update_scene` accepts optional `notes` - New `import_scenes` method: parses a numbered plain-text scene list and populates scene cards (appends if any scene is already approved, replaces otherwise) **OpenRPC spec** (`crates/hero_videos_server/openrpc.json`): - All method signatures and schema components updated to match **Collections page** (`crates/hero_videos_app/src/components/collections_page.rs`): - New Collection modal has "Brand / Style Notes" and "Visual Reference" fields - Collection cards display `style_notes` (truncated to 60 chars) below the name **Projects page** (`crates/hero_videos_app/src/components/projects_page.rs`): - New Project modal replaced the single intent textarea with structured fields: Target Audience, Key Message / CTA, Tone / Style, Platform & Format (select), Target Duration — with a collapsible "Advanced" section for a free-text intent override - Project card preview now shows `key_message` (falls back to `intent`) - Pipeline step labels updated: Planning → Brief & Storyboard, Imaging → Visuals, Video → Clips, Assembly → Final Edit **Planning step** (`crates/hero_videos_app/src/components/editor/planning.rs`): - Scene cards show "Scene Description" label with plain-language placeholder; raw image prompt is hidden behind "Advanced — AI prompt" disclosure — both inputs control the same underlying field - Each scene card has an "Editorial Notes" textarea persisted via `update_scene` - "Import Script" button opens a paste panel; submitting calls `import_scenes` RPC and populates scene cards **Editor step labels** (`crates/hero_videos_app/src/components/editor/mod.rs`): - Step header labels updated to match: Brief & Storyboard, Visuals, Video Prompts, Clips, Final Edit ### Test Results - Total: 4 | Passed: 3 | Failed: 0 | Ignored: 1 - `cargo check --workspace` and WASM check both clean ### Acceptance Criteria Status - [x] New Collection modal has "Brand / Style Notes" and "Visual Reference" fields; values are persisted and shown on the card - [x] New Project modal shows Target Audience, Key Message / CTA, Tone / Style, Platform & Format, and Target Duration; free-text Intent is hidden in "Advanced" - [x] `create_project` synthesises `intent` from structured fields; existing free-text intent path is preserved - [x] Platform field is stored on the Project and visible in the project card - [x] Planning scene cards show "Scene Description" label; raw "Image Prompt" is hidden under "Advanced — AI prompt" - [x] Each scene card has an "Editorial Notes" textarea; value persists via `update_scene` - [x] "Import Script" button opens a paste panel; importing a numbered scene list populates scene cards via `import_scenes` RPC - [x] Pipeline step labels read: Brief & Storyboard, Visuals, Video Prompts, Clips, Final Edit, Done - [x] All existing pipeline functionality continues to work unchanged
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
development
main
integration
latest
v0.1.2
v0.1.1
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
lhumina_code/hero_videos#1
No description provided.