I've used the starter template, and run through Liquify and it works great.
During the conversion, I noticed it converts the reference to webflow.js into /assets/webflow.js.liquid.
Then, in the theme it references as {{ 'webflow.js' | asset_url }} and indeed it loads fine.
However, with my OWN webflow project I get a different behavior. I've generated a webflow from Relume, and I've added the webflow.js reference into the <head> in the site settings. On conversion, it does the same thing, creating an asset of 'webflow.js.liquid' - however, it won't load and it 404s. I'm not sure what the difference is or why it's not loading the same. Theme.liquid references it in the exact same way.
Hi - new to Liquify and kicking the tires. I would like to make sure that I understand this workflow correctly.
After the initial commit I make to my connected repo, any new pages that I create in my webflow project won't be converted into liquid page templates; but if I do create new sections (with the li-section tag) those will be merged and created in the published template, is that correct?
What about updating and changing those sections? Or, once published, do I have to do all of that in the theme files? If so, any guidance on keeping synched with my webflow project?
I can see both sides of this, but from a development workflow, this methodology has some gaps as well. When early in a project of developing a theme, much can change and it just means that the proper way to set this up is not necessarily a github flow, but to convert and manually upload the theme .zip.
