Component based
@webflow Development ๐
A good 3/4 of a year ago, I said that components would be THE thing in
#Webflow today. And I wasn't wrong.
Developing an appealing and accessible website for users is no longer the only thing that counts when developing a Webflow project. Today, even more than before, what counts is making the maintenance and editing of the website as accessible and sustainable as possible for the editors of the project.
Webflow has given us the tools, so we should make something of them. Even if Webflow's
#components โ especially those with
#CMS content โ still need a lot of love from Webflow, what is already possible is absolutely satisfactory (not the game ๐).
What should not be underestimated, however, is the time required for a completely component-based development.
The components alone, which you can see here in the screenshot of my current project, have cost me around 1.25 - 1.5 times as much time in development as if I were to develop them statically and therefore not sustainably. This is because it is often not just the definition of component properties, but also the optimization of custom CSS and the JavaScript required for the functions when Webflow's slots are in slots and the semantics are therefore no longer correct.
What you can't see in the screenshot is that there are other components in each section, which may also have slots with components.
Happy flowin - Dennis โ
ALT Webflow Designer UI - Open navigator panel with many visible Webflow components