Two related products, different execution paths
Web Spark is the specialist website studio with Discover, Plan, Design, Build, Review and Launch stages. Work Mode is the broader Vulcan Intelligence environment for supported actions, connected accounts and deliverables. The products complement each other, but they do not automatically share every tool or approval.
For an existing Web Spark project, open that project in its Studio and use its page selection, agent questions and exact release workflow. The Work catalog reviewed for this collection does not register a general Web Spark project-editing or publishing action.
Use Work to prepare inputs for the studio
Help me write a Web Spark brief for our electrical company. Use the approved services, territory and brand notes below. Suggest a service-page structure and customer journey. Leave it as a brief; do not create, edit or publish a website.
This is useful preparatory writing. Review the facts, then place the brief and approved assets into the correct Web Spark project. A generated brief or image does not prove it was added to the project or included in its next release.
Use plugin workflows for separately connected websites
For a customer website whose source is in GitHub, connect the exact repositories and review changes on a branch. For Vercel delivery, select the customer’s team and project; previews and production are separate targets. Desktop Commander can work with selected computer files when the device is online and authorized.
An existing Git-linked site should be updated through its repository. Do not replace it with a partial file upload. A Git commit is not a deployment, and a provider-ready deployment is not the same as a checked public page.
Pick the right guide
- Web Spark field guide — setup, specialist agents, page editing, hosting, domains and launch.
- GitHub connection — selected repositories, branches and reviewed source changes.
- Vercel connection — customer previews, exact commit deployment and domain handoffs.
- Desktop Commander connection — selected files and separately approved terminal work.
A clear website-change request
Name the website and its actual hosting/editor path. State the exact page, approved content, what must stay unchanged and whether you want a draft or a public release. Ask for proof at the appropriate level: saved Studio draft, commit, preview URL or verified public page.
When you only want a concept, say so. When the requested capability is unavailable, use the owning editor instead of treating a conversational design suggestion as a completed change.