Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
First off, thanks for providing the source to this. It's really a great example of a well laid out project using the Skrollr.Js library and inspired me to lay my project out in a very similar way. Certainly helping save some time refactoring!
While putting together our project in a very similar style, I came across a very small performance tweak that has quite a large effect on frame-rate when using transforms to manipulate full-screen elements. Especially on lower powered devices.
This was really inspired by a blog post I came across when researching CSS performance: http://blog.teamtreehouse.com/increase-your-sites-performance-with-hardware-accelerated-css
I used it in my project with great results and applied it to your source just as a proof of concept. And perhaps a bit of thanks in there as well :). Really only the Materials section requires any of it as that's where most of the repaints seem to occur. There are still a few left, but this drastically increases how smoothly it scrolls.
Before Tweaks:
After Tweaks:
Anyway, pop it in there if you want, or not. But hope it's useful for someone!