added filter function

[gyaresu]

This is where a templating framework like Handlebars might be useful to get away from manual formatting but I wanted to keep it to the tools you were already working with.

If you want an easy way to make it a live site (as it's all static files) checkout Surge.sh

demo: http://far-alarm.surge.sh/

gyaresu@shazbot:~/programming/projects/WorkshopInABox|gareth
⇒  surge .

              email: [email protected]
              token: *****************
       project path: /Users/gyaresu/programming/projects/WorkshopInABox
               size: 21 files, 1.2 MB
             domain: far-alarm.surge.sh
             upload: [====================] 100%, eta: 0.0s
   propagate on CDN: [====================] 100%
               plan: Free
              users: [email protected]
         IP address: 192.241.214.148

    Success! Project is published and running at far-alarm.surge.sh

[Brianfit]

Wowser, that's a completely different approach than I was planning but SO MUCH BETTER. Filter on everything! Excelllent: and bam, the magic of collaboration takes it down a different road. Thanks, Gareth, you've given me not just a working solution to this particular catalogue challenge, but a great story about open source collaboration to tell when presenting this tool. I may need your advice on how to now manage a forked project, that's new territory for me, but I'll have a crack first.

Handlebars. Yes... I keep seeing this mentioned but not investigated further than realising a) it has a learning curve and b) that learning curve always appears to exceeds in time what's necessary to hand code what I'm trying to do on a particular project. This ignores, of course, the aggregate future time I might save in just learning the damn thing.

[gyaresu]

You're so very welcome 👍

If you want to add me as a collaborator I'm more than happy resolve conflicts if that's helpful (repo settings in the vertical menu on the right)

Yeah, don't sweat handlebars. There's a dozen templating languages and there's no point fixing a problem you don't have yet. (that falls under the optimise too early dilema)

If you haven't got a pain point then there's nothing to fix/learn.

But there's definitely some fun to be had doing some http://nodeschool.io challenges or http://codewars.com/ or even the http://freecodecamp.com/ 'bonfires'.

There's a lot of these types of puzzles that will give you a few great tools in methods like map, filter and reduce (functional programming for the win).

They're good fun and they'll wrap your head around asynchronous programming (callbacks) which is essential to survive in Javascript. (Plus they come with solutions so it's a great way to learn)

Funny thing is you don't even need jQuery anymore as the native libraries are robust without it.
There's nothing wrong with making things easy though. A little syntactic sugar makes the medicine go down. (i.e. http://underscorejs.org/ has amazing functions that just make life a lot easier)

Anyway... Team Canada has Toast the Coast tonight so I'll be around Sunday if you want to do any live coding