I like the idea of a one page site with smooth scrolling up and down. So I made one and it works pretty well. But the problem with such a page is the amount of code that gets generated. The result? Long loading times and disastrous google appreciation. I’m not too worried about Google though, as for this site it is not important with high rankings, as it will mostly be know-the-address-driven.
Still, it would be nice if somebody could have a look and see if anything can be done, and/or give me some advice. I’ve tried the Externalize Action, but to be honest with the different alternatives I sometimes felt as if I didn’t know what I was doing. At the moment no such action is in place and only externalize stylesheets is ticked off in document setup.
For one thing you’re loading a lot of stylesheets and a couple js files both of which could be compiled and compressed into a single CSS and js file respectively. That alone could potentially help quite a bit.
While very easy to do with a tool like CodeKit and an editor the problem you have is FW which has a very specific and rigid way of doing things that makes what I suggest far more difficult than it would otherwise be.
So yes, there are things you can do to make the code more efficient and faster-loading but it will require a more hands-on approach.
Out of curiousity, did anything materialise from this sentence you wrote in a thread back in 2015?
“Honestly I don’t know why I’m so curious about integrating CodeKit and FW in the first place, but if (big “if”) it were possible I might even be persuaded to write a tutorial.”
Jon
freewaytalk mailing list
email@hidden
Update your subscriptions at:
At the time there was no expressed interest on FWT for a CodeKit tutorial, and since I don’t use FW there was no incentive to invest the time.
However, two years later I believe Max recently mentioned something about possibly putting together a FW + CodeKit tutorial. Check the WebYep threads from this year.