For those who aren’t familiar with the concept of Pattern-Lab (or a Pattern Library), it’s essentially a living style guide; a common tool in modern web development. At their most basic, they are continuously updated documents that help documenting common design styles for web components, bringing together the intended look & feel with the images and codes to build them.
Over the last year a key objective for the Technology team at Comic Relief has been to build products not websites. Tech Lead, Peter Vanhee, explained in a previous blog post how we’re using Drupal 8 to create a reusable platform product for building campaign websites. Since then the team have been working to deliver another website using the platform codebase and also preparing to open-source the codebase.
10 years ago (at the end of 2006), Drush appeared to make it easy for Drupal developers to do some common tasks, it wasn’t immediately popular as it was a Command-LIne tool and a lot of people didn’t appreciate the idea, but year after year it’s popularity grew as did its functionality.
I talked about our journey of building a product to power all our editorial websites at Comic Relief (see my previous blog post), and focused on three topics: editor experience, automation & streamlining, and using decoupled services.
Hey, I’m Leigh. I’m a digital designer at Comic Relief and this is my first post for the Comic Relief Tech Blog! I’ve just started working on a new digital storytelling product and thought it might be interesting to blog our journey, through our processes, what’s working, our challenges etc. In this first post I’ll start by giving a little context to the work.
Working at Comic Relief has challenges unlike any I’ve experienced in previous roles at startups or agencies. When working in other roles, I’ve known exactly who our ‘target market’ are, what traits our users have and what we believed their biggest needs were, but how do you identify your core user groups when your brand is a national treasure?
In the past we used a Drupal 7 multi-site powering at least 3 different sites at the same time with all our business logic bundled inside of various massive custom modules shared along all the sites and some of them with dependencies of external modules (like Message Broker) and each site was using a different version of these modules.
We changed a few of the services that support our apps for Red Nose Day giving pages before the big day this year.
One of the more interesting processes was finding a good solution for all our caches and session data. In many cases, we found a Redis service worked well with our Cloud Foundry apps, especially when data has to be shared.
‘A lack of women in technology jobs is not just a problem for women, it’s a problem for the whole sector.’
That’s the conclusion reached by the Tech Partnership and Founders 4 Schools, who recently published research into diversity in the sector. Alarmingly, this research also found that only 17% of technology staff are female. Worse still, fewer than 10% of these women are in leadership positions.
Kids are my favourite kind of user. I haven’t yet met a user with more honest feedback than a pre-teen. And there’s no shortage of it: they always seem to have a lot to say for themselves!
This year our tech team created Comic Relief’s third version of a digital interactive story for teachers to use in primary school classrooms – and it’s the best one yet (not that I’m a proud Product Manager or anything).