daily links

  • Locometric
    RoomScan The App that Draws Floor Plans by Itself
  • karacas/imgLiquid
    A jQuery Plugin to resize images to fit in a container.
  • facebook/watchman
    Watchman exists to watch files and record when they actually change. It can also trigger actions (such as rebuilding assets) when matching files change.
  • Naming UI components in OOCSS – CSS Wizardry – CSS, OOCSS, front-end architecture, performance and more, by Harry Roberts
    tl;dr Keep using agnostic, abstract, OOCSS classes in your markup, but add any desired meaning to your HTML via a data-ui-component attribute, e.g.: <ul class="ui-list" data-ui-component="users-list">.
  • Quick Tip: Solving the Equal Height Column Conundrum – Tuts+ Web Design Tutorial
    How can I have 100% height backgrounds in my flexible multi-column layout?
  • Fast 404 | Drupal.org
    Drupal has expensive 404 errors. On an ‘average’ site with an ‘average’ module load, you can be looking at 60-100MB of memory being consumed on your server to deliver a 404. Consider a page with a bad .gif link and a missing .css file. That page will generate 2 404s along with the actual load of the page. You are most likely looking at 180MB of memory to server that page rather than the 60MB it should take. That’s where Fast 404 comes in. This module combines a very common method of handling missing image/file 404 errors (discussed here and planned for Drupal 8) with a method created by dpardo (a co-maintainer of this project) to deliver super fast 404 error pages for both missing images and bad paths. Depending on which method of implementation you choose (aggressive or super aggressive) you can deliver 404 errors using less than 1MB of memory on your server.