Jump to content

Client-side routing (page.js)


Recommended Posts

Hi, everyone!

I'm going to start a new nice site, but the client wanted absolutely a site like one he found surfing the web.
It has a smart navigation system, like an app, so you won't find "jumps" between the pages.

It's super cool and i found it uses page.js as client-side routing, loading the main content with ajax calls.

So, this is my question. Do you think i will find some problem using this script, or maybe i'll find some conflicts with processwire internal routing?
Maybe here there is someone who already used this type of client-side routing with PW?

I'd lile to use PW, with many different page templates...

Link to comment
Share on other sites

Got to agree with @Pixrael. While page.js seems nice, it's probably overkill in this case, and since you already have ProcessWire to provide routing, it makes sense to just add JavaScript-powered transitions on top of that. I've used http://barbajs.org/ in the past for this purpose.

As a bonus compared to pure JavaScript approach you won't have to worry about search engines, non-JS enabled browsers, etc. as they'll still get the "regular page load experience" :)

  • Like 5
Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...