Continuously delivering software to production systems is a key part of building great digital products and creating a culture of agility within different teams. In this post, I will share our recipes for building pipelines centered around Concourse CI.
Although AWS re:Invent 2018 is now over, the announcements will have a wide ranging effect on how we build our products over the coming years.
We use AWS for our Serverless microservices built using the awesome Serverless Framework, so it is really great for us to see the rapid iteration and improvements to the backing services that we use on a daily basis (check out our post on going serverless).
Back in February we held a hack day which led to this post on practical tips for organising one. One of the problems we tried to find a solution for on the day was from our Impact & Investment team. They were receiving a lot of applications for funding that didn’t meet the eligibility criteria we’d set out. This was wasting the valuable time of both those spending the time completing an application and the team at Comic Relief who review them.
Hackdays and hackathons are a fantastic way to engage your development team in new challenges. At Comic Relief, we’re pretty pleased with the outcomes of our hackdays – while we may not always get a product out of the day, we never leave a hackday without gaining clearer view of what we need to do to solve user and business problems.
This post is just a few practical tips for anyone who’s looking to organise a hackday – sharing what we’ve learnt from organising our latest hackday.
Accessible digital experiences are something we strive for at Comic Relief – we’re not perfect at it, but we’re trying to make sure that we can embed inclusive design at the heart of our product development*. In this article, I’ll be sharing some of the peaks and troughs of our accessibility work and the progress we’ve been making to ensure our digital experiences are accessible to all users.
Working in the charity sector you learn to be pretty resourceful when you need to be, and that doesn’t stop at blagging free stuff (obviously we never do that ;)).
One of the most significant things we learnt from amalgamating our campaign sites onto a single platform was the efficiency that emerged from reusing code and functionality.
So when our Schools and Youth team approached us with an objective that was new to all of us we did what anyone else would do, look at what we’d done already and could copy!
For the past four months, the Platform Squad at Comic Relief has been working on a content migration from the old Drupal 7 code base to our beautiful new Drupal 8 platform. Anyone who’s been near this blog in the past year will have heard tons about the new platform (available here on Github) – but what today’s post is about is the final stage of the migration, ‘Going Live’.
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.
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.