Grzegorz Róg — CEO at easy_
Tools and automations that allow me to work 10x more efficiently
September 5, 2023
11:00
No-Code
🇵🇱 Polish
No-Code
Everyone can become a Webflow expert (the truth about mindset, skillset, and how to become Webflow master)
About
Webflow is a hot topic nowadays, although its marketing is pretty misleading (same as other no-code tools). It's not about web design, or rather, not design-only. It's about development. As long as we can use Webflow for design, true, switching the mindset to development will make us create timeless, effortless and efficient websites. Not only sites that look good and attract the eye.
Let’s talk about best practices and most common mistakes in Low-code development. Let’s decompose no/low-code development mindset, including consulting approach and value–focus (not deliverables).
What you’ll learn is, being able to treat websites as products and tools helping companies reach business goals. Understand how designers and Webflow dev’s see layout, what you have to remember about. How to approach accessibility. Interactions (not only animations). How important it is to spend more time thinking than acting -> for example, how to build comprehensive CMS structures, by starting from information architecture, and more.
See you in September! And let’s talk about how to lead low–code world-wide-web.
Watch the full talk
Watch this WaysConf session, then continue with related talks or explore the current programme.
From the recording
Talk in brief
A roadmap for becoming a Webflow professional by treating the tool as a development environment rather than a visual canvas. The talk begins with mindset: design the experience elsewhere, then translate it into semantic, responsive, performant, maintainable web pages. It contrasts an implementer who depends on platform defaults with a developer who understands HTML, CSS, JavaScript, integrations, and documentation well enough to work beyond those defaults. The required skill set includes accessible structure, CMS modeling, SEO, responsive units, components, optimization, and appropriate custom code. Frameworks and mentors can accelerate learning, but expertise comes from understanding the web principles beneath the interface.
Key takeaways
- 01
Enter Webflow with a developer mindset
The interface may look visual, but production work still requires browser, content, performance, accessibility, and maintenance decisions.
Watch from 3:41 - 02
Translate completed designs instead of designing in place
Creative exploration belongs in a design tool, while Webflow should implement a considered structure and interaction model.
Watch from 6:30 - 03
Move beyond platform-only implementation
Understanding web logic and documentation lets practitioners solve requirements that exceed built-in controls or familiar recipes.
Watch from 14:43 - 04
Build expertise across three skill groups
Front-end fundamentals, integrations, and content management together make a website usable for both customers and the business operating it.
Watch from 16:23 - 05
Use frameworks as accelerators, not foundations
Studying several systems reveals useful conventions, but practitioners still need enough CSS and structural knowledge to judge what fits each project.
Watch from 24:13
Read edited transcript highlights
These concise notes were edited from automatic captions and checked against the talk structure. They are not a verbatim transcript.
A visual interface does not remove engineering responsibility
Opening Webflow means entering the environment where a website must work across browsers, devices, content states, and network conditions. The practitioner has to consider page speed, semantic structure, accessibility, search visibility, and future editing. Dragging elements onto a canvas is only the visible action; the professional task is deciding how those elements should behave as a real web document.
Watch from 3:41Design freedom and implementation discipline serve different phases
A design tool supports exploration of journeys, layout, and visual direction without requiring every production constraint to be resolved immediately. Once the work moves into Webflow, the goal changes. The developer translates a prepared concept into valid elements, predictable classes, responsive relationships, and maintainable behavior rather than continuing to improvise the design inside the build.
Watch from 6:30Platform familiarity alone creates a capability ceiling
An implementer can reproduce patterns supported directly by the tool, but becomes stuck when a client requests unfamiliar behavior or an integration. A developer reads documentation, understands which layer controls structure, style, or interaction, and can evaluate an external service or a small amount of custom code. That broader model makes platform limitations navigable rather than terminal.
Watch from 14:43A business website continues living after launch
Front-end quality is only one part of professional delivery. Forms may need to reach a CRM, analytics must capture meaningful activity, and the content model must let the client update people, articles, products, or testimonials safely. Treating integrations and CMS architecture as core skills prevents a visually finished site from becoming operationally fragile the moment ownership changes.
Watch from 16:23Borrow conventions only after understanding their purpose
Webflow frameworks package solutions to naming, spacing, responsiveness, and reusable structure. Reviewing several can reveal why common challenges have been solved in particular ways. No framework can replace judgment, however. The developer needs enough CSS and web knowledge to select useful conventions, discard mismatched ones, and keep the project understandable to the next person.
Watch from 24:13
Explore WaysConf 2026
