My favourite resources for making websites
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
Louis-Olivier Brassard 3b2ee333f9 Mise à jour de '' 1 month ago
.gitignore Initial commit 1 month ago
LICENSE Initial commit 1 month ago Mise à jour de '' 1 month ago

My favourite resources for making websites

Here is a collection of my go-to resources when creating a website, loosly organized by topic.

Thinking, planning

  • Notebooks and plain paper
  • Black ink pen (Pilot Hi-tecpoint or similar)



  • Brackets
  • Vim (command-line text editor) + plugins
  • A really nice terminal (like iTerm)
  • ZSH (better than bash)
  • Powerlevel9k (terminal goodies for ZSH)
  • Nodejs + NPM (command line tools, task runners, scripts you can easily write and hack on)


  • HTML5 boilerplate
  • Handlebars
  • Mustache



  • SmoothScroll (enable smooth scrolling on anchors)
  • Swipe
  • Gumshoe (nice little companion to SmoothScroll)
  • Fastactive (touch responsiveness on hover)
  • Bean (polyfill events, although not really required anymore, since browser support is pretty ok)
  • Swup (AJAX transitions between pages)
  • Require (tiny drop-in replacement for RequireJS)
  • Microjs (libraries for javascript stuff)
  • Webpack (the setup is a bit of a pain though and you don’t always understand everything)

Static-site generators

  • Hugo
  • Hexo
  • Eleventy


  • Grav
  • Perch
  • Kirby
  • Google Drive (fetch raw data with ArchieML, for example)
  • GitHub / GitLab / etc. to host text files
  • No CMS (text files)

Fuck off, Wordpress.

Version control

  • Use Git from the start.
  • Host the code on an online repo (not just on your local computer).

Code snippets and examples

  • Codyhouse (modules and blueprints)
  • Codrops (code experiments)


  • Remain minimal. The website should do what the website should do, nothing more. Don’t take up bandwith, don’t eat up the CPU, just deliver the fucking content when the visitor asks for it.
  • Design for all. Do not assume everyone is using cutting-edge technology (oh, and there are bugs in there, too).
  • Users are stupid. Just be nice and make things easy for everyone.
  • Use the standards. Don’t reinvent the wheel. Look around, reuse stuff, don’t try to play the original perfectionnist.
  • Structure the content naturally + semantically. Nest categories appropriately. Section > Subsection > Page. Reflect that logical structure in the site.
  • Make things tangible. Create visual feedback. Help the user grasp the navigation and actionable content.
  • Respect privacy. Say no to google analytics.
  • Keep a small footprint. Save server energy, bandwith, device resources. Good for the user, the environment, and for the developer (less time + energy consuming).
  • Use less tools. The more tools you use, the less easy the project is to manage (and the more time it consumes), and the less likely fine-tuning changes are made.