Recent Development
Overview
Over the last five years my client work has focused primarily on using Drupal 6 and 7, but still with a good mix of front-end implementations with pure HTML/JS/CSS and obviously the “obligatory” dependencies and services.
My own personal projects have continued to center very heavily around JavaScript, front and back-end. I've been experimenting, as usual, with some of the recent "crazes" — but tempering that risky cutting-edge with years of "vanilla" knowledge.
Unfortunately, most of my very recent client work has been toward a project I frustratingly cannot show here. However, I can highlight some of the elements I was charged with working on.
Codelamp v4
Redesigned parallax, and modern tech
My personal website has just be relaunched, rewritten entirely from scratch. You'll be viewing this right now, hopefully it shouldn't need much in the way of introduction.
What you may not know however is the site is constructed from a "Vanilla" CSS/JavaScript parallax framework, designed to work without JavaScript. The content is then handled by a smattering of microsites, each one powered by a different technology (Riot.js, React, and Angular).
This was done purely for the sake of learning, not because I somehow think it is good architectural practice.
You can read a bit more about the parallax journey here on my blog. Which is also powered by a different technology (Jekyll)
Demo reel
I have also taken the time to put together a demo to highlight some of my more favoured pieces of work.
It is still work in progress at the moment, it is also the first video I've put together since Video Production at school — so be kind ;)
Headless CMS, and CMS/Angular Front-end (2016)
Git, and many, many, repos ...
The last client project I was working on for a ticketing company, was actively using 90+ git repositories. This allowed for great modularisation and helped in avoiding conflicts, but became quite a task in terms of management. Especially when we weren’t allowed to use a git management tool like GitHub or BitBucket, and that it took 40 repos to build just one of the two sites we were working on.
To add to the complication, much of the development team were working remotely, with English as a second language, so trying to confirm that all developers were on the same page became a task in itself.
No time had been assigned to this issue, so we needed a quick solution. Some developers were already using a simple bash script to pull down multiple repos (considering there doesn’t seem to be a good tool for managing actions on multiple repos simultaneously).
So I extended the script outside of project time to give us what was required.