Allow "hitsPerPage" and "page" query parameters

[tholman]

This PR allows the apiServer to pass through hitsPerPage and page query params, as per the Algolia api

Includes:

• Small changes to apiServer.js to allow the passing of the params
• Changes to the documentation page, showing how to use the params

[tholman]

Any questions/clarifications needed here? I'm happy to chat.

[tholman]

Anywhere I can drop a few $'s to get this & #191 looked at? :) cc @PeterDaveHello

[PeterDaveHello]

Thanks for the pull request and sorry for the late review!
There are few empty line changes not related to the function itself, please revert it.

I have only two concerns here:

1. Would hitsPerPage be appropriate enough or can we use something more friendly than hits here?
2. A little bit familiar with the above issue, I wonder how many websites using page = 0 as the first page in the parameter? What do you think about we treat 1 as the first page and just minus one and then send to API?

[tholman]

Would hitsPerPage be appropriate enough or can we use something more friendly than hits here?

I went with hitsPerPage as the query parameter, for the most part so the API matches with the algolia API, which we're using here to get the results anyway. Happy to change it, I only feel like it adds a small layer of unneeded confusion.

A little bit familiar with the above issue, I wonder how many websites using page = 0 as the first page in the parameter? What do you think about we treat 1 as the first page and just minus one and then send to API?

Same point here as with the hitsPerPage issue, feels strange to defer from the algolia api that we're interfacing with in the first place.