Would be nice to have custom code changes visible in the designer rather than publishing to see changes
Double Standards in the South Korean Government's Response to Shincheonji and Sarang Jeil Church. They have been unfair to Shincheonji, but they have not prosecuted Sarang Jeil Church which explicitly went against government orders of not meeting together and told congregants to not get tested
Click to find out more > christian council of korea
Yes, the developer must change the constructor. At the moment, it is not very convenient to edit the site template. krunker io For convenience, you need to add a button and a panel for editing.
This needs to be top priority. Can we prioritise this please?
Finally i find my best code inside designer here thank you. العاب بنات free codes i like it so much good job bro.
This will become essential. happy wheels free Being able to create "section templates" will allow editors extra freedom to create more, and will ease the designers work load. It got to be optional, of course, so we can prevent the careless editor to break the website.
Please I love webflow as a designer but not being able to seamlessly integrate with front-end developers and not being able to import code back into webflow is a deal breaker for using it with my company. Unfortunately is making me look into other options such a sitejet.com if you could just add code editing similar to them I would be so happy as I would finally be able to fully integrate it into our work environment.
This request should be merged with this one: https://wishlist.webflow.com/ideas/WEBFLOW-I-42
Yes, it would be very helpful to see custom code live in the designer!
To extend this, it would be great to simply click on the code within the designer, and change the existing CSS, rather than needing to put it in the <head>.
The style tag is good for a few lines of code but for large chunks of code a editor in webflow that put the code inside the css stylesheet will be nice, also a toggle switch to enable js in the designer!
I agree, although I'd like to see the things this is usually used for implemented first :) (eg pseudo classes, breakpoints...)
I hadn't thought of a debug URL with auto refresh – that could work!
Pretty much every site I build has custom code of some sort – being able to see the effects without having to refresh would be helpful.
(this is from a post that was specific to pseudo classes but works for any CSS):
I found out the other day from @samliew that if you add an embed element to your page containing <style> [add pseudo classes here] </style>, the effects of the code will be reflected in the webflow preview.
<style> [add pseudo classes here] </style>
Part of the pain for me was having to publish to see the effects of any pseudo classes I added as custom code – at least this way I can see the effects directly in the editor (it feels a bit weird adding <style> blocks outside of the <head> but I can get over that!).
I'm sure this is probably old news to some but finding this out has really helped me use pseudo classes until webflow figure out how to give support in the editor.
…or maybe some kind of debug url that has auto refresh?
You won't be notified about changes to this idea.