All I am asking for is to for a minor change how pages are cloned which will not hurt anybody
and which is absolutely easy to implement for the Webflow team.
People who want to keep a single CSS file could still do so, but this is not a religious
And as you will know better than many other people, the HTML standard leaves the option to
connect multiple CSS files with a single webpage.
This is how HTML works and not my personal opinion!
Especially if Webflow takes pride in their clean code and keeping HTML/CSS standards up
high, they should finally accept the very rudimental HTML standard of adding
multiple CSS files into a single webpage.
I don’t understand your problem with that and why you try to convince me how working the
other way around is better.
Usually I do mockups in Photoshop first, but who does 50 pages mockups?
Maybe you do, but for what do I need Webflow then (as a person who knows how to code)?
If you do the hard work before you even open up Webflow, then for example as a Creative
Cloud Member you can fire up Dreamweaver, skip Webflow and achieve the same
You and me like Webflow because of it’s flexibility of making changes and design websites
without fiddling hours manually in CSS files.
That safes designers a ton of time and that is maybe the biggest reason why Designers who do know
how to code should try Webflow.
Otherwise they can stick with Coda, DW or whatever.
Design only people have other tools too which don’t generate clean code, but then they don’t
need to care anyway because they simply don’t have a clue about it.