Skip to content

FAQ & Glossary

No. Studio is your draft and editing environment. Changes affect the live site only after you publish.

Should I start from a URL import or from scratch?

Section titled “Should I start from a URL import or from scratch?”

Use URL import when you already have a public site and want a faster first draft. Use scratch when the site should be built primarily from your brief and assets.

Why can’t Vivd import some public websites?

Section titled “Why can’t Vivd import some public websites?”

Some websites block automated browsers or traffic from datacenter IP ranges. Vivd’s importer uses the scraper service to load the source site in a headless browser, so Cloudflare challenges, CAPTCHAs, 403 responses, or IP-based blocking can stop the import even when the site is public. Self-hosted installs can route the scraper through a residential proxy with PROXY_HOST, PROXY_PORT, PROXY_USERNAME, and PROXY_PASSWORD. Read Import an Existing Website for the fuller explanation and Self-Host Config Reference for the env setup.

Do I have to configure plugins before every project?

Section titled “Do I have to configure plugins before every project?”

Only if the project needs those capabilities. Contact forms and analytics are project-level decisions, not mandatory for every site.

Can customers access only their own project?

Section titled “Can customers access only their own project?”

That is the intended client-editor pattern. Keep access limited to the smallest useful scope.

The team or client space that owns projects and user access.

A website workspace inside Vivd, including versions, assets, plugins, and publish state.

The editing environment where you make AI-assisted and direct changes to the project.

The current work-in-progress version of the site inside Vivd.

The published version currently served on the public domain.

The pre-launch review step used to catch obvious issues before a version goes live.