Skip to content

Latest commit

 

History

History
103 lines (56 loc) · 4.26 KB

README.md

File metadata and controls

103 lines (56 loc) · 4.26 KB
Raw

Ajaxify

Ajaxify your entire website instantly with this simple drop-in script using the HTML5 History API with History.js and jQuery ScrollTo.

Installation

Direct

<!-- jQuery -->
<script src="//ajax.googleapis.com/ajax/libs/jquery/1.9.1/jquery.min.js"></script>

<!-- jQuery ScrollTo Plugin -->
<script src="//balupton.github.io/jquery-scrollto/lib/jquery-scrollto.js"></script>

<!-- History.js -->
<script src="//browserstate.github.io/history.js/scripts/bundled/html4+html5/jquery.history.js"></script>

<!-- Ajaxify -->
<script src="//rawgithub.com/browserstate/ajaxify/master/ajaxify-html5.js"></script>

Bookmarklet

javascript:var%20e=document.createElement('script');e.setAttribute('src','//rawgithub.com/browserstate/ajaxify/master/ajaxify-bookmarklet-helper.js');document.body.appendChild(e);void(0);

Extension

Install the Ajaxify History.js It! Google Chrome Extension

Explanation

What do the installation instructions do?

  1. Load in jQuery
  2. Load in the jQuery ScrollTo Plugin allowing our ajaxify gist to scroll nicely and smoothly to the new loaded in content
  3. Load in History.js with support for jQuery, HTML4 and HTML5
  4. Load in this gist :-)

What does this gist do?

  1. Check if History.js is enabled for our current browser, if it isn't then skip this gist.

  2. Create a way to detect our page's root url, so we can compare our links against it.

  3. Create a way to convert the ajax repsonse into a format jQuery will understand - as jQuery is only made to handle elements which go inside the body element, not elements made for the head element.

  4. Define our content and menu selectors, these are using when we load in new pages. We use our content selector to find our new content within the response, and replace the existing content on our current page. We use our menu selector to update the active navigation link in our menu when the page changes.

  5. Discover our internal links on our website, and upgrade them so when they are clicked it instead of changing the page to the new page, it will change our page's state to the new page. Links with the class no-ajaxy will not be upgraded.

  6. When a page state change occurs, we will:

    1. Determine the absolute and relative urls from the new url

    2. Use our content selector to find our current page's content and fade it out

    3. Send off an ajax request to the absolute url

    4. Convert the response into one we can undertand

    5. Extract the response's title and set document.title and the title element to it

    6. Use our menu selector to find our page's menu, then scan for new page's url in the menu, and make that the active menu item and mark other menu items inactive

    7. Finish the current content's fadeout animation

    8. Use our menu selector to find the new page's content, and replace the current content with the new page's content

    9. Fade the new content in

    10. Scroll to the new current content so the user is directed to the right place - rather than them ending up looking at the footer or something instead of your page's content due to the height shift with the content change

    11. Inform Google Analytics and other tracking software about the page change

Using this Gist?

Post your website in the showcase here!

Further Reading

History

  • v1.0.1 - 30 September, 2012
    • Added completion event (customisable via completedEventName defaults to statechangecomplete)
    • Updated for new Google Analytics code - credits to aspiziri

License

Licensed under the New BSD License