Guides: Implement hashed routing

[ericbtaylorjr]

Guides flow should be: "Guides" > "Spec" > "Spec Guide"

Default section should be "Overview" and user should be able to navigation through the Spec Guide via the section navigation, which will be hashed content loaded via AJAX.

Example: guides/rogue/outlaw#rotation

[raynjamin]

@dellinger Hey man, I spoke with @Accomp some more and he would prefer the ajax loading of bits of content considering there would be so much to load at once if we used traditional hash navigation.

The biggest potential problem is loading images. If you link to/navigate to the bottom of the page, it's possible for a very terrible user experience while all of the content and images to load. We're talking either the user has to wait until all the images load and THEN navigate to the bottom of the page, OR the user navigates immediately and has to deal with content flashing/moving around until all the assets load.

After some discussion (and I think we're going to need this regardless) I think a better option would be to load all the content on the page, but to use an image defer library to set placeholder images in the page, replacing them as images load with their actual assets. This would prevent the page from moving around on the user and would be a more pragmatic approach to the hash navigation on the page.

I've not done a ton of research but I've seen a couple candidate libraries so far. Maybe research this and see what you come up with?

[dellinger]

Gotcha, I can get on board with that. I'll check to see a few of them out there. I may need to see what you mean as far as the ajax loading is concerned -- where does it fire? When user clicks a link it gets fired?

[raynjamin]

No forget the Ajax loading of the content. Current plan is to load the entire page and asynchronously load images so the page doesn't flicker around like a motherfucker.

[dellinger]

Roger roger.