By hand, not generated. But feel free to steal.

Thanks, will take a look.

And didn't want to imply the rest of it is any less awesome. Really dig it.

I personally see myself using it purely on the web, as a way of getting across an idea or perhaps even a tutorial of some kind.

Big thumbs up.

The scrolling of the docs is definitely interesting, with URL fragments changing continuously along with small page effects, but I think the bugs may outweigh the features...

For instance, clicking anywhere on the scroll wheel causes the fragments to cycle through. The URL bar goes a bit crazy. Quick scrolling also lags because of this. The back button causes the same effect. Perhaps there is a way to fix all this. But even so I find it creates a jarring user experience.

I couldn't reproduce these either in the latest Safari.

neither could I, but it's there in chrome

I can't reproduce any of these bugs using Firefox.

The elements and everything used during the scroll checks is in fact cached (which you'll be able to verify by looking at those internals you mention) and throttled per my comment below. As another commenter pointed out, the project page itself is full of drop shadows, text shadows, and css3 gradients, and opacity. Those are probably slowing you down way more than the plugin. Do you see the same performance problem from the relatively unstyled examples?

Plugin author here, I can help clarify that. The scrolling is throttled so that all the checks aren't run with every single scroll event, as that would choke everything. So the small delay you see there is some 0-100 millisecond value while it hasn't triggered the event yet.

You can change the throttle by setting $.waypoints.settings.scrollThrottle = 50, or whatever number you like, to try to reduce flickers in cases like these. Just be aware its a balance you'll be striking with executing more scroll checks. But all the selectors and offset values are cached so the performance should still hold up should you choose to lower this value.

Reminds me of this, I guess you read it already:

http://ejohn.org/blog/learning-from-twitter/

Based the throttling on that exact post.

I love what you did with this and i will definitely play around with it. This functionality should really be built into the browser in my opinion. I was thinking, for performance reasons, did you try ditching the $(window).scroll and go with this? http://jsbin.com/eciwu4/edit