25 Feb 2015, 09:30

Around the Web - February 2015


  • The Fold manifesto : why the page fold still matters ; even if we get used to scroll, we need to be encourage to do it. Thus the fold is strategic to convince the user to make the effort to go beyond this limit ; whatever the size of the device is (RWD included).



  • OCTO was at DotJS and try to sum up what is the status of frontend frameworks (in French) mentionning Web Components, Isomorphic javascript (ie both in frontend and backend side) and some ideas around the announcement of the AngularJS 2.0 which generated a lot of noise.

CoreOS, Docker & co

  • Discover Docker; another blog from OCTO, about CoreOS. So if you don't know about CoreOS, Etcd and Fleet, the article is for you so that you have an overview of what is CoreOS.
  • Nuxeo made a summary of their use of CoreOS (including Fleet & Etcd), Docker and the tools they build for Nuxeo.io platform. Very interesting summary.
  • If you are interested in minimalist OS, this post on Docker blog mentions "of course" CoreOS but also Ubuntu Snappy Core (Ubuntu based) or Project Atomic (closed to RedHat/CentOS/Fedora system).

Responsive Webdesign

ReactJS, Flux


  • Making a complete polyfill for the HTML5 details element : if you were to bridge the gap by providing a feature a browser does not include, it is very interesting to see the how it is done from a methodological point of view.
  • Improve your lists with style ! Now that counters are "stylable", you can do a lot of things to improve the rendering of your lists (no more bullet points but some shiny icon ?, manage padding, etc). HAve a look at the demo (requires a modern browser)

01 May 2013, 22:45

Pagination and View all

Back to ergonomy with an article from last alert from Jabob Nielson called : "Users' pagination preferences and View all" reviewing some pagination use cases and the opportunity of a "View all" feature and of course to save user's preference when you can to avoid poisoning his user experience.

Some examples where pagination is fine like for Search Engine Result Pages ; You don"t consider your users to see all of the pages and you are able to promote the top results to him. Thus, they will limit them to the first pages, when not only the 1st ; to some extend, we could consider that it's useless to compute more than the n first pages..

Some examples where pagination is badly considered :

  • When users may need to see all the content to make his choice and needds to embrace the whole selection to progress in his thinking. Ex for clothers where you want not to see only the 5 first shirts but the whole collection to make your choice between colors.
  • Articles and other linear content flows should never be paginated as breaks are badly considered. Or at least you should provide both views (full & paginated).

View n items vs view all : author would recommend to have a default pagination value and a view all option than to have a "view 10/20/50/100 items". Moreover, the default pagination view and view all will simplify your form management as the choice would be easier thant if you propose multiple pagination steps. Easy filtering is better than complex one.

Of course, the "View all" for performance issue may be limited or being available only when your query is small enough (less than 100 items ?)

Last but not least, once your user chose a preference about pagination, be consistent with it during its session and later if possible so that he does not get lost or will get angry to refine each time his preferences.