The community member is new to Web Studio and has questions about its workflow, particularly regarding integrating a headless CMS like Dato CMS and deploying the site. The comments indicate that Web Studio supports dynamic updates from a headless CMS without the need for a full rebuild, and that the site can be deployed anywhere, not just on Web Studio's cloud. However, there is no definitive answer on whether a static site can be generated and deployed to Netlify while still allowing dynamic updates from the CMS. The community member is encouraged to review the Web Studio documentation to find the answers.
Hi everyone, I'm new here. Web studio came on to my radar a while back and certainly ticked a lot of boxes for me, however my lack of understanding how it all works in totality means I have some unanswered questions I come from a web design/web dev hybrid background I had been using quite an old stack for a lot of my projects , Middleman as the SSG, datoCMS as headless CMS and netlify for the build and hosting. I push code changes to a git respository which also allows for continuous deployment I was able to allow clients to make edits on the CMS and then using a webhook force a deploy to netlify I was wondering is a similar workflow is possible using webflow, either with or without a git repository Specifically the use case when a client makes an edit in the CMS, can the build command be iniitiated Thanks for any insights Dave
aghh, so the website does not need to be rebuilt in order to generate new dynamic pages. Does this only apply if the site is hosted on webstudio cloud or could i also host/deploy it to netlify or vercel and have changes in headless CMS be reflected immediately on the production website
Also on a related note, does your software support datoCMS as a headless CMS provider. I saw them in one table of headless CMSes on your website but then not shown in the headless CMS compatible list??
ok so i could download the builder locally..connect to datocms as a headless CMS and when someone makes an edit in datocms the whole website is available in its most up-to-date state on netlify WITHOUT any additional buildprocess required
So I build and deploy once and then all headless CMS updates are just published automatically?
I need to get my head around this as I am used to SSG that need to be rebuilt everytime there is an update to code or addtion to CMS content
Can you point me in the direction of some documentation/yt tutorials/examples that will help me understand this more and have a go at migrating one of my projects from middleman
I am working through the docs and no doubt will get this all figured out
until then are you able to let me know if
a.) I can generate and deploy a static site, that is built locally and hosted on netlify and populated with content from a headless CMS like datoCMS and redeployed every time a change is made in the headless CMS? [cause like it is static and I love the benefits of static website over dynamic but I need it to be able to change based on the CMS] b.) I can build a SSR that will automatically update content on the website when headless CSM content is edited and deploy this SSR to netlify or vercel [note i have not ruled out using your cloud i just don't know enough aboit it yet]( I haven't reached this point in the docs yet, but please indugle me, I just wanna make sure I invest time in somethng that will give me the flexible approach I may need for various projects . If I am sure i will then invest more time in learning the platform/stack. I like what I see so far. It doesn;t align completely with my current workflows but I am open to some change if i think it will in the long run give me the flexibility I want.
Does using the local version of your tool come with any restrictions i need to know about from the get go vis-a-vis what I can or cannot do with headless CMSes going forward
Final little aside question ( I am a man of many questions!! lol)
Is there a way to have an html design (like a theme I have paid for) and sort of import it into the tool and have the tool 'convert' it to webstudio format, and maybe then store it as some sort of design template resource from whcih i can create reusable design components OR does all design have to be done from scratch
now i know you either have a permenant [facepalm] right now or maybe your screaming at the screen 'read the effing docs Dave!'...and i will I will I just like covering a few bases to make sure i have decided on the best tool for me and how I work.
