Full workspace lane
Studio Guide
Studio is the multi-file workspace for production-grade vibe development: editable source, source-vs-runtime preview clarity, and stronger backend integration entrypoints.
Multi-file workspace guidance for serious iteration and release flows.
Implementation focus
Use Studio for modular codebases, imported projects, and any app expected to evolve across multiple releases.
Expected outcomes
- Manage larger project structure without losing public publish velocity.
- Coordinate preview, source, and publish intent from one workspace.
- Attach Pulses and automation safely as the app evolves.
Workspace responsibilities
Studio is the full project workspace. It owns file editing, project structure, preview intent, import/build workflows, publish metadata, release flow, and the handoff between editable source and runnable output.
Studio must keep the source plane and runtime plane conceptually separate. Source files are what the creator edits. Runtime artifacts are the platform-built bundles that viewers execute.
- Use Studio for modular apps, imported repositories, assets, and project-shaped work.
- Preview from the intended runtime entry before publishing.
- Use publish metadata to explain the app for viewers and crawlers.
- Attach Pulses when trusted work belongs server-side.
Preview and publish discipline
A green preview is not the same as a durable release. Preview proves the current workspace can run; publishing records an immutable artifact and updates public discovery surfaces.
If a change alters runtime behavior, source access, public metadata, or backend calls, treat it as a release decision rather than a cosmetic edit.
- Check the live runtime path, not only the editor state.
- Use BUMP IT for the next public cut of the same app.
- Confirm Pulse calls work through same-origin routes before telling users they are production-ready.
Example and read next
Example: you imported a Vite project with assets and a server endpoint. Use Studio to keep source files editable, preview the browser-ready output, attach the Pulse route, and publish an immutable runtime artifact.
Use these related pages when you need the next layer of guidance. They point to the most likely follow-up tasks, not every page that happens to touch the same system.
- Read next: VibeComposer (/docs/composer)
- Read next: BUMP IT (/docs/bump-it)
- Read next: Source & Versions (/docs/source)
- Read next: Automation Safety (/docs/automation-safety)