Landing Page

The CHAT dock layout is implemented, and the /landing and landing.localhost routes resolve the landing entry experience. These routes load the editor; CHAT remains available as a factory favorite. Its durable factory identifier remains factory-start for project compatibility.

Goal

Keep the working editor directly reachable through a minimal, layout-based front-facing surface with AI chat, project-media handling, and an Open action.

Dev URLs

URL	Behavior
`http://localhost:5173/`	Editor using the last active layout
`http://landing.localhost:5173/`	Resolves the landing entry experience and loads the editor bundle
`http://localhost:5173/landing`	Same landing entry experience when the subdomain is unavailable

Implementation Notes

CHAT is a protected factory layout and a default favorite immediately to the right of 3D EDIT.
The layout is one full-size, layout-only panel; it is intentionally hidden from the generic panel pickers and has no tab strip or editor toolbar.
Landing entry selection loads the editor bundle. The landing surface itself is the start dock panel; there is no separate page layered over the editor.
When CHAT is active, the visible controls are a responsive AI chat pill, top-right Mail, Project, and Open actions, project-file previews, and a finished-video preview when an output is present. Files can be dropped anywhere on the surface for import.
Account access is owned by the route shell rather than the full editor layout. Login, pricing, account, redeem, and successful auth-return dialogs therefore work consistently on /landing, /chat, and /editor, with one shared overlay host above entry transitions.
The project picker offers a new project, an explicit Open project action, and recent project files. Project toggles these choices inside Chat instead of opening the native folder picker immediately. A second Project click closes the choices and restores the last selected project.
Browser tabs keep independent project selections and chat-session routing. Refreshing one /chat tab restores that tab’s project instead of adopting the project or session currently active in another tab.
Project-file previews expose a small remove action. Removing media uses the shared media deletion path and asks for confirmation when the source is still referenced by timeline clips; document and text entries use their corresponding project stores.
Open loads the factory VIDEO EDIT layout in place and reuses the existing 400 ms dock transition. Media, Preview, the right-side tools, Timeline, and toolbar enter as a compact overlapping sequence.
Before the panels enter, the chat pill contracts symmetrically along the x-axis and fades away during the first 120 ms.
The staged reveal uses the dock layout transition in sequence mode. Media, Preview, and Timeline are eligible for live-surface animation; other layout elements may use transition clones.
The light Chat surface remains fixed underneath the whole sequence. Loading CHAT from the favorite bar runs the same sequence in reverse: the gray editor panes leave stage by stage and reveal the light surface.
Split handles stay transparent while the light surface is exposed, so the final editor grid is not drawn over the transition background in advance.
The global toolbar enters from above during the compact transition when leaving CHAT. When returning, it becomes an overlay and exits upward while the dock expands underneath it. CHAT is also detected from its actual root panel, so project hydration cannot accidentally leave the toolbar visible.
On the reverse transition, existing splitter lines fade out instead of disappearing in a single frame.
Startup dialogs stay paused during the transition so they cannot cover the layout reveal.
Enter submits; Shift+Enter keeps multiline input available. Focus, disabled, loading, and screen-reader feedback states are built in.
Submitting the chat starts a resumable background job: it prepares a single source video when available, runs a FlashBoard AI chat turn, and renders the current timeline. Hosted AI chat can require authentication and credits.
While the job is active, the chat pill reports authoritative runtime phases instead of a static thinking state. Snapshot reads, transcript collection, footage preparation, planning, read-only inspection, edit operations, verification, commit/rollback, and rendering update the visible headline; multi-operation edits also show their current/total count. The last three completed phases remain visible as a compact trail.
Desktop centers the landing content. Narrow screens retain the centered layout with safe-area padding; they do not dock the pill above the safe area.
Hosted Pages requests outside the supported editor, landing, admin, credit-claim, and legal paths return 404 instead of loading the editor fallback.
The dock-layout model is the implementation. Routing selects the landing experience.