Webstudio
Log in

Join the Webstudio community

Home
Members
Samuel Gregory
S
Samuel Gregory
Offline, last seen 3 months ago
Joined December 13, 2024
SSamuel Gregory
·

Ability to transfer projects

I couldn't find this in the ideas or suggestions over on Github so thought I'd add. Would be great to transfer projects, especially as the only way to log in is with personal Google or Github accounts. This means building for clients is pretty impossible as I'm not about to give them my personal Gmail or Github and they aren't either
21 comments
S
O
J
P
M
SSamuel Gregory
·

Legality and ethics of using a Webflow theme in Webstudio.

or ANYONE,

Wanted to guage the ethics/legality of buying a theme on Webflow and using the copy/paste feature to get it into Webstudio. Can anyone see a problem with this either from a T’s and C’s perspective or even morally?
9 comments
O
J
S
SSamuel Gregory
·

'Optimize' breaks externally linked image assets

I haven't done extensive research but I'm linking to an external image asset and when I built my project for Vercel, the image did not load. The url was relative.

I had a hunch, turned the 'optimize' feature off and this is now working.
2 comments
S
SSamuel Gregory
·

Issues with CLI to Vercel

I'm having some issues deploying my website to Vercel. Ran through the normal commands whenever I've updated my website and when I ran webstudio sync I didn't get a success message or error (the message is now lost into the ether, something with a URL in it). I then tried building npx webstudio build --template=vercel and then pushing to Vercel npx vercel deploy --prod but I never saw any updates.

So I decided to start from scratch. Delete my project locally.

npx webstudio-cli

but I get the following error

Plain Text
◇  The project is linked successfully
│
◇  Where would you like to deploy your project?
│  Vercel
│
◇  Would you like to install dependencies? (recommended)
│  Yes
│
◇  Project data synchronized successfully
│
◇  Scaffolding the project files
Error: ENOENT: no such file or directory, open 'app/route-templates/html.tsx'
    at async open (node:internal/fs/promises:641:25)
    at async readFile (node:internal/fs/promises:1254:14)
    at async createFramework (file:///Users/samuelgregory/.asdf/installs/nodejs/22.2.0/.npm/lib/node_modules/webstudio/lib/cli.js:455:24)
    at async prebuild (file:///Users/samuelgregory/.asdf/installs/nodejs/22.2.0/.npm/lib/node_modules/webstudio/lib/cli.js:716:17)
    at async build (file:///Users/samuelgregory/.asdf/installs/nodejs/22.2.0/.npm/lib/node_modules/webstudio/lib/cli.js:1160:3)
    at async Object.initFlow [as handler] (file:///Users/samuelgregory/.asdf/installs/nodejs/22.2.0/.npm/lib/node_modules/webstudio/lib/cli.js:1239:3) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: 'app/route-templates/html.tsx'
}
18 comments
B
S
O
SSamuel Gregory
·

Is there a need for Canonical for WebStudio sites?

Given we need to publish the site to be able to sync and deploy to Vercel, this means 2 sites are live on different URLs.

Does the WebStudio version somehow recognised its been synced/linked and deindex itself? If canonical is required, is there a recommended way to do it?
4 comments
S
J
O
SSamuel Gregory
·

Create a dynamic background image

Settings > Properties > +

Create 'style' and set the value as a dynamic value (purple circle) and set "background-image: url(" + 'Collection Item'.field.image_url + ")"

(or whatever the route to your image is)
8 comments
M
B