31

How do you use Webflow when you prefer to write/edit code?

over 5 years ago from , Web Designer / Front-end Developer

Hi DN,

I'm not sure if i'm alone here, but I don't like these types of programs and here's why:

I do think Webflow is one of the best solutions out there, but I just don't see how these types of programs will ever work. There is a constant battle to have the latest technologies implemented and I just see it eventually falling behind.

I love writing raw code, and seeing it all come to life is where I get my kick from, these programs just seem artificial in a sense. Putting blocks onto a page and creating interactions with clicks just seems unnatural.

In Webflows case, you can't edit your generated code (unless you download it), which is not how I like things. I like to get dirty with my code. I want to be able to say, yeah...all that code, came from a certain sequence of keyboard presses, from my brain! I'm awesome! If Webflow were to help me with that, that would be better. I just feel like these programs are trying to control too much.

These programs should help you and guide you down the right way, and every time I look at one of these, I feel like I did the first time I had Dreamweaver put in from of me, but I was able to do it myself, learn myself and Dreamweaver may not be the best program for coding but it auto-completed things for me, closed my tags, showed me more options in my css and ultimately helped me better my coding skills.

In conclusion, I'd like to end it with a quote: ‘Our AI systems must do what we want them to do,’ - Steven Hawking Though this is referring to artificial intelligence, I think this can be applied here.

