@damianwalsh

35 Followers
79 Following
121 Posts

Designer based in Manchester, UK.

#11ty #CSS #IndieWeb

Websitehttps://www.damianwalsh.co.uk/
@irina @robb In hot weather, consider bathing exclusively in rainwater collected from your butt
@robb 300bn litres of water lost daily through leaks in the supply network. No new reservoirs built since 1991. But yeah, our bad for not deleting old emails.

Suddenly and viscerally obsessed with these letterforms. Why has that never occurred to me, and why is it the first time I’m seeing the idea??

(Font is ALS Lamon by Dmitry Lamonov.)

@underlap Nice write-up Glyn. I'm neither an engineer nor a web developer by trade, but I also found learning through experimentation to be a better way of getting to grips with Eleventy. Its flexibility seems to be a great advantage for practically everything—except perhaps understanding how it all works. By the way, I always think of Douglas Adams whenever I hear or say "Eleventy."
@cory The data is fascinating, isn't it? My project is somewhat different, being based on a collection of CDs and vinyl, but I noticed patterns with track numbers. It's almost like there's a formula for where they place the big hits. Release dates too—so many of my records were released around the same date in May across years and decades. I imagine executives saying, "this will be the big summer hit!".
@cory Very cool! I like how this view surfaces your individual track plays across the entire album. I’m guessing this one stacks the big hitters up front!
@rem Nunjucks. Wasn't a particularly conscious decision at the time, but because most Eleventy tutorials use it. Might switch to Vento or WebC someday if I summon up the bottle for a rewrite.

@jaredwhite +1 for using the Michael Engen approach. I was able to get my data from LinkedIn in JSON and that now is the source of truth for both my webpage and PDF using Eleventy and Puppeteer.

https://damianwalsh.co.uk/resume/

#11ty

Résumé

Designer (Interaction/UX/UI) based in Manchester, UK

@castastrophe 2000s web team: copywriter, designer, developers (front/back-end), information architect, and manager. Those people kicked ass, seriously. I still remember them fondly—one remains a close friend. Management hired independent thinkers and trusted them to deliver. In fact, it was a great shame when the company grew to a size where it was felt "agile" ways of working were required. Everything slowed down, people became miserable and left. Autonomy worked better than process.
@cory Watching the liquid glass debacle unfold alongside almost every other tool I use sprouting features I don't want or need makes me think I might actually be doing something sensible here, rather than just launching into another project because why not 😅