After months of refining the structure, Small Medium Large V2 is live!
A Controlled Webflow Component Framework built for clarity, not chaos.
Faster builds. Cleaner structure. Easier handover.
www.small-medium-large.com
After months of refining the structure, Small Medium Large V2 is live!
A Controlled Webflow Component Framework built for clarity, not chaos.
Faster builds. Cleaner structure. Easier handover.
www.small-medium-large.com
What the Small Medium Large Webflow component framework update is about:
I finished the last component for my Small-Medium-Large Webflow framework update.
Now all that there is left to do is to update the site record an explainer video and go live with the cloneable.
The first webflow build with the updated SML component framework went live.
A one paged build by ZUID for Aqwire: aquire.nl
This morning I managed to wrap up creating an API connection between Webflow and TeamTailor with Cloudflare worker.
Sure I could have spend my weekend on other stuff... but when a developer says that things are not possible and very complex, then I have to proof him wrong.
Anoyment can sometimes be the best motivation.
A job a developer did got done badly. So this weekend I am seeing if I can wrap my mind around Cloudflare workers and some API Webflow hoopla.
Saturday is done, and the CMS is being populated, multiref fields and all. Tomorrow I’ll handle updates.
And the native Webflow slider component has also been added. Off course again using the new switch property for toggling autoplay
And of course if autoplay is off the code gets hidden server-side.
Next up Slider and Nav... and then I can release it.
Tab section has been added to the SML components build. Optional autoplay function as a simple switch on or off.
Thanks that is nice to hear. Yeah spacer divs are always an item up for discussion. I find them a bit more present in the navigator then paddings or margins. But as things have been going I am sure I switch my mind about it at some point hahaha
One of those things is that I in the past did not create tabs, sliders or menus in the framework. But now that I go all in on components I will build bare-bones versions of them.
The framework will also be more catered to my current job at zuid.com where I will be training junior Webflow devs.
There are so many ways to go. And in the end I pick a direction because that is how I like to work. It totally makes sense to pick a framework and rip it apart to turn it in your own.
Sml is not yet updated with the new component system. But it will launch in February.
I don’t know what you mean with “opinionated”… With SML I try to stay as non-designed as possible, but it is a hard line to follow.
Work is being done
The code behind the new SML webflow component system.
I expect to have a bit more free time in the next weeks for the new webflow sml component framework. I was lucky to test it on two projects. The bigger the project, the more powerful it is.
Aiming for releasing it in February. To do are tabs, sliders and navigation. The three horrors in my life ,)
This past half year being back at work for a dutch agency I have build and put live 6 webflow websites.
easyflex.nl
euramaxcladding.com
brandgang.com
zuidagency.group
adfiadon.nl
nationaleseksenquete.nl
This year I will easily go past the one build per month ratio.
I've added a #builtwithSML section to the Small Medium Large site small-medium-large.com
Thanks for offering to help. It was for a demo that was held yesterday so I am good for now. I skipped the fancy animation stuff and we seemed to did okay.
I was trying the other day to add a gsap stagger to CMS elements in a Webflow dropdown… this stuff aint half easy.
Mental math on paper, that makes no sense. That is like remembering something by writing it down.
I need to activate this blue sky stuff here.
My Webflow framework small-medium-large.com has been updated, all text sizes can now be controlled directly from the variables panel. Additionally, responsive sizing for spacing, gaps, and gutters is now fully adjustable within the same panel.
Goal for 2025, slow further down and remain calm
I am going to need to transition a few clients sites back to my own workspace for that reason. Kinda hard to bother the client with this.
So why do I spend time on Small Medium Large and keeping it up to date?
Firstly, because I use it on a daily basis.
Secondly to give insight into how I think components can be used.
Thirdly to inspire, to push forward.
SML is nothing more than sharing the system I use.
I should work on that yes. There are several sites out in the wild that are built with it, but I do not have a gallery. Here is a list of a few that come to mind that withstood the test of time.
webnique.de
ditis.de
brandgang.com
zuidagency.group
energiebaas.nieuwestroom.nl
vp-strategy-advisors.de
The Webflow component blocks inside small-medium-large.com now include tabs, sliders, image lightboxes, and video lightboxes, all of which hold component slots for endless layout options.
small-medium-large-s-1440.webflow.io/stylesheet/c...
Sneak peek into the project that I am currently working on. It is not done yet, but I need to share.
This one-pager is 100% built in Webflow Build Mode. Some component blocks are used 100+ times.
brandbook-zuid.webflow.io
More and more Webflow sites that I build revolve around creating components and giving power to Clients working in Build Mode. This update should save me a bundle of time.