TEST 1
Create New Project.
1 Page containing a section and nothing else.
No classes. No styles. No nothing. Just a section (div).
Result:
CSS:
project style sheet - 0 bytes
normalize - 8kb
webflow.css - 38kb… QUESTION: WHY IS THERE A WEBFLOW.CSS FILE (thinking about white-labeling)
JS:
modernizr: 5kb
webflow.js - 56kb… QUESTION: WHY IS THERE A WEBFLOW.JS FILE (thinking about white-labeling)
TEST 2
Open an existing project
Tons of classes.
Project uses jquery to dynamically load a photo library
Result
CSS:
project style sheet - 30kb
normalize - 8kb
webflow.css - my project doesn’t have a webflow.css - why not… test 1 did ???
component.css - 38kb
JS:
modernizr: 5kb
(project).js - 131kb… why does a new project have a webflow.js file but an exiting project have a js file nmed after the project.
So… it appears the project js file is smaller. In my case about 50% smaller when comparing a new project with nothing in it (56kb file) to a complete - fairly large project (131kb).
Issue 1:
Also… with this update… it seems webflow no longer uses the project name for the js file… instead opting to name the file webflow.js… Which is a step backwards when it concerns any level of white-labeling.
Issue 2:
And… with this update… it seems webflow no longer uses the project name for the css file… instead opting to name the file components.css… Which is a step backwards when it concerns any level of white-labeling.