57 comments

  • Vlad Magdalin, over 5 years ago (edited over 5 years ago )

    Ouch. I'm the founder of Webflow, and it stings a bit to see that sort of title on top of DN :|

    Webflow's mission is to give people the power to build the future of the web, and for us "people" is defined as all people, not just developers who know how to write code. You'd be surprised to know that a paltry 0.25% of the world's population knows how to code, which means the other 99.75% don't have the kind of power that you might. The point of Webflow is to start unlocking that ability for those who may not be that skilled in writing code, or are starting from zero.

    15 years ago, there was plenty of similar language about blog publishing tools. Some people "hated" Blogger, Wordpress, Movable Type, etc - because at first they were so limited and you could do so much more if you were a programmer building everything from scratch. But despite those complaints, these tools opened up the power of personal publishing to hundreds of millions of people, many orders of magnitude more than the maybe tens of thousands who were publishing their thoughts online previously (because they happened to know the right mix of HTML, CSS, and FTP skills). Over the years, these tools improved to where today it makes very little sense to build your own CMS or blogging engine from scratch.

    Webflow is in a similar category - we're just now beginning to scratch the surface to help non-technical people harness the power of the open web platform. It has been life changing for thousands of designers who don't have a coding background. We've also heard from hundreds of proficient coders who use Webflow regularly to accelerate their workflow (seriously, who wants to remember the exact syntax of a CSS radial gradient?). Over time, Webflow will become more and more powerful, so what you see today may not work for you - but in two years, who knows?

    Believe it or not, the web platform is actually getting more and more complex over time. When I started in web development in 2000, all I needed was a book and a copy of Dreamweaver, and I pretty much knew the ins and outs of building websites. Today, a designer starting out from scratch has such a paradox of choice in toolsets that it's really intimidating just to figure out the basics. Off the top of my head, here are the things I'd have to tell a creative person about just to publish a basic site - HTML5, CSS3, Saas, LESS, Grunt, Gulp, Bootstrap, Sublime, minification, uglification, compression, caching, CSS prefixes, cross-browser issues, media queries, mobile first design, etc etc. That is incredibly daunting for someone just starting out, and that's why Webflow exists. We help centralize and implement a lot of that knowledge so creative people don't have to worry about it, and we strive to make the workflow so flexible that you don't lose the precise level of control that all other WYSIWYGs take from you.

    As a testament to that, look at all the real/production sites that have been created with Webflow: https://webflow.com/gallery or https://webflow.com/discover/popular

    54 points
    • Taron GhazaryanTaron Ghazaryan, over 5 years ago

      Don't let it get to you. I know how to write code and I still prefer webflow because of its speed. Saying you hate webflow because it doesn't allow you to write code is like saying you hate Adobe Illustrator because it doesn't allow you to edit photos.

      Different tools for different purposes.

      19 points
    • Liam MaddisonLiam Maddison, over 5 years ago

      Hi there Vlad,

      I'd firstly like to apologize for the strong header, all I wanted was to start a healthy conversation and I think you can now see your market a little better (not saying you need more knowledge of any sort).

      I agree for a designer, this is a very proficient tool, and can help in many ways.

      I just hate the way it isn't 100% flexible, and that is what makes Dreamweaver a long lasting tool, is that I aids you, doesn't tell you how your code should and shouldn't be or what you can or can't do, due to software restrictions.

      You can obviously tell i'm very skeptical about this type of software, and it's only because I think coding is a huge skillset to have, applying this to a piece of software is almost impossible.

      I will agree as anyone else will too, that your tool is good. I am not saying it's bad, just the fact that it structures my markup and I can't be completely flexible is all that irritates me.

      Maybe there should be two sides of the program, where you give a markup guide on how to write HTML for Webflow so that you can import and export sites, this would be awesome, and allow the user to edit the markup!

      Anyway, they are just my thoughts.

      Thanks for replying!

      2 points
      • Luke SeeleyLuke Seeley, over 5 years ago

        It's hard to have a "healthy conversation" with statements like "I just hate the way it isn't 100% flexible".

        2 points
    • Liam MaddisonLiam Maddison, over 5 years ago

      Also forgot to add, that with these sort of hypes, employers choose to use these programs within their business and what happens then? designers/developers need a new skillset to acquire a job.

      Employers will be more inclined to hiring someone who knows the used software within the business, which in turn is outrageous, because I could easily be better than that person at the job in general.

      You can create websites with Webflow, but I only see this being used as a prototyping tool, which in this thread has been one of the only arguments.

      0 points
    • Daniel SieradskiDaniel Sieradski, over 5 years ago

      +1. On that note I highly recommend Douglas Rushkoff's "Program or Be Programmed."

      0 points
  • Tom WoodTom Wood, over 5 years ago

    Perhaps for you, but the ability to rapidly create a very slick looking site with frankly awesome animations (and for free) is very appealing.

    I could do without the "Sponsor" icon on DN being green - cos I've clicked on it 3 times thinking it was an "Ask" icon, but nevertheless I was impressed with what I saw.

    Webflow isn't meant for you - which is why you'll always create something far more individual and probably better - but if you don't want to invest the time in coding from scratch I can't fault webflow.

    16 points
  • Nathan HueningNathan Huening, over 5 years ago (edited over 5 years ago )

    tl;dr "The world should conform to my views and every product should exist to meet my needs. I am threatened by new technology that might obsolete my skill set in narrow, specific ways."

    Lots of different kinds of people out there. Lots of different kinds of unmet web needs. It's OK for other engineers and product teams to meet needs that you are not and don't want to.

    I'm sure you didn't intend to write a troll-ish inflammatory headline, but you sure got the discussion you wanted!

    13 points
  • Juan SolanoJuan Solano, over 5 years ago (edited over 5 years ago )

    As others have mention, you are probably not the target for Webflow, and neither I am. I also prefer to do the code by myself, I know how and I can do it reasonably fast, there is no need for me to spend time learning this new tool.

    However I have recommended it to my Designer peers and they have found tremendous value on it. They can prototype stuff without paying someone and can have a greater communication with their client.

    7 points
  • Drew AlbinsonDrew Albinson, over 5 years ago

    I find Webflow a useful tool, but not for the reasons they want me to. They're boasting code-free web dev+design, which isn't anything new (although they're doing it a little better). I agree that this type of product isn't to the point where it can replace raw code, and frankly I don't think it ever will be as those on the cutting edge of new web technologies will always be deep in their text editors.

    The way that I use Webflow is as a tool for rapid prototyping. Yes, I could use a framework to do this fairly quickly and get something off the ground, but when my clients or boss would like to see some sort of mockup or wireframes first, I now use Webflow to do essentially what I used to do in Photoshop with comps and I can quickly produce a working prototype. Yes, this is still wasted time in a way, but it helps me wrap my mind around the project and think ahead further before building something properly from scratch. So far I haven't used any of the code spit out from my quick Webflow prototyping, but it helps me consider the structure of my site because its controls essentially are GUI inputs for CSS and HTML elements.

    The value of a tool like this is working faster to produce something tangible for clients who need to see a site to understand what they want or what you're proposing. The web is still a very abstract thing to many, and tying together static comps doesn't always convey interactivity properly.

    6 points
  • Sebastien AzimiSebastien Azimi, over 5 years ago

    Disclaimer: I am a web developer, not a designer.

    Hello!

    I am not an intensive user of Webflow. In fact, I have learned about this web app a few weeks ago.

    Yet I already have recommended it to a designer friend who is using Illustrator/Photoshop to design his templates. Why? Source code clearly scares him. I don't blame him. And even if he became HTML/CSS3 fluent, he surely would spend much time to achieve his templates using code only. So why would he change his way? Webflow looks like a Photoshop fork, which clearly may reassure him, and may give him a better feel of what can be done or not in pure HTML and CSS3 combination. His way to communicate with developers/integrators would definitively be improved. Plus, using this tool, he would be able to sell ready-to-use templates, so increase his pricing.

    As a frontend developer and integrator, I know how to turn Illustrator/Photoshop templates to HTML pages and stylesheets. But I am not a designer while I really am interested in web design. I have made templates "just" coding them. Some of them were bad, some were just not too ugly. Maybe I am not creative enough (which is clearly possible), but I feel that only using code to achieve templates slows down creativity process. Webflow may be a game changer, as it enables building layouts in a breeze.

    You are right: I would not be able to do whatever I want with this tool. But does it really matter? In my opinion it's just a tool among the many ones I daily use that may speed up templating workflow (which is what I want from it, referring the Steven Hawking's quote).

    5 points
    • Liam MaddisonLiam Maddison, over 5 years ago

      Hi Sebastien,

      You make good points, and I do agree with most. It does speed up processes, building templates is obviously something that takes time and why not use a tool to help you enhance efficiency. I'm all for that.

      However, I don't agree that it slows down the creativity process. As the process should be to design your website in Photoshop, then build it with code, so essentially all your creativity is in Photoshop and your coding skills in developing.

      Thanks for the reply! :)

      1 point
      • Tom WoodTom Wood, over 5 years ago

        What is advantageous is the ability to create something slick in a short amount of time.

        I'm a designer with some front-end dev experience, but for me to create an animation or even a series of divs to look exactly as I intended on my first attempt is near impossible. It always takes trial and error - part of what makes the outcome so satisfactory to some, but also part of what puts so many people off.

        1 point
      • Sebastien AzimiSebastien Azimi, over 5 years ago

        I know how to use Photoshop but, maybe because I am a developer and not a designer, I do not want to use it when I am building a template. These two steps (design in Photoshop then integrate it in HTML/CSS3) make me feel like I am wasting my time and should do it directly using code, as if I would do the same thing twice. I certainly am wrong but this is how I feel about this process. Webflow is something in-between: the template I make using Webflow is directly usable, even if it must be tweaked after export.

        Ten years from now I used Dreamweaver, when building a layout with tables was not a problem at all, and I do understand what you meant about sense of code behind the templates. Dreamweaver definitively taught me a lot about HTML and CSS. The Dreamweaver version I used is not that different from Webflow, except Webflow enables building modern designs without coding a single line, just placing HTML elements then setting properties to them, as you would with Photoshop, then easily exporting your project in code.

        1 point
        • Liam MaddisonLiam Maddison, over 5 years ago

          I see where you're coming from. These programs are super quick at designing sites, I agree with that, saves a whole lot of time.

          However, one thing I forgot to mention also is that these programs are built to build "modern" websites as you say, they are programmed to follow what is in style today in the web industry.

          So if everything went towards a new style of design, say like 3D. These tools would have to have major re-developing to adapt to this, at which point you would just build a new tool.

          Tools that stay around for years and years are tools to think about, I don't think these ones will stay around for long. Dreamweaver has, and will for more time. These tools don't control what we create, it helps us create what we want to create.

          0 points
          • Sebastien AzimiSebastien Azimi, over 5 years ago

            I totally agree: this tool is just a time saver to build templates according to modern website standards, not to revolutionize web design. Yet is it a reason to hate Webflow? ;-)

            1 point
  • Guillaume GosselinGuillaume Gosselin, over 5 years ago

    It's like saying that you will code a new Design Software each time you need a design, because you don't like how Illustrator or Photoshop simplified the design process with their own "Artificial" Tools.

    It's like saying there is no a good CMS and that you prefer to code your own CMS everytime.

    Come on, designers need a tool that simplified web and responsive design, and Webflow is the perfect tool for that.

    4 points
    • Liam MaddisonLiam Maddison, over 5 years ago

      I disagree. There are frameworks to speed up the process, with responsive, which are super flexible.

      I think that designers need a tool to aid them in coding, not telling them how its going to be structured etc..

      I agree that there should be a tool to simplify the design/developing process. If you could combine front-end frameworks, with auto-completing and super flexibility, then you're onto something special. I just don't like being told how my code is going to be structured and so on.

      0 points
      • chirpy zzz, over 3 years ago

        Designers shouldn't be coding, they should be concentrating on the design. Just as coders should not be designing. While it is helpful for each to know something of the other, you cannot be an expert at both. Although, I know many more designers that know how to code rather than coders that know how to design pretty things.

        1 point
  • Craig FrostCraig Frost, over 5 years ago

    It's a shame that the conversation generated by this post is moot. If you don't like a tool, don't use it. Inflammatory opinions aren't useful. Perhaps mine isn't either.

    3 points
  • Nelson Abalos JrNelson Abalos Jr, over 5 years ago

    I agree that Webflow isn't for everyone. But, for most people who work in a position where most clients need to see actual working prototypes, WF gets the job done and fast.

    I understand that you love to code and you feel that WF takes some of that control away from you. But, just like you said, you can still export the code and do what you want with it.

    Just like everything else in this world, humans will always find ways to push themselves out of a job. For instance, remember when it took many people to maintain train tracks?

    Well now we have just a few doing it while machines do the rest.

    https://www.youtube.com/watch?v=8iN_iYhtc2Y

    It's just the way the world works.

    To me, WF is the present and future of web design.

    Lastly, "hate" is such a strong word. No one is forcing you to use it.

    3 points
  • O LO L, over 5 years ago (edited over 5 years ago )

    Reading this post, I sense it was created for self-promotion (yes, we get it, you love to code) rather than addressing any real issues.

    Just so we clear, you hate Webflow because you have to copy/paste generated code and paste to an editor of your choice for further development.

    No offence, but this makes me question your problem solving skills on the basic level and your ability to foresee how such unjustified title can be damaging for a small startup that works hard on delivering great product. And what do you propose to make Webflow better?

    Lastly, your quote about AI is not applicable to Webflow, but [sarcasm] you may recycle it when writing hatin' posts about other tools, such as The Grid [/sarcasm]

    2 points
  • Mike MaiMike Mai, over 5 years ago

    I am with you, man. I tried these programs one after another, there are a dozen of them now, seems like one pops up everyday.

    I, like you, just prefer to design with code. By not touching code, one is just avoiding the problem. Knowing how HTML and CSS work is not enough, knowing how to write it will actually help you become a better designer. And the only way to know how to write it is to do it daily.

    Even if you create a design with really crappy code, that is a major step towards taking yourself to the next level. HTML and CSS is a tool, no different than Photoshop or Sketch.

    Designing in the browser forces one to solve problems, whether it's technical or visual. And solving problems is what design is all about.

    I do think tools like Webflow have a place in the designer's work flow, such as prototyping. The tools allow you to quickly rip up a ton of interactive prototypes for testing or brainstorming before final design, but should never be used for production.

    2 points
    • Liam MaddisonLiam Maddison, over 5 years ago

      Totally 10000% agree. These programs are never going to give you the quality that you would get from coding.

      Coding helps you understand how elements work together and that essentially goes through to your designs.

      I get many mockups from clients in the company I work for, asking for things of which aren't possible, not even with our CMS, that wouldn't generally work, and these are real life Designers at work here.

      0 points
  • Andrew CiobanasiuAndrew Ciobanasiu, over 5 years ago (edited over 5 years ago )

    The way I see it: Webflow allows for extremely rapid prototyping and playing. A lot of the designs are beautiful and come with a bunch of fancy animations tossed in that seem to work very well.

    Quick idea for how something slides in/out of view on-scroll?

    Bam. Done.

    It's really great for designers who are afraid to get down with some syntax and who aren't familiar with updated standards/solutions. But let's be honest, it's basically the better version of Wix. It doesn't require any deeper understanding of how and why something works. This will always be the indication to true professionalism in my opinion. Shit smells really bad when it hits the fan and you're sitting there not knowing why something isn't doing the thing it's supposed to do.

    When you're intimate with your code (I know, bleh) you get a better sense of where the looser links are. From there you can start fixing when things go awry. It would really suck to answer a pissed off client with, "Sorry sir, the website we used to build your site on isn't working ... " and that's it.

    I see Webflow as another tool at my disposal, not a complete substitution for "hand coded" development. In the same way that you don't list "Dreamweaver" on your resume (I hope) you don't list Webflow.

    If you do ... well ... Godspeed.

    You're making it easier for the rest of us to stand out.

    2 points
    • Liam Maddison, over 5 years ago

      I know, the only point I was making is that there is a massive hype about it when actually it isn't the best solution for building real websites.

      PS. on my resume I have Dreamweaver = 5 Star Skillz. Is that bad?

      0 points
      • Andrew CiobanasiuAndrew Ciobanasiu, over 5 years ago (edited over 5 years ago )

        I totally agree with that.

        But I can't tell if you're being sarcastic or not about Dreamweaver. It's leaps and bounds better to list your proficiency in languages than to put your percentage in DW or whatever else.

        Listing HTML/CSS/JS/C++/etc. shows your employer that you know your stuff. They don't care whether you use the latest alpha of web.derv.io or notepad to write your code, so long as it works.

        1 point
      • Drew AlbinsonDrew Albinson, over 5 years ago

        I think you could say the same thing about TypeCast which someone mentioned earlier. Personally I really like TypeCast for quick testing but I'm not going to rely on it entirely. I think the functional piece of these tools is skipping photoshop all together, which many are now considering a best practice especially as website are becoming more dynamic (responsiveness, animations, and other patterns aren't clear in a static mockup).

        2 points
  • Thomas WrightThomas Wright, over 5 years ago

    I heard about this post and so signed up here to respond. Cannot believe anyone would "hate" webflow but each to their own. First, by way of disclaimer, I do NOT work for webflow. My interest is as a user/customer of webflow.

    Some of the thoughts or purported beliefs in this thread bother me to no end. First is this thing about "writing raw code and seeing it come to life." I can appreciate that.

    But in the real world of running a business that might need to crank out 5 or 10 or 25 websites a week, writing raw code and seeing it come to life is tantamount to bankruptcy in my opinion or else having to charge so much you exclude a majority of your potential customers.

    Because, let's face it, building a complex and comprehensive website for a customer by hand takes a lot of time. Even with the automation of something like webflow it can takes weeks or longer to build a clients website and time is money either charged or paid.

    You absolutely must have more of a sense of automation to survive in the real world business dealing with individuals and small business budgets, at least as we've learned it. This is just our opinion from running our own business and we have been in business since 1998 and serve hundreds of customers across the globe.

    Oh, and individuals and small businesses generally don't know the difference between raw code, clean code or underwear. They only know what they like and/or what they want and if you deliver same.

    The internet machine might know the difference between raw code or clean code and it might care (somewhat). But it shows a page all the same regardless of what kind of hand (or machine) wrote it. Point being, when it comes down to it (speaking from the mind of a business owner that designs sites everyday for individuals and small businesses and has employees to feed, and client budgets to keep) what really only matters is does the site do what it is supposed to do and look like it is supposed to look? Not whether it is written by hand or machine.

    But in terms of running a business you have to balance the clients needs and desires with the ability to produce good or better quality websites quickly, efficiently and cost effectively. and that is where Webflow excels, at least for us.

    It is for that which much of the negative-speak about Webflow I think trivializes Webflow because it is a great program. We've used it to quickly and easily create beautiful responsive websites without having to write one piece of code by hand. This saves a ton of time, a ton of money, keeps our design costs low for our client and satisfies all the stakeholders. Our average client doesn't care about the means only the end result and Webflow enables us to quickly and easily accomplish the end result.

    Personally, I have been designing websites literally since the birth of the Internet as well am CIW Certified Web Designer. But you cannot run a full-fledged business on that alone and expect to grow and survive. I suppose if you are a single operator making your money one or two or three clients at a time, perhaps for sure. But when you have hundreds of clients and all of the things that go with running a business - automation is fantastic and Webflow is fantastic in that it helps us that way.

    And for the poster to say "There is a constant battle to have the latest technologies implemented and I just see it eventually falling behind," well, I know that is his opinion but it just comes across so rude to me to predict Webflow to fall behind, obviously he knows very little about the true Webflow and has not spent time with it like I have.

    Personally, I'd like to see some of these sites the original poster so awesomely creates from hand getting dirty with the code, and see how they compare to an awesome Webflow site. What's the difference I ask myself..? Maybe then I'd be able to have a better opinion about his hating Webflow.

    1 point
  • Greg BowenGreg Bowen, over 5 years ago (edited over 5 years ago )

    What follows are my impressions. Please correct any flaws in my reasoning. :)

    If you are not a designer and you want to build your own website, then themes and a CMS are the way to go. There are thousands of great inexpensive looks that are ready to go.

    If you are a developer and are working for a client with a solid budget, I don't believe you will ever be able to beat the speed, flexibility and extensibility of custom code.

    What is left? If you are a designer that doesn't know how to code, or just doesn't want to mess with it, for personal projects, or smaller clients - Webflow sounds a potential candidate.

    For prototyping, it sounds like a goods choice, however aren't there tools out there designed specifically for this purpose?

    1 point
  • Alexander ZizzoAlexander Zizzo, over 5 years ago

    i dont like using them either, but i still find myself rooting for them. if they truly get to a place where it's better, faster in all ways than me raw coding it - great. i'll start using it and pick up another skillset to keep myself desirable as a developer

    1 point
  • Tor Løvskogen BollingmoTor Løvskogen Bollingmo, over 5 years ago

    I love writing raw code – I like to get dirty with my code.

    That's the crux. And you love writing code because solutions doing it for you in the past have produced crappy results. This has conditioned you.

    I for one hope we can get rid of manually writing code, starting with basic HTML and CSS. I don't want to waste my time doing that. It should be a thing of the past.

    1 point
  • Charlie McCullochCharlie McCulloch, over 5 years ago

    I don't think it's obvious who this program is for. I thought it looked ideal, then spent half an hour playing around with it before coming to the conclusion that it's not worth the time and effort to get it to do what you want, because the mental model (for me at least) does not match up with HTML + CSS workflow.

    1 point
  • chirpy zzz, over 3 years ago

    Just saw this post while searching for something Webflow related. I am a designer that knows how to code. I much prefer to "design" in the browser using Webflow than to hand code something every time. In Webflow you can see changes happening as you make them, as well as selecting colors, fonts, styles etc. Not only that, but it allow me to create interactions with elements without having to learn Javascript. It's great for both wirefrraming and site design, protyping websites and mobile apps. Webflow has also come a long way in the 2 years since your post. Additionally, you can drop in your own code if you want to using custom code blocks. I'm not really sure why you would want to edit the generated code, when the generated code is fine? Seems really odd and as others have said you are not the target audience for this. However, your web designer is the target audience. Your designer builds his site in Webflow, exports the code, gives it to you to tweak and voila - live website when you're done. That's the strength of Webflow - anyone can use it and YOU don't have to worry about a web designer screwing up your code because he doesn't know what he's doing.

    0 points
  • Robert Redford, over 3 years ago

    This post title is internet cancer. I bump into it so often, I made an account to specifically call out Liam Maddison on his foolish use of this information outlet, not only being greatly misleading, but also damaging to a team of people who've invested countless hours in providing an excellent service. I am not related to webflow in any way. I am here to say it is a real shame this post has garnered enough attention to continuously show up on google's front page, dissuading casual readers to look further into webflow, as not everyone will go through this post to realize OP didn't even really mean what the title said.

    0 points
  • Martin Adams, over 3 years ago

    It’s an unfortunate header, Liam, especially if you think that “Webflow is one of the best solutions out there.” I strongly urge you to reconsider changing the header of this blog. I find it misleading.

    0 points
  • Charles Hiker, almost 4 years ago

    Sounds like a personal issue.

    0 points
  • MZ Dev, almost 4 years ago

    I can't even begin to express just how ridiculous the OP is. If you so love writing code yourself, why are you even attempting to use a program like webflow? You are clearly not webflow's target audience. But at the same time, it's soooooo stupid to say that you hate a product because it does something that you don't want to do in the first place. It's like saying you hate chocolate because it tastes like... wait for it... chocolate! We get it, you like stroke stuff yourself and get all excited and orgasmic when something comes out. Why again are you using Webflow? And why again are you creating potentially negative-looking content around a product and company who are both EXCEPTIONAL at what they do? To put it lightly - dude - get over yourself. Maybe if you put even half the effort into your own projects as the webflow team has into their's -- well then you wouldn't have time to leave stupid articles on DN, that's for sure, and second, you'd appreciate the work of others a little bit more.. and avoid writing posts with over the top titles while you're at it.

    0 points
  • Artur MaklyarevskyArtur Maklyarevsky, 5 years ago (edited 5 years ago )

    ☞ Would be ideal if Sketch could export to Webflow ;-)

    0 points
  • Joe BlauJoe Blau, over 5 years ago

    Try Blocs. As a developer, I tried using Webflow as well and something about it didn't stick. I like Blocs paradigm of building sites a lot better.

    0 points
  • Ryan Coughlin, over 5 years ago

    Same as TypeCast. Ill save the paragraph of reasons, but it was pointless.

    0 points