As last year, please find below my best of the different advent calendar.
- Day 1 : What it takes to build a website ? ; a gentle intro which makes the review between how we used to do some website and how we should do it today.
- Day 10 : Making website responsive, responsibly : take the opportunity to make your responsive site more accesible to offer some enhancements with new HTML5 features. Offline first is a good use case but others like light captor could be too.
- Day 12 ; is Agile harder for Agencies : a classical post on Agile in a Agency/Customer relationship/context and why it can't work as you expect if all actors don't change the way they work.
- Day 16 : An overview of SVG Sprites creation techniques : because you can do sprites with SVG (never think about it and don't use SVG that much so far). By the way you may consider SVG instead of icon-font...
- Day 20 : Meet for learning : turn your meeting into a learning experience for individual and collective progress.
- Day 21 : Naming things ; always a challenge !
- Day 22 : Integrate constrast checks in your web workflow : because all of us does not see colors as you expect.
24 jours du web (FR)
- Day 1 : Quand Saas ne rend plus service : Author introduce the limits of SASS or for the two examples mentioned where a CSS post-processor (like PleeeaseCSS or AutoPrefixer or px_to_rem) or some grunt/gulp tasks can bring more value than CSS pre-processor (like SASS). Article also compare the best case when to use the extend syntax or a mixin.
- Day 6 : Un guide qui a du style : introduction and thoughts about style guides which aims to collect, list and document every item of your frontend blocks and items.
- Day 10 : Guerilla design en mode responsive et mobile : author introduce both challenges and tips on about how design, UX and prototyping change with mobile/responsive approach. Also paper is better than software for quick and efficient prototyping.
- Day 12 : Le web mobile et la performance : a brilliant, relevant and instructing article on mobile and web performance so that you are more aware of the challegences, things to check/monitor and some solutions.
- Day 14 : Le nouveau : best and worst practices when you welcome a new member in your team. some food for thoughts !
- Day 15 : Design poli : some thoughts about "gentle design" which will not hurt end users by doing something he did not want (like install some extensions updates and preventing him using the app for a while or doing some crappy pop-ups and alternatives).
- Day 19 : Le beau et l'utilisable ; because the relation between prettyness and usability is not that obvious
- Day 2 : Running applications at scale with kubernetes : Kubernetes is a docker orchestrator and the article introduce the concepts and interest of the tool.
- Day 13 : Managing repositories with pulp ; pulp is a kind of meta repositories manager (ie whatever repo is CPAN, Maven or your linux distro). May be useful if you need to manage a large collections of repositories to be provided locally.
- Day 20 : the pursuit of learning through bad ideas : because even bad idears are still ideas and may be not that bad to get your solution.
- Day 2 : HTTPS & Web performance : some best practices arount HTTPS setup and around the issue raised when mixing https and webperf.
- Day 4 : HTTP 2.0 is coming, be ready : intro to HTTP/2, how it works and what it would/may change in the way we build web site/apps.
- Day 13 : Async Fragments : rediscovering rendering HTML progressive rendering : to some extend, the concept of lazy loading of your page only when you need it or at least in a way that makes the page loaded faster for your users. Attention to the fact that such a loading method will not hurt the behaviour of your page or the user focus.
- Day 16 : Graph your web-performance metrics ; I spoke about sitespeed.io earlier, now you can use is in conjunction with WebPageTest to graph and compare your scores over time.
- Day 19 : Tips for optimising SVG delivery for the web
- Day 24 : Fast forward performance : future looks bright : about the coming API focused on webperf being studied at the W3C level and so soon (when not already) available in browsers.
- Day 25 : W3C API in the wild, beyond plain load times : a consequence of post ab(ove, some example to know if a ressource is in the cache, failed to load and so on. Useful even if not ready for production yet.
- Day 29 : Different angles of Web Performance because you can see the topic in many angles : what is fast enough ? Presenting Data ? Load & Scalability ? Web perf optimisation ?
- Day 30 : leverage browser storage for a faster web : (ab)use of localStorage or other mechanism in your browser to save unnecessary http requests.