title: Server-side, CSS et UX

*Billet comportant les liens de veille technologique présentés aux étudiants dans le cadre [d’une routine de mes cours](/david/blog/2015/cours-iut-construction-collaborative/).*

> Say what you will about server-rendered apps, the performance of your server is much more predictable, and more easily upgraded, than the many, many different device configurations of your users. Server-rendering is important to ensure that users who are not on the latest-and-greatest can see your content immediately when they click a link.
> 
> <cite>*[You’re Missing the Point of Server-Side Rendered JavaScript Apps](http://tomdale.net/2015/02/youre-missing-the-point-of-server-side-rendered-javascript-apps/)* ([cache](/david/cache/b0d05411a11c9944bff0dee0fb7baa71/))</cite>

Ainsi que [la réponse](http://ponyfoo.com/articles/server-first-apps) ([cache](/david/cache/ff89062d4ecd5c0bc3396a78462ae5cc/)) qui considère Angular comme étant le Bootstrap de JavaScript ♥ (merci [la veille de Makina par Simon Georges](http://makina-corpus.com/@@search?sort_on=Date&sort_order=reverse&Subject:list=Veille)). Pour aborder la génération de pages côté serveur.

> An extensive CSS reference with all the important properties and info to learn CSS from the basics
>
> <cite>*[CSS Reference](http://tympanus.net/codrops/css_reference/)*</cite>

Plutôt bien fait et [l’article sur Flexbox](http://tympanus.net/codrops/css_reference/flexbox/) est relativement complet.

> A login form with two fields, two buttons, and a link on it seems simple, right? Bog standard. It is, until you consider all the ways the simple act of logging in with those two fields can go wrong for the user. Let's think.
>
> <cite>*[The God Login](http://blog.codinghorror.com/the-god-login/)* ([cache](/david/cache/fa32abb406282b737d9f0fb65d6ab084/))</cite>

Ils sont intéressés par l’UI/UX donc c’est l’occasion d’engager la discussion.
