It's all about perspective... viewing projects for what their intent really is & adding additional functionality on top of that if needed. Components, Modules & Progressive Enhancers... planning projects and trying to construct scaleabilty can be just as time consuming, if not more, as it is to actually write the code. Great stream! Thanks for your insight & enjoy State-Of-Flow!
@shaunsavage35992 жыл бұрын
Thanks Finsweet! This is exactly what I was hoping you’d cover
@freshlesh30197542 жыл бұрын
Thanks for the tutorial. Looking forward to the SweetJS
@alex-pattison2 жыл бұрын
Thanks for sharing!
@GregDolan2 жыл бұрын
Great tutorial lads, cheers 🙌
@djryanashton Жыл бұрын
It's interesting. So really, you're simply building a template in Webflow and then doing the rest in Svelte. Now that Figma has all those developer tools and dev-mode, could one do the same with Figma?
@labruda Жыл бұрын
Watching this today. Now with DevLinks out, this changes entirely right? Now using a framework will be actually easy simpler. Are you planning on doing.a stream on that? :)
@neoniquestudio2 жыл бұрын
Interesting stream - but I´m wondering if it really makes sense to kinda "force" pure dev-tools into Webflow. If you are a developer and know how to work with those frameworks, I think you won´t work with Webflow anyway. And the other way too: if you are design-oriented web-dev and love using Webflow, you probably are overwhelmed with a framework. 🤔 But ... since Alex is building something to bring both worlds together, so I´m looking forward to that! 🤪
@Mexad0n2 жыл бұрын
Thanks guys for nice content, it is nice to see how to hack WF but like was mentioned no one of these hacks are ideal to be used in production within WF. Svelte example you have shown on {F website is nice and make sense to use it this way as component. This bring me back to thought I had a few months ago that for me will be ideal to use WF just as UI Build tool that will generate HTML into Svelte component, or have custom build svelte components in sidebar to build from and Sveltekit as engine as it has many futures build in like Actions, Basic animations Routing, allows server-side code run etc.etc. and have option to store data in any DB or CMS of choice based on project complexity like Supabase or Planet Scale using their features like authentications etc. But this is not "no-code" way. Thanks again for great content.
@samuel_ahmed2 жыл бұрын
I keep missing the live streams... I have a quick question though: can we use webflow with external databases and incorporate user functions without using membershipstack?
@Blackfeet Жыл бұрын
did you figure this out?
@juannoguera59182 жыл бұрын
Why didn't you talked about jquery?
@neoniquestudio2 жыл бұрын
I´m not a dev but I think jquery is "just" a library, not a framework 🤔
@chakhmanmohamed94362 жыл бұрын
The decision of Fs to make these as live long videos is bad in my opinion. Ppl usually don't have time to watch it live so they get back to it later but they are sooo long. I wish if they kept it less than 30 mins and on point.
@hellomaitrik94742 жыл бұрын
The decision of finsweet to make live episode is so that they can explain you live like you are studying in a school and then asking questions to teacher on the sub topics you didn't quite get it.
@thecommentingguy34872 жыл бұрын
There's decades worth of quality tooling thats actually built to serve devs needs. Webflow is not one of them. At best this idea is reckless to make young devs think that this is how they should be building sites for clients, and thats not even speaking on the countless issues with webflow that make it a sub-par choice for people who actually know what they're doing. I'm sure alex is a very talented dev, but this type of content just feels like its chasing the seo clout of putting 'webflow' in the title
@alexiglesias_me2 жыл бұрын
Hey @thecommentingguy! We're just giving people options, we're not encouraging anyone to start using JS frameworks on their Webflow projects. During the stream I made sure we talked both about the pros and cons of each option, and stated that neither of these are the ones that we use in Finsweet in our day to day development.