Transforming The Relationship Between Designers And Developers

In the forever-shifting landscape of design and technology, some rare artifacts surprisingly never change.

Throughout the last two decades, we have witnessed the astonishing evolution of creative tooling, methodologies, and working practices. However, after all of this advancement, we still have clients asking to make the logo bigger, designers despairing as their creations are built with not quite the exact amount of bottom-margin, and developers going crazy about last-minute design changes.

Quite frankly, I’ve had enough. So join me in a parenting-style-hands-on-hips pose of disdain, roll up your sleeves, and let’s fix this mess together, once and for all!

Why Is This Still An Important Topic?

Ultimately, the quality of your designer-developer relations will have a vital impact on the quality of your product. In turn, this will impact customer experience (be it internal or external).

Customer experience is everything, and these days the smallest of chinks can create an even bigger dent in the business itself.

It may not even be an obvious or noticeable issue. Over time, those moments of misunderstanding in your team could result in a series of micro-inconsistencies that are felt by the customer yet sneak underneath the radar of quality assurance.

Perhaps you’ll catch these things during user research, but in this scenario, you’d be playing catch-up instead of advancing forward.

To cut a long story short, it could be slowing you down in the race against your competitors and costing you more money in the process.

So, with that in mind, let’s get stuck into the techniques that can steer us in the right direction and inspire everyone on the team to deliver the slickest of user experiences together.

Working Culture

In my opinion, process improvements may only get you so far. The working culture in your organization will heavily influence the output of your digital teams. Whilst the subject of culture is incredibly vast, there are a few key elements that I think are hugely important to foster a greater level of collaboration between design and developers:

  1. Alignment on the goals of the project and/or business.
  2. Encouraging a more “robotic” attitude to feedback. Of course, you can be passionate about what you do, but when it comes to feedback, I always try to encourage people to respond with logic before emotion.
  3. Communication: Ultimately, you have to trust people to be proactive. You can have a great process, but the gaps and edge cases will still slip through the net unless you have people who are open and ready to prod each other when issues arise.

This may seem like common sense to many of us, but many organizations (big ones, too!) still operate without this crucial foundation to motivate and support their teams.

However, it is essential to be honest with yourself and consider the role you play within your team. Even if you think you have already fulfilled these criteria, I’d encourage you to investigate this further to ensure everyone feels the same. It can be as simple as having a 121 discussion with each member of the team, or you could even send out short questionnaires to gauge your workplace’s suitability for an optimal designer and developer collaboration.

You might be surprised by what you hear back from people. Treat any criticism as gold dust. It’s an opportunity to improve.

Once you’ve created this foundation within your organization, it’s important to maintain and protect it. Keep reviewing it regularly, and make sure that anyone joining the team will be able to fit in. This leads us nicely on to…

Hiring

If you’re scaling your team, maintaining quality can always be a challenge as you grow. Despite the challenges, it’s important to continue hiring people who have a positive and empathetic attitude to ensure you can maintain this foundation within your workplace.

In order to gauge this, I would like to include the following interview questions.

Developer

Begin by showing a sample screenshot of your product or a specially crafted concept design:

“You’ve just built X, and the designer wants to change Y. How do you respond?”

Follow up:

“The designer and PM reject your suggestion because of ___. How do you respond?”

Designer

Begin by showing a sample screenshot of your product or a specially crafted concept design:

“The developer says, “We can’t build X quickly; can we do Y instead to deliver faster?” How do you react?”

Follow up:

“The product owner says they are then disappointed with the design. How do you react?”

I recommend asking these kinds of questions in the middle or towards the end of the interview so you have already built rapport. If the candidate is at ease, they are more likely to let slip any negative attitudes that lurk beneath the surface.

I’ve asked interview questions like these to many designers and developers, and every so often, they will openly criticize and stereotype each other with a smile on their faces. I’ve even seen some candidates become visibly frustrated as they recount real-life scenarios from their own experiences.

How you score this is more difficult. Ultimately, skills and work ethic are the most important things, so concerning answers to these questions may not necessarily lead to an outright rejection but perhaps flag something you may need to work on with the candidate if they do later join your team.

Hopefully, in most cases, the stronger candidates you speak to will naturally provide balanced and conscientious responses to these tests of character!

Process

We talked a bit about hiring, but I’d imagine many people who need this article are more likely to be in the midst of a designer-developer flame-war as opposed to trying to prevent one in the future!

So, what can we do process-wise to keep things flowing?

Provided that there is plenty of early and ongoing collaboration in your workflow, there is no absolute right or wrong answer. It’s about what fits your team and your product best. Ultimately, you need to discard the silos of the past and start working together as a team early on.

  • Developers would typically be the last people to get involved, but they should be involved from the start to guide technical feasibility and provide their own ideas.
  • Designers are often more involved in the beginning but can often drift away before the end of a release. However, we need to keep them onboard and get them to play with the product so we can keep making it even better!

It’s important to be open-minded about the solutions. Alas, I have even worked in organizations where different teams have different approaches. Bearing that in mind, here are some good places to start in terms of exploring what might work for your workplace.

Scoping

When new features are on the horizon, getting everyone involved in these discussions is crucial.

Sometimes, it can be difficult for developers to detach from the current sprint and think ahead, but it’s important that we have their guidance, and it is ultimately going to save them (and the whole team) time further down the line.

Scoping can appear in many different forms across the spectrum of agile methodologies out there. It’s not my intention to cover any of these and discuss all the positives and negatives of each (that’d make this into a book, and not one that anyone would like to read!); in fact, I am deliberately not mentioning any of them. This article is ultimately about people, and the people we need at this early stage are not just the stakeholders and a product manager. We need designers and developers shaping these early discussions for the following reasons:

  • They will bring their own ideas.
  • They will visualize the idea very quickly and assess its feasibility.
  • They will connect the concept with other parts of the domain.
  • They will also (albeit rarely!) prevent an impossible dream or daft idea from growing on the face of the business like a festering wart.

Another Perspective On Scoping: SquaredUp

In order to take a deeper dive into the subject of scoping, I spoke to Dave Clarke, product manager at SquaredUp.

“Developers are looped in during the design stage, and we’ll test interactive mockups with the engineering team as well as other internal stakeholders before going out to external audiences for feedback. This means that when a feature is ready to be built by an engineer, they’re already really familiar with what we’re building”

— Dave Clarke

Back in late 2018, I met the SquaredUp team at an open day in their UK hub in Maidenhead. I was impressed by the quality of their product, considering it was a very technical audience. It looked beautiful, and you could tell that they went the extra mile in terms of collaboration. Not only do they involve developers in the design phase, but they get them involved even earlier than that.

“We send engineers to events so they can talk to customers and hear their pain points first-hand. This helps foster a real appreciation and understanding of the ‘user’ and ensures designers/developers/PMs are all coming at a problem with a solid understanding of the issue from the user’s perspective.”

— Dave Clarke

This brings us back again to that all-important foundation. Alignment on goals is key, and what better way to reinforce that message than by getting everyone involved in hearing directly from the end users of your product?

Design Presentations

Once the wheels are in motion on the big new thing, many teams like to have the designer present their work for forthcoming iteration(s) to the team. This allows everyone to have a say and get excited about what is coming up.

Once again, there are many organizations that would simply agree on the design between stakeholders and designers alone. From the developer perspective, this is incredibly frustrating. Not only will it result in a lower-quality output, but it will also make developers feel as though their opinion doesn’t matter.

With my developer hat on, though, I absolutely love these kinds of sessions. They allow us to question the details, suggest alternatives, and consider how we slice stuff up into smaller bundles of value that can be released faster.

With my design hat on, it caters to my need to think about the bigger picture. It’s not always practical to design iteratively, but in these sessions, we can all get together and appreciate the end-to-end experience.

Typically, we allow the designer time to talk through everything, allowing for questions throughout, and give everyone a chance to dive in and bring their ideas to the table. However, do what works for your team. If you have a designer who wants to present, take all questions at the end and then make changes afterward, do that. If you have one who likes handling lots of questions throughout and makes changes live, go with that.

Perhaps even give it your own identity, too. In my current workplace, one of the squads calls it Design Time and in our squad, we decided to open the name to a poll, and thus (with one cheeky addition to the poll from a colleague) the Itty Bitty Refinement Committee was born!

Managing Conflict

However, these kinds of sessions do have the potential to get sidetracked. So, as with any meeting, it is essential to have a clear agenda and ensure that good facilitation prevents things from going off-piste. If there are conflicts, I always try to find resolutions by considering where we might find the answers. For example,

  • Can we look at our analytics?
  • Which option is a better fit for our company goals?
  • Could we do an A/B test to see what is more effective?

When people bring ideas to the table, it’s always important to acknowledge them positively and seek further exploration. Sometimes, we can agree on an approach quickly, and on other occasions, we can defer the discussion to a later refinement session.

Sharing Responsibilities

In my opinion, there is also a gray area between designers and developers, where it often isn’t clear who holds responsibility. This is a big risk because, in many organizations, essential aspects can be completely forgotten.

From my past experience, there are two key areas where I see this happening often. So this may not be exhaustive, but I encourage you to think about these and then ask yourself: Is there anything else — specific to my organization — that could have fallen into this void between our designers and developers?

See if you can identify these risks and agree on a way of working together to ensure they are tackled effectively.

Animations

Nowadays, many dev teams are working on JavaScript-heavy applications, and most of us will have the power of CSS transitions at our disposal. Yet, I frequently land on new projects where they aren’t being leveraged to enhance the customer experience.

Animations can be quite time-consuming to create using many design tools. In particular, I often find that loading states are quite fiddly to prototype in some cases.

In my recent work at Floww, I collaborated with designer Hidemi Wenn on an animated progress bar. For the first version, Hidemi had begun with an idea crafted in After Effects. I replicated this in a CodePen and suggested adding some bubbles to highlight the changes in the numbers.

Note: Of course, CodePen is just one example of this. There are many other tools out there, such as Storybook, that can also allow us to build and collaborate on ideas quickly.

See the Pen Bar Chart of Destiny [forked] by Chris Day.

This allowed Hidemi to see her creation working in the browser early — before it had been fully implemented into the product — and we then collaborated further to make more enhancements.

“Working together like this was awesome! We could easily bounce around ideas, and tweaking the animation was a breeze.”

— Hidemi Wenn, Product Designer at Floww

Pairing is often between developers, but why not jump on a call and pair with a designer whilst you write the CSS? This gives them full transparency, and you can collaborate together.

Nowadays, we have amazing tools at our disposal to collaborate, and yet still, so many designers and developers elect to operate in silos.

Accessibility

One of the first things I do when joining any existing digital project is to spin up Wave (an accessibility testing tool) and subsequently slump into my seat in despair.

Accessibility is something that always suffers as a result of a designer/developer standoff. Some might say it’s the realm of design, while others would argue it’s quite a technical thing and, therefore, lives in dev land. The truth is it is a shared responsibility.

Take something like :focus, for example. Whenever I review code, this is something I always check and often discover it’s missing. Ask the developer, and they’ll say, “We didn’t have designs for it.” Well, perhaps, ask the designer to create them, just as I’d expect the designer to query an unimplemented state they had designed for.

We should scrutinize each other’s work and continue to channel our inner robot to respond with logic when it comes to constructive criticism. Keep encouraging everyone to embrace feedback because that is the gold dust that makes our product shine brighter.

During Implementation

Having steered our way together through the implementation of our features, at some point, we begin to approach the time to release our features into the wild. We are on the final stretch, and thus, it’s time for developers to stage a reverse-design presentation!

Whilst mentoring developers on this subject, I always remind them not to take the feedback personally.

Likewise, I ask designers to never hold back. Be persnickety (in a kind way!) and ensure all your concerns are addressed.

It’s only natural for a developer to behave defensively in these scenarios. As a result, designers may hold back on some of the feedback they provide in order to prevent upsetting the developer.

Developers are often very vocal, and if you are tasked with delivering a barrage of design feedback to them, it can appear daunting and make designers fearful of a backlash.

Prevent the silo. Perhaps have a third party, such as the product owner/manager, attend the meetings. They can diffuse any situation by referring us all back to the business value.

I’ve also witnessed rare cases where the developer has nodded and agreed with all the feedback and then just hasn’t implemented any of it afterward! So, make sure it’s all captured in whatever project management tools you use so you can follow up on the status. Sometimes, it’s easy to forget to do this when the changes are so small, so often (in my current team), we might create a single ticket on our board to implement all the feedback changes as opposed to creating a work item for each.

Another common issue I’ve found is that I’ve met many designers who don’t actually ever test out the products that they design. For me, they are missing out on the opportunity to further hone their work, and to learn.

If you’re a designer, ensure that you can log in to the app/website. Get a test account from someone, and try to break stuff!

Once all the feedback is in, we can create more work items to give our product those magical finishing touches and ship our masterpiece to the World.

Design Systems

Having mentioned focus states earlier on, you were probably already thinking about design systems before this heading came along! Of course, the design system plays a key role in helping us maintain that consistency, and ensuring accessibility concerns are baked-in to our library of beautiful components.

There are many, many articles about design systems out there already but here, I am going to just consider them in the context of the working relationship.

As the design system encourages reuse, it encourages us to think about other teams in our organization and be more mindful.

If the basic building blocks are covered, we can focus on solving more complex challenges together. I think this is also a really important value to get your teams on board with.

Design systems can also cause friction. Not everyone will get on board with it. Some designers will feel as though it restricts their creativity. Some developers will be frustrated at having to update the design system instead of cracking on with their own features.

In my opinion, these attitudes will not only slow you down but could harm the working culture of your business. Nowadays, I’d say it’s absolutely crucial for any product team (big or small) to have a design system and have the majority of your team buying into it.

I’ve been present at organizations where the design system is neglected, and in these cases, it actually ends up worse than not having one at all. You really need the majority of your team to be committed to it; otherwise, some people will go off-piste and keep reinventing the wheel (probably without those focus states!).

Another Perspective On Design Systems: GOV.UK

The GDS (Government Digital Service) of the UK has built a design system that serves a vast spectrum of different services and tech stacks. An enormous challenge, which is almost certain to be of interest in our quest for knowledge! So, I got in touch with product designer Ed Horsford who has worked on a series of government services that make use of this.

“GDS provides the GOV.UK Prototype Kit, so as a designer, I can create something in the kit, make full use of the functionality of the design system, and point developers towards the prototype.”

— Edward Horsford

Whilst many other organizations are now making use of tools such as Figma’s excellent Dev Mode feature to streamline design handover, this still requires naming conventions to be lined up between the codebase and the Figma component library. What’s impressive about GDS’ approach here is that the provision of their own prototyping tool makes it absolutely clear to developers which components need to be used. However, the availability of a great design system tooling doesn’t always guarantee a smooth outcome, as Ed explains:

“It can be a bit of a mind-shift for developers new to the UK government or using design systems in general — they may default to hand coding the HTML and CSS to match a design, rather than using the components from the design system to match the prototype.”

“If there is a bespoke requirement outside of the design system, then I will always call it out early so I can discuss it with the team.”

— Edward Horsford

Once again, this takes us back to the importance of communication. In a landscape where a design system must be deployed amongst many different teams, it’s up to the designers and developers to scrutinize each other’s work.

It was great to hear that as a designer, Ed was actively looking at the front-end code to assist the developer, ensuring the design system was respected so that all of its many benefits could be embedded into the product.

Crisis Mode

I appreciate that much of the advice in this article requires planning and a fair bit of trial and error. So what do you do if your designers and developers are already engulfed in a mass brawl that needs to be quelled?

In these scenarios, I think it is an ideal moment to pause and simply ask each member of the team: What is our goal? What are we working towards?

If people are angry, in some ways, it’s a good thing because you know they care. People who care should always be open to a bit of a reset. Openly discuss what everyone wants, and you’ll probably be surprised at how aligned people really are; I always go back to this fundamental and work onwards from there.

Sometimes, we get so tangled up in the details we forget what is truly important.

Apathy

For every angry team, there are probably many more that just don’t give a crap. For me, this is a far worse situation.

Every problem described in this article could be present. The designers make mockups, the designers build them without question, and everyone gets paid. Who needs to question anything? It’s just a job, right?

Can we really fix this?

Well, in my opinion, you are going to need a much deeper dive into company culture to try and revive that team spirit. I have worked at places like this in the past, and it is very challenging to try and implement solutions when the people are just not bought into the vision of the organization.

Whether this is feasible or not depends on your role and the organization itself. I have walked away from situations like this in the past because I didn’t feel as though the organization was willing to change or even be able to acknowledge the problem.

Conclusion

The dynamic between designers and developers is a subject that has always been of great interest to me, as I’ve worked in both roles as well as being an agency owner.

I’m confident as the years continue to progress, this will become less of a problem as the world of work continues to gravitate towards greater levels of inclusivity, honesty, and openness. The foundations of great company culture are so crucial to ensuring that designers and developers can unite and take on the world side-by-side on behalf of your organization.

For now, though, in today’s fragmented and divided world, you can gain a true competitive advantage by leveraging the power of a harmonious digital team built on the foundations of your organizational values.

Go smash it!

Smashing Podcast Episode 65 With Alex Older: How Do You Run A Grassroots Conference?

We’re talking about running grassroots conferences and meet-ups. What does it take to organize a small industry event for your community? Drew McLellan talks to WDC’s Alex Older to find out.

Note: This episode of The Smashing Podcast isn’t sponsored by anyone. However, our guest Alex has generously offered listeners a 10% discount on tickets to WebDevConf. So if you’re in or able to get to Bristol for the conference go to webdevconf.com for tickets and use the code smashing to claim your discount. Thanks Alex!

Show Notes

  • Alex Older’s website.
  • Save the date for WDC2023: 20 October in Bristol, UK.

Weekly Update

Transcript

Drew: He’s a full stack developer and founder of development agency Bluefly Digital here in the UK. He’s also the founder and core organizer of the UK’s longest running web design conference, WDC, which is now entering its 14th year, all of which makes him the perfect candidate for our discussion today. So we know he’s an accomplished developer, business owner, and conference organizer, but did you know he invented the pork jam roly-poly? My smashing friends, please welcome Alex Older. Hi, Alex. How are you?

Alex Older: Hi, Drew. I’m good. I’m smashing.

Drew: Good to hear it. Congratulations on what’s about to be the 14th year of WDC...

Alex: [inaudible] facts are wrong there.

Drew: My facts are wrong? Oh...

Alex: So it might be the 14th event, but it’s been running since 2007.

Drew: Okay. So the 14th edition, is what we should be saying, the 14th edition of WDC.

Alex: Yeah. Absolutely.

Drew: Okay. My introduction and everything is incorrect due to my poor research, but I think we’ll get away with it. But your 14th edition this October.

Alex: Yes.

Drew: For those who don’t know, it’s a very much... It’s a local feeling event, even though actually its reach is felt across the region and across the UK. Correct me if I’m wrong here, you have a day of workshops, and then a conference day, or have done in the past?

Alex: We have done in the past. What I’ve found is that, whilst it’s great to do workshops, is that it can be quite hard to find subjects that are appealing to a lot of people. I’ve seen it work for events and conferences that are very focused in one area. So if it’s a WordPress conference or a design systems conference or something like that, because they’re focusing on one area, a workshop relating to that works a lot better than stuff for WDC, because it’s very general.

Drew: Yeah. It’s a broad subject area, isn’t it? So finding enough people who want to focus down on a small bit for a workshop is trickier.

Alex: Yes.

Drew: Yeah. That makes sense. I remember a few years back, I attended one of your workshops, I think it was a node workshop with Jack Franklin, which was great. I learned a lot that day. That was brilliant. These days you’re sticking to just the main conference day?

Alex: Yeah. So last year because of various things, we hadn’t done an event for a few years, so we decided to come back with a bang and do two days, which was nice because it meant we could get lots of people to come and speak for it, and it drew a slightly different crowd as well, which was quite nice. But the organizing headache of it all, I was like, "No, I’m just going to do one day." It’s a lot nicer just to manage one day with eight speakers than it is to try and manage two days with 16 speakers, because it doubles all the worry.

Drew: Yes. So what was it that spurred you to start this in the first place? Where did the idea come from?

Alex: So I started... This is where I realized how old I am. So I started uni in 2006, and Joe Leach came in one of our induction days, and gave a talk about what the world of the web is, and what it does, and all this, that, and the other. And a couple of friends of mine were talking to me afterwards, "But I don’t understand what this is or that is." And so the idea from there also came about that we were learning command line Java.

Drew: Okay. My condolences.

Alex: Yes. And the university I was at was there going, "You need to learn this module, because if we go to this job site and put in this web development without Java, the results disappear. You get a third of the results." So a lot of it was trying to show my fellow students that what people are doing in the web isn’t necessarily what’s being taught, and showing that actually the web technologies that are out there aren’t necessarily what we’re learning in a classroom or in a lecture. And also trying to get rid of the idea of buzzwords as well. So it started off as an event to get professionals in to speak to students, and then go, "As we’re in Bristol, if you’re in the area and want to come to the event, come to the event." So that’s how it started, and it’s just grown from there as I went through uni.

Drew: That’s amazing. When I think about everything that’s involved in running an event like a conference, it must be like finding venues, finding speakers, finding an audience, it’s overwhelming. As someone personally, I’ve had a bit of a long-running community side project, I’m thinking of the website I used to run, 24 ways, and I just know that organizing something like that year after year, it really takes it out of you. I can’t imagine if it was then a physical event, like a web conference. So what is it that keeps you coming back year after year and doing it again to yourself?

Alex: It might sound really bad, but it’s effectively... One of the reasons I keep doing it is because it gives me a chance to go to a conference, with life and family and everything else. You don’t get as much time as you think you might to go to all these things and fly around and go to events. So it’s a chance for me to see people I’ve heard of talking about something they love doing, and gets me out of the house for at least a couple of days. So it was there, kept going because I want to do an event, and it just benefits me that I don’t have to pay for a ticket, as it were. And then I just have to stand up in front of people and make a fool of myself, very briefly.

Drew: But you get to put on your dream event as much as possible. You can tailor it to you.

Alex: Yes, exactly. And it’s not an event we take far too seriously. And I’ve been fortunate enough with venues that we’ve always, aside from a small test of another venue, we’ve always been at the same venue. And it’s in a really good location in the center of Bristol. And it just means that if people are coming in, it’s quite easy for them to go, "That’s where the venue is, and there are 20 hotels around it. So I can come into Bristol, I can stay in Bristol, and walk to the event, and it’s all good."

Drew: So talking about practicalities then, when you’re thinking about organizing another addition of this, you say you’ve got your preferred venue. So what comes first? Finding a date? Or...

Alex: Yes. So over 14 events, we’ve... It used to be that it was organized early September, because the unis would start then, and it would then mean that I could speak to the union and go, "This is when the event is." It would mean that they can tie it into stuff that they’re doing. And since then, it’s migrated to October, and it’s always been the first Friday in October, except for this year because we’ve had to push it back for other reasons. But we go, "This is the date..." It’s always October now. And then from that, I know the venue’s there, the venue hasn’t gone up in flames, it’s quite established, and it’s... Because it’s at the Watershed, so it’s quite an established venue in Bristol. And so I know that’s sorted, I know roughly when it is, and then it’s just working back from then to make sure that things are launched with enough time to make sales to cover the bills.

Drew: So how do you decide on the lineup? So you’ve got your dates sorted, you’ve got the event booked. How do you decide what’s going to happen on stage on that day?

Alex: So I think I’ve been very fortunate, and I’ve lucked into a lot of it. So I’ve gone, "I really want to see Drew speak," so I’ll invite you along, and you’ll tell me what you’re speaking about. And then I’ll go, "I want to see someone else," and I’ll invite them along. Over the last few years I’ve teamed up with Luke to put the event on. So because of his role, he’s got a lot more contacts that I maybe wouldn’t have come across. And so it’s going, I really like what this person’s tweeting about or blogging about, and I’ve read this article, and they happen to be based in Leeds or Manchester, and I’ll invite them down. And I’ve been really lucky in that, over the years, the theme of the day has echoed through every talk. And I even had, at one point I had Paul Boag speaking, and he panicked a bit, he was like, "But my talk is really similar to the talk that was on now." And it was like, he was speaking to me, there was a talk between the one he was going on about and his, and he was worried that his would basically be sounding the same. And I said to him, "It doesn’t matter. What your talk does will tie everything together at the end of the day." And it worked really well. So I’ve been really lucky, in that there’s been a theme that’s worked with a spattering of other bits and pieces in the middle.

Drew: Yeah. It’s funny how that can happen, because there’s often themes running through the industry at a certain time. Everybody’s thinking about the next ideas, and often they are interconnected, because the web as an industry is moving forward towards the same sort of places. I can remember a similar situation speaking at a conference, where the talk that came directly before mine covered about, I don’t know, about 25% of the same stuff that I was about to go over. And so I had to get on stage and I’d say things like, "I hope you’re seeing a theme here. You’re seeing what we’re trying between us, what we’re trying to say," and make it sound intentional. And of course it wasn’t a problem. It was reinforcing the ideas. It was actually saying, "Here’s the important ideas that we’re all thinking about at the moment."

Alex: Yeah, exactly. And I think it helps attendees as well almost see that these people are up in front of them saying these things, and it’s not just one person saying these things, it’s four or five, and they’re not necessarily saying it in... It’s not a pulled quote that they’re going over and over again. They’re saying it in their way and how it applies to them and what they’re doing.

Drew: Yeah. It reinforces the point and gives different perspectives on it as well at the same time. So at this point, we’ve got a venue, we’ve got a date, you’ve invited some people to speak, they’re working away on their presentations and looking forward to visiting Bristol. How do you go about getting the word out? How do you sell tickets? How do you find an audience and let people know?

Alex: I cross my fingers, and... So I think my biggest thing is I’m not that social, as it were, and what I do is I hope that the speakers who are coming to the event will go, "I’m speaking at this event, here it is." I’ve got an adequate Twitter following for the conference. And what I also do is, before tickets are launched, I’ll say, "Look, register your interest. We’ll tell you as soon as you can get a ticket," and stuff like this. And I’m really thankful that there’s a kind of almost core community around the event that will go, "Yep, I’m coming, I’ve bought my ticket, it’s there, I’ll be there." And slowly but surely word spreads out to different areas of the country as people... Some people would take a chance in it and go, "I had a really great time." And then many years ago, it used to be the thing that people would write up their experiences and do a review, and for a while you could see the referrals coming in through analytics and stuff and going, "Okay." And so it’s grown word of mouth more than, I need to make sure I’m speaking to this publisher or this site or whoever to mention my event.

Drew: Sorry, I’ve noticed that your ticket prices are incredibly low for a full-day conference. So it’s, what, the full price is...

Alex: The full price this year is going to be £100.

Drew: £100. Which is great value. And I guess that enables people to take a bit of a punt on... If it’s not going to cost them too much to get to Bristol, and they’ve heard good things, 100 quid, actually that’s exceptional value.

Alex: Yeah, exactly. The idea is that it... The theory being is that, if you’re missing a day of work and you’re a freelancer, you don’t get paid for that day of work. So the idea being that the whole trip to Bristol, staying in Bristol, coming to the event, shouldn’t cost more than a day of work. And the whole idea of the ticket price is that it covers the event cost. I don’t sit there and go, "I need to charge 250 quid a ticket to make X amount at the end of the event once all the bills are settled." I need to be at zero once all the bills are settled, so that it can keep funding itself every year. And I’ve been unfortunate a few times where it’s lost money, but over 14 events, it’s happened twice. So being able to sit there and go, I know... People will then know and come to expect that the cost of the ticket is reasonable, and I’m not suddenly sitting there going, "Yeah, now I’ve got 100,000 Twitter followers, I’m going to charge this much money because it’ll make it." I’m going to keep doing what I’m doing, because it gives even the smaller freelancers the chance to attend an event that isn’t out of a price range.

Drew: And do you find, as a result, your audience is primarily freelancers and primarily people who are paying their own way for their ticket? Sounds like that’s the sort of...

Alex: I think these days now it’s more of a 50/50 split, because being able to see the way... Because I use Tito for the ticket sales, is that I can see how tickets are ordered. And there are lots of freelance, but then you’ll get an order for five, ten tickets from one company. There are definitely companies out there that are buying tickets for their employees to attend the event, but there are freelancers as well. And it makes quite a nice mix, because we’ve even had partnerships with companies in the past who are recruiting. So there might be freelancers who are like, "I’ve been doing this for a couple of years and it’s all right, but I’ve met these guys at WDC, and I had a chat with them, and they’ve got a job, and I might apply for it." So hopefully the idea [inaudible] the networking side [inaudible] event leads to that, and the split in ticket sales between freelancers and companies and bits and pieces like that spurs that on, I think.

Drew: Yes. And I think it’s in contrast to what we’ve seen from a lot of the... Because going back ten years, there were a lot more conferences, single-day conferences at affordable prices that were going on in the UK. And we had Carsonified back in the day running their events, Future Of... We used to have things from Clearleft, dConstruct, and... What’s the typography one called? Ampersand. And some of those people are still running conferences, Clearleft are still running conferences, but what we’ve seen from them is they’ve gone very upmarket, where a ticket will cost over £1,000 or... And I very much suspect their audience are people who are not paying their own way, that their company has sent them, or it’s a significant business purchase, not an individual thinking, "I’ll just go and learn about this thing." So it’s interesting that most of the UK market of what’s left of conferences has tended to go up higher-end. Is there something about putting conferences on in the UK that makes it really hard, that you’ve got to charge a lot of money? Or... I’m just wondering if you have any insight what goes on there.

Alex: I don’t think so. I think a lot of it is that the more higher-end conferences seem to be in London, and from that, the venue’s going to cost an extortionate amount of money. And then you’ve got to get... Especially depending on who your target is, you’ve got to have the right names of people in the industry at that event, which will then be charging their fee, which will be relevant to their experience, and so on and so forth. Whereas outside of London, a venue hire doesn’t cost a huge amount of money, hotel costs don’t cost a huge amount of money, and everything else. But I think that the target for those upscale events, as you say, is our big organizations who have maybe heard of a keyword that happens to be relevant and gone, "We must put some resource into this, and we’ve got our spending for the year, and if we don’t spend it, we lose it." Drew, you’ll go into that event and you might go, "Oh, great," and then you realize that maybe two or three of the talks are relevant to what you’re doing, and not all of it. And I think that there’s obviously a place for them, but outside of that, the costs of everything are a lot less. And for me, it’s not just about putting on the event, it’s about being able to put on all the bits around it, and make more of a community effort to it, and have a community around the event, than it is to go, "I’ve put on this massive event, and we’ve got eight great speakers, it’s going to cost you two grand for a ticket." But you’ll go to the day, you’ll leave, and that’ll be it, because you’re probably London-based, so you’ve gone home.

Drew: Yeah. Yes. It’s amazing the different feel that a more community-based conference like WDC has, than some of the more upmarket and therefore a little bit more corporate events have. And I think you’re right about... Because you mentioned briefly about the ability to network and things, and if you are a freelancer, a community event like this is a great opportunity to get to meet other people, meet potential customers, but also potential collaborators or contacts. And as a freelancer, it’s always useful to know other people with different specialisms who you might want to bring into a project, and it’s a great opportunity to make those connections and meet people. Once you’re advertising your tickets, they’re on sale, you’ve got your fingers crossed, hoping that people buy tickets, I guess you’ve got quite a lot on the line at that point. You’ve committed to a whole load of costs. How do you cope with that? Does it keep you up at night?

Alex: No, because [inaudible] this year’s a bit different to the norm, because normally... So with an event in October, we launched late spring, so April, May sort of time. And then the first thing... If I’ve got that gap between launching the site for the year and the event, what I’ll do, the first thing that I do is I’ll go, "Let me get in 50 ticket sales." So I’ll do what I’ve called in the past a super early bird ticket. I get those ticket sales in, and I know that I’ve got... I believe normally I’ve got the cost of the venue and half the hotel cost covered at that point. And they’re normally on sale for two weeks or until they sell out. So I sit there and try and make a deal about the fact that there’s only 50 of them, and once and they’re gone. And so once I get that in, it sits away in a pot, and I’ve got a space in my banking that’s for WDC, and every ticket sale money just sits in there until I need to pay the bills. And then what tends to happen after that is you then hit the summer, and everything goes quiet.

Drew: Yep.

Alex: So you get to a point where you’re like, "I’ve got at least this cost covered. I’m only out a little bit of money." And then everyone gets back to work in September and it picks up again. And at that point it’s the general admission tickets for the event. And then you get to the point... I think normally by then, I know I’ve got the base costs covered, because of the way I cover speaker travel and stuff, I know all I’ve got to worry about then is their travel. And some people will be Bristol-based anyway. Some people will... I’ve had it before where some people have driven in with friends and everything else. So actually, you’re not sat there going, "Oh no, I’m going to be... I’ve got all this expense to cover that I haven’t covered yet." So what I’ve got to cover now is very small, and every time a ticket sale comes in, it gets closer and closer to zero.

Drew: Yep. So those super early bird, which presumably has snapped up by your core regulars who are going to come back every year, because they just know it’s great and they don’t need to know anything about the lineup, they just know they’re coming.

Alex: Yeah. Yes. I did once do blind birds, where I went, "This is the date of the event. And over the next couple of months, we’ll sort out all the speakers and stuff." And they did all right. It wasn’t an instant success, but I hope that as the track record grows, more and more people go, "If he does a blind bird and it’s 50 quid, I’ll do that." So...

Drew: It’s worth a gamble because the odds are pretty good.

Alex: Yeah, exactly. Yeah.

Drew: Yeah. And that then helps your cashflow to make sure that any initial expenses are coverable. Yes. That’s smart. The conference industry as it is has taken a pretty big hit over the last few years with the pandemic and things. I’m guessing you just didn’t run WDC through the pandemic, because you couldn’t.

Alex: Yeah, so we got... It was really unfortunate. I’m just going to bring up the... Because I’m slowly filling out the site. So we didn’t run in 2019, 2020, 2021. 20 19 was because of family commitments and my kids being very little, and they take up an extraordinary amount of time. And then what I was trying to do through the pandemic and stuff like that was at least have something there that people could watch and get to. And we’d done a slot on a conference where we had... It was like a Q&A session, but a very tongue in cheek Q&A session. And I was trying to plan to do something like that, to have people keep engaged, but that again didn’t happen. People got busy. So it took a break just before that, and I was like, "I’m getting ready for 2020." [inaudible] probably sat there in January going, "The ideas are forming..." [inaudible] And then everything went all to hell. So we took a break. And then, as I say, we came back last year once we were past it all. And as I say, we’re back now, and this is what we’re doing, and trying to now essentially build up a bit more momentum to be like, "So we’re back this year, we’re going to be back next, year after that, we’re going to keep going, keep people interested in those things happening."

Drew: And did you find that the audience returned as you’d expected last year? Or was it a little bit slower?

Alex: It was a little bit slower. I think partly that was down to, it was a two-day event. And I spoke to various people about the fact that two days for them, especially with everything else that was going on, is that... It’s just a bit too much time to take off. Which I completely understood and would never... If someone’s got to do something else than attend my conference, then let them do it. I’m not going to hold it against them. And that was part of the reason, to go back to one, is one, it’s always on a Friday. The worst you’ve got to do is travel... If you are an employee, you can travel to Bristol the Thursday evening after the event... Not after the event, sorry. After work. That’s the one. And then you’re traveling home again on a Saturday. So you’re not there panicking that you’ve got to get up after the event, get back on a train to get to an office. No, you’ve got the Saturday, so you can... I’ve known people who’ve gone, "Well, I’m going to spend the day in Bristol."

Drew: The important point then as well is, if you are a freelancer deep in the weeds of a project, taking one Friday off to do some personal development stuff and go to WDC is... No client’s going to bat an eyelid, really.

Alex: Yeah [inaudible].

Drew: I’m not around this Friday, back on Monday and... Fine.

Alex: Yeah. And the worst I seem to have had on a Friday is, "Could you look at this on Monday for me?" Yeah, of course. That’s Monday. That’s after the weekend. So I’ve had it a couple of times where there’s been talks going on and I’m like, "Okay, phone down, respond to the email. Okay, done." And then there’s nothing.

Drew: Yeah. I feel as we dig into the weeds of what’s involved in organizing a conference, there’s a lot going on. It’s a big endeavor, right?

Alex: Yeah. There’s always little things you forget about. And as you’ve covered venue... Date, venue, speakers, and hotels, probably the four big things you’ve got to get sorted out. Then you’ve got to worry about the schedule on the day. The schedule on the day, there’s always one you forget about, because they’re all there, and you sit and go, "When are they speaking?" Or... And the big one as well is that people always tweet or contact you to go, "What is the schedule? What are they talking about?" You’re like, "Okay, yeah, I’ve got to put those details together for them." Because [inaudible] it works, especially for bigger organizations, is that they want to be able to see what these people are talking about to make sure it’s relevant if they’re sending employees. And then you’ve got lanyards, stickers or... I do pin badges, I’ve got a little set of pin badges that I’ve done. Then you’ve got to worry about volunteers. And volunteers I always forget about, and they’re amazing. They give up their time to sit in the Watershed, and they sit out the front and check people into the event.

Drew: Do registration and... [inaudible]

Alex: While I run around crazily going... I’ve got to put banners up here, so I’ve got to make sure I’ve got banners, and I’ve got to make sure that this person’s set up and ready to speak, and... Thankfully the tech team at the Watershed are amazing. So I come in and they go, "Yeah, okay. We’re doing this again. Okay." And they get everyone set up, it’s all working, and they’re all mic’d up and all ready to go. And volunteers just sit there and go, "Right, they’re in, they’re in." And you check on them a couple of times, and they’re like, "Yep, I’ve had these people." What other small details are there? Oh, getting myself to the event. So I live just on the outskirts of Bristol, so what I’ve done in the past is I’ve driven in the morning to get to the venue for 8:00 with a... And I’ve got it in the garage now, it’s a conference box, which has various bits of...

Drew: Canned food, firelighters. Emergency flares.

Alex: [inaudible] Hi-vis jackets. It’s got all the bits and pieces that have built up over the years. Because you sit there and go, "I can put an event on for 300 people, and so I want 300 of these things." And then you get 200 people show up. So you have to go, "I’ve got 100..." I’ve got old dot grid notebooks and stuff that are from event many years ago that I’m like, "I’ve got those to put out so people can have them, because I don’t want them in my garage." So what I’m now doing is I’m making sure that I can book a hotel room for myself, to make sure I can get up at 4:00 in the morning, because I can’t sleep anyway, because I’m like, "I’m putting on conference today," and being close to the venue anyway. And... What else? There’s loads of little bits you always forget about every time you put on a thing, you’re like, "I did that last year. Why did I forget this year?" And stuff like that.

Drew: I guess it’s one of the advantages of having a regular venue that you go back to year after year.

Alex: Yes.

Drew: Is that, as you say with the tech team, they know you, they know your event, they know what they’re doing. You don’t have to waste energy thinking about, "Where do we put the registration desks? Where do we do this?" Because you just know. You’ve done it before, you just fall into the pattern, and it takes off a lot of mental load.

Alex: Yeah. Yeah. If it was my first one, I’d be... I wouldn’t sleep for the week before the event, because I’d be like, "Have I got X? Have I got Y? No. Oh, no. What am I going to do?" And then I’ve been really fortunate with, if we’re doing printing of schedules and stuff and name badges, is that I’ve got a printer I can go to the week before and go, "I need this." [inaudible] "Okay, great." And within... In the past, I’ve had a 24-hour notification to go, "It’s been dispatched." You’re like, "This is great." And then I’ve gone, "There was a typo and it’s my fault. I’m really sorry. Can you print these?" So thankfully I’ve now got my wife and a couple of friends who will proofread anything I send that’s going to be printed.

Drew: Yeah. Yes. When you’re used to working digitally, sending stuff to print is terrifying, isn’t it?

Alex: Yeah. I don’t know about you, but it’s the thing I’m always saying to clients is, "You’ve got to remember a website can be changed, as and when you want it to be changed. Can’t do that with a schedule book that you’ve printed out."

Drew: No. And have you ever had any situations like with speakers needing to cancel last minute, or being ill, or anything like that?

Alex: I’ve had an issue with a speaker before where, because of train... We’ve had issues with train strikes and stuff before. I had an issue with a speaker who went to get on a train, to find out that the train was canceled, and they were traveling down late the night before, and they were meant to be on early first thing the following morning. So there was a lot of panic there about what we were going to do, and they made it in the end, and it was just... Essentially, I could probably give a course in crisis management for it. We had... Again, last year, even though I’ve done 14 events, I’ve never spoken at them, because it’s not something I do. And last year we got to a point where I was like, "We’ve got one lightning slot, and the person we wanted to speak at it is unavailable." And I think was 48 hours before that slot was to take place, I was like, "I’ll do it. How bad can it be?" And having spoken to people who’ve never spoken at events before, who’ve done it, and their nerves and stuff like this, I thought I had a really good idea for a talk for 15 minutes. It’s only 15 minutes. And I was there panicking about it, and thankfully we had Gavin Strange on after me. I spotted him walking in the room after I was about seven minutes in. I’m like, "I’ve run out of content, I’ve run out of stuff to say," because I’d panicked my way through it. I was like, "That’s me done." [inaudible] So a lot of it is just making sure... Knowing enough in advance when things are happening, I think. We’ve been caught out with train strikes, I think at least twice now. And that’s always the thing... If it’s something we can control, so if it’s a speaker who’s sat there [inaudible] "I’m really sorry, I can’t do it," we can... We’ve done it before where we’ve had a slightly extended break, or moved things around ever so slightly because they’ve been unable to attend. But something that we can’t control is industrial action and bits and pieces like that. Thankfully they published it well in advance [inaudible] like, "Is this going to impact travel?" And it did last year, which was a bit annoying. And had it been a one-day event, it wouldn’t have happened.

Drew: Yeah. What seems to be clear is that organizing something like WDC, you probably can’t do it as a business. It has to be something you do out of passion and you do because of the love for it, because it’s so much work. And to be able to keep it to being so accessible in terms of cost and things, as a business move, it doesn’t make any sense, right?

Alex: No. If I wanted to do it as a business, I’d have to charge a lot more for a ticket, and I couldn’t do one event a year. I’d have to explore options and go down those very narrow lanes of content to make it a business. And at that point I’m like, "Do I really want to organize 10 events plus a year to run a business?2 And the answer’s no.

Drew: Yeah. It’s a complete change of business, isn’t it?

Alex: Yeah, exactly.

Drew: No longer a software engineer, an event organizer. What would you say to somebody who is thinking about setting something like WDC up, who wanted to do that themselves, a grass root, accessible event, other than don’t do it in Bristol in October? Would you have any advice to give to them?

Alex: So I’ve spoken to people about it before, and the advice I can give is, if you’ve got the community locally... I’ve been very fortunate with the web scene in Bristol, is that if there’s the community locally and you start off with meetups and networking locally, then if you then put on an event that’s aimed at that community, the chances are that it’ll start in Bristol... Not in Bristol, sorry. It’ll start in your location of choice that isn’t Bristol. And what will happen is that the people who are local will obviously have a network that’s ever so slightly further apart, and it’ll grow out that way. And if you get the right people to speak at that event as well, they will tweet about it and everything else. And that’s the way WDC has grown, is through, as I say, word of mouth. I got extremely lucky in that I could work with the uni that I was at to put on the first three events. And so if there’s a partner who’s willing to help you as well [inaudible] "I’ve got an idea for this, but what I need is just someone to help me cover the cost," you can grow it that way as well. So if you know that there’s a community in your area, and it’s... The other thing that I think is very important is good travel links for people traveling in. So obviously Bristol’s quite a good location, because we can get trains from the Southwest, from the East, from the North, all relatively easily. The travel links are really good for Bristol. So if you’ve got that infrastructure in place as well, it means that people coming from outside of your area, can get to it, stay there, and get home again without fuss. And it’s making sure that you’re getting people talking about things that people want to listen to. So it can be about following trends, but what we’ve done with our lightning talks is that it’s a 15-minute slot that you don’t have to talk about web stuff. You can talk about anything. So we’ve had people talking about building desks and furniture and stuff like that, which is great to show that people in the industry do other things. It’s not that you sit in front of a computer all day. Find the community to build the event in the middle of, and let it... I’ve been very fortunate [inaudible] word of mouth, it’ll grow, because whilst your network could be 50 people, their network is then another 50 people for each one of them, and it grows that way.

Drew: Fantastic. I’ve been learning all about what it takes to put on an independent web conference. What have you been learning about lately, Alex?

Alex: So I’ve been learning about Eleventy. Because I’m a big WordPress person. I’ve been doing WordPress for 15 years professionally. And the conference site has been a mismatch of different things over the years. So I’ve been learning Eleventy to pull it all together in one platform. Because obviously it’s a conference, so nothing changes dynamically a lot. So what I’m currently doing is filling in the back catalog of event sites, so that people can see what... Because we’ve tried fun themes and stuff with them over the years, is that I’m using Eleventy to bring all that in and going, "How do I do this with this thing?" And "Why does it error when I do this thing this way, and do something similar but not quite the same this way?"

Drew: It’s always very challenging and a little bit humbling, isn’t it? When you pick up a different bit of software, where you know how to do the task with something else you’re familiar with, and you pick up something different, and suddenly you feel like an idiot.

Alex: Yes.

Drew: But also, it’s so fulfilling, isn’t it? Once you figure out how to do something and just... That sort of dopamine hit you get from achieving things is amazing.

Alex: Yeah. For me it’s like, "But the documentation says this." And what’s getting in my way of using documentation properly is that I think I can do it another way, because in the other systems I use and the frameworks I use, this is how I do it. [inaudible] read what we’re saying. You’re like, "Fine. I surrender."

Drew: I surrender. I will do what the documentation says. If you, dear listener, would like to hear more from Alex, you can find his personal site at alexolder.com, and of course, WebDevConf returns to Bristol on the 20th of October this year. You can find all about that and get your tickets at webdevconf.com. Thanks for joining us today, Alex. Did you have any parting words?

Alex: No, but please do say hello, because I don’t use social stuff very much because I’m always busy. But do say hello if you ever see me anywhere.

Sustainable Web Development Strategies Within An Organization

Sustainability is rightly becoming more widely discussed within the web development industry, just as it is an increasing concern in the wider public consciousness. Many countries around the world have committed to ambitious climate goals, although many have some way to go if they are to meet their targets.

All industries have a part to play, and that includes web design and development. The internet accounts for an estimated 3–4% of global emissions — equivalent to some countries. That means we, as tech workers, are in a position to make choices that contribute to reducing the environmental impact of our industry. Not only that, but as a well-connected industry, one that builds digital products often used by thousands or millions of people, we are also relatively well-positioned to influence the behavior of others.

In this article, we’ll explore some of the ways that we as individuals can use our skills to have a positive environmental impact within a digital organization.

Presenting The Case For Sustainability

One of the first hurdles to implementing sustainable practices within an organization (or on a project) is convincing stakeholders that it is worth the investment. Any change of practice, however small, will probably require some time investment by employees. Being able to present a business case, and demonstrate that the benefits outweigh the costs, will help justify focusing resources in the area of sustainability.

Cost-Effectiveness

It would be great to think that for every company, the idea of building a better world trumps financial concerns. Unfortunately, with some exceptions, that’s generally not the case. But there are plenty of actions we can take that reduce our environmental impact and reduce costs (or increase revenue) at the same time.

For example, changing our database architecture to be more efficient could save on server costs. Making performance improvements to a client’s site could result in happier clients who send more business our way. Identifying where sustainability and cost savings overlap is a good place to start.

Regulation

Despite financial impact being a fairly obvious incentive, it’s not the only one, and perhaps not even the most significant. In his recent Smashing Conference talk, green software expert Asim Hussain mentioned that the biggest shift he is seeing is as a result of regulation — or the threat of regulation.

With many countries publicly committed to Net Zero goals, it is increasingly likely that companies will need to submit to regulation of their carbon emissions. The UK’s commitment is enshrined into law, with carbon budgets set over many years. Many companies are already taking the long view and looking to get ahead of the competition by reducing their emissions early.

Being able to demonstrate as a company that you are committed to sustainability can open up a greater number of opportunities. Organizations working with the UK government to build new digital services, for example, are required to meet standards defined in their Greening Government ICT and Digital Services Strategy.

Accreditation

Companies that can demonstrate their environmental credentials may be eligible for certification, such as ISO14001 standard in the UK. In the case of Ada Mode, the company I work for, this has has directly contributed to winning us more work, and has enabled us to partner with much larger organizations.

Businesses that achieve BCorp status can benefit (according to the website) from “committed and motivated employees, increased customer loyalty, higher levels of innovation, and market leadership”.

Certainly organizations positioning themselves as environmentally conscious increase their chances of attracting sustainability-minded candidates for recruitment, as more and more people seek meaningful work.

It’s All In The Branding

Another great bit of advice from Asim’s talk from Smashing Conference was on branding. The “Eco” movement has long been associated with being somewhat spartan, taking away something, using or consuming less. Rather than giving our users a reduced experience, reducing the environmental impact of our digital products has the opportunity to deliver our users more. Asim talked about Performance Mode in Microsoft Edge: switching on Performance Mode means users get a faster website, while also saving resources. “Performance Mode” sounds a lot more appealing than “Eco Mode”, which sounds like something is being taken away.

The Bigger Picture

When presenting the case for investing time in sustainability efforts in an organization, it can be helpful to explain the relevance of small actions on a bigger scale. For example, Smashing’s editor, Vitaly Friedman, makes the case for reducing the size and quality of images on a site by explaining the overall cost and CO2 savings when taking into account page views over an entire year.

On the Fact Sheets page, we can save approx. 85% of images’ file sizes without a noticeable loss of image quality. With approx. 1,300,000 annual page views…this makes for 5.2 Terabyte of wasted traffic.
The difference is approx. EUR 1000–1650 in costs (on one single page!). Notably, this makes for 17.28 tons of CO2, which requires 925 trees to be planted, and that’s enough to drive an electric car for 295,000km — annually.
Get Organized

Affecting change at an organizational level is nearly always easier when you build consensus.

Forming A Team

Forming a green team within your organization enables you to support each other to achieve climate goals, and identify new opportunities. ClimateAction.tech has some resources on starting a green team at your place of work.

If your organization is small, or there is a lack of interest, then finding a supportive community outside of work (such as ClimateAction.tech) can help you stay motivated, and lend their advice. It’s also a great idea to connect with teams working on sustainability in other businesses.

Planning

Once you have a team, you’ll be in a good position to plan your actions. It can be hard to know where to focus your efforts first. One way we could do this is by drawing a diagram and sorting potential actions according to their impact and effort.

For example, switching to a green hosting provider could be a small-to-medium effort, but result in a high impact. Re-writing your web app to use a more lightweight JS framework could be extremely high effort for relatively low impact.

The goal is to identify the areas where your efforts would be best focused. Low-effort/high-impact actions are easy wins, and definitely worth prioritizing. Achieving a few aims early on is great for moral, and helps keep the momentum going. High-effort/high-impact actions are worth considering as part of your long-term strategy, even if you can’t get to them right away. Low-effort/low-impact tasks might also be worth doing, as they won’t take up too much time and effort. High effort/low impact actions are generally to be avoided.

This isn’t the only way to prioritize, however. Other factors to consider include workload, resources (including financial), and the availability of team members. For example, if your development team are particularly stretched thin, it may be more prudent to focus on goals within the areas of design or project management, or prioritize actions that can be easily integrated with the development workflow in a current project.

It’s not always the case that every sustainability effort needs to be meticulously planned and scheduled. Jamie Thompson from intelligent energy platform Kaluza explained in a recent talk how a developer spent just 30 minutes of spare time removing database logs, resulting in a large reduction in CO2 emissions — enough to offset Jamie’s train journey to the event.

Watch the video of Jamie’s talk from Green Tech South West.

Measuring The Impact

Measuring the impact of your sustainability efforts is a thorny subject, and depends on what exactly you want to measure. To get some idea of the impact of changes to our websites, we can use tools such as Website Carbon Calculator, EcoPing, and Beacon. These tools are especially helpful in making the impact more tangible, by comparing the amount of CO2 emitted to common activities such as traveling by car, boiling the kettle, or watching a video.

Where sustainability goals align with cost-saving (such as reducing server load), we may be able to measure the impact by the financial savings we’re making. But we should be careful not to conflate the two goals.

Some Areas To Consider

If you’re not sure where to start when it comes to making your digital organization more sustainable, here are a few areas to think about.

Green Your Website

There are many ways we can reduce the environmental impact of the websites and digital products we build, from reducing and optimizing our images, to minimizing the amount to data we transfer, to implementing a low-energy color scheme. Tom Greenwood’s book, Sustainable Web Design is packed with advice for building low-carbon websites.

When the architectural website Dezeen discovered how polluting their website was, they took steps to massively reduce its carbon footprint, resulting in some huge savings — according to their measurements, equivalent to the carbon sequestered by 96,600 mature trees.

Green Hosting

Our choice of web host can have a big impact on our organization’s carbon emissions. Consider switching to a host that uses renewable energy. The Green Web Foundation has a directory.

Switch your analytics

Do you really need Google Analytics on every site you build? How about switching to a lower-carbon alternative like Fathom or Cabin instead. As a bonus, you might not need that cookie banner either.

Developer Toolchain

Eric Bailey writes in this article for Thoughtbot:

“If I was a better programmer, I’d write a script that shows you the cumulative CO₂ you’ve generated every time you type npm install.”

Clean up your dependencies, and the remove ones you no longer need, especially if you’re working on a project or package that will be installed by a lot of developers. Consider whether a static site might serve your needs better than a bloated WordPress project in some instances. (Eric’s article also includes a bunch of other great tips for building more sustainably.)

Hardware And E-Waste

Several tonnes of carbon go into producing our MacBooks, PCs, tablets and mobile devices, even before we start using them. Do we really need to upgrade our devices as regularly as we do? We must also consider their disposal, which also produces generates carbon emissions and produces harmful waste. It might be possible to repair the device or, if we need to upgrade, to sell or donate the old ones to someone who needs them, extending their useful life.

Gerry McGovern has written and spoken extensively about the problem of e-waste, including his book, World Wide Waste.

Electricity use

It’s probably fairly obvious, but reducing our electricity consumption by switching off or powering devices when we don’t need them, and switching to a green electricity supplier could make a big difference.

Travel

Does your team regularly drive or fly for work? It might be helpful to set some organization-level targets for reducing carbon-intensive travel, and looking for sustainable alternatives where possible. Driving and flying are among the most polluting activities an individual can engage in.

Larger Organizations

If you work for a big corporation, the battle to get climate action on the agenda may be uphill — but, on the flip-side, your efforts could have a far more wide-ranging impact. Small changes to improve the carbon footprint of a site can have a big impact when that site is used my millions of people. And in an organization of thousands, corporate policies on sustainable travel and electricity use can save a lot of carbon emissions.

Many of the big tech companies have the potential to use their lobbying power for the greater good. As tech workers, we can help push it up the agenda. Check out Climate Voice for some of the ways tech workers are attempting to use their influence.

Spread The Word

A common argument people make against action on climate change is that individual actions don’t make a difference. There’s a great podcast episode in the How To Save a Planet series called Is Your Carbon Footprint BS? which confronts exactly this dilemma. You could argue that when taken individually our actions are of little consequence. But all of our actions have the potential to spark action in others, and ripple outwards. Dr. Anthony Leiserowitz, who runs the Yale Center for Climate Change Communication is quoted in the episode, saying:

“One of the single most important things that anyone, anyone can do. When people say, ‘What can I do about climate change?’ My answer first and foremost is talk about it.”

By taking action at an organizational level, you’ve already extended your sphere of influence beyond just yourself. Encourage the people working at your company to be vocal about your climate commitments. We have the power to inspire action in others.

Inclusivity, Accessibility And Climate Justice

However we choose to take action on climate change and sustainability, it’s imperative to exclude no one. We should make sure our actions don’t overtly or covertly place undue burdens on already-marginalized people, including those with disabilities, people of color, those living in developing countries, people with below-average incomes, or LGBTQ+ people. Climate change is already exacerbating inequalities, with the people causing the least pollution the ones at the most risk from its effects. We must ensure that whatever climate action we take, we’re making fair and equitable decisions that include everyone.

Resources

  • Jon Gibbins founder and director of As It Should Be, a UK-based agency helping digital teams design and build accessible and sustainable products and services, recently delivered a talk about accessibility and sustainability. You can watch his talk, Leave No One Behind, on the Green Tech South West website.
  • The Environment Variables podcast from the Green Software Foundation has an episode on Accessibility and Sustainability.
  • Read more about climate justice in this article from Carbon Brief.

Jobs For Designers And Developers Affected By The War In Ukraine 🇺🇦

In these difficult times, We all are Ukraine. If due to the ongoing war in Ukraine, you need a design or tech job immediately or have friends who are looking for a job, we came across some fantastic initiatives that connect designers and developers from Ukraine with potential employers.

The options below are just a few of the ones that we’ve stumbled upon, and there are surely plenty of other opportunities — these are just the ones submitted by our community. Also, if you’re an employer and you need help on a project or are looking to fill a full-time position — remote or onsite — you might find just the right person for the role on one of these platforms, too.

Job Opportunities
  • UA Talents
    On UA Talents, companies from all over Europe can advertise their job openings to people from Ukraine who have lost their employment due to the war. If you’re looking for a job, you can fill out a questionnaire and UA Talents will select vacancies that match your request. Employers can then contact you. Alternatively, you can also choose a vacancy from the database.
  • Designers United for Ukraine
    Designers United for Ukraine is continually searching for work opportunities that can be fulfilled remotely from Ukraine or onsite in locations around the world, with a particular lookout for connections that include visa sponsorship, travel, and accommodations. If you are a designer who has been impacted by the war, you can add your details to the list, so that hiring managers can connect with you. Organizations with open roles for designers can post their open positions, too.
  • Create with Ukraine
    Brands and startups can upload a creative brief, and Create with Ukraine will recommend creatives whose skills match the requirements. To start receiving work, job seekers can set up a profile with their area of expertise and work samples. After the registration, the user will be instantly ready to start receiving creative work.
  • Ukraine Jobs
    Ukraine Jobs aims at bringing refugees and Austrian employers together. The platform has the purpose of instantly helping job seekers with their demand as well as supporting integration into the Austrian labor market.
  • Creative Ukraine Program
    The job board lists job openings in Slovakia as well as remote positions.
  • Fuzzboard Ukraine
    Fuzzboard Ukraine provides a list of job openings in companies willing to sponsor migrants coming to the European Union. It covers positions for development, design, marketing, product management, business development, and more.
  • Hire for Ukraine
    Hire for Ukraine is not only for tech-related jobs but also for professionals from other fields. Professionals can list their profiles so that hiring managers and recruiters can get in touch with them directly.
  • Workeer
    Workeer is the biggest resource for job postings in Germany that are aimed at refugees. It lists jobs from different industries, not only tech. People looking for a job can register to be contacted by employers or browse job postings.

Also, if you’d like to write an article or case study of a front-end/UX project, please don’t hesitate to get in touch with us — we pay, too. We also have a job board for designers and developers.

Further Help & Support
  • Artists for Ukraine
    Artists for Ukraine aims to provide artists who had to leave Ukraine with technical equipment to get back to work. If you have any spare equipment you want to donate or if you need equipment, you can reach out to the platform and they will establish the connection between you both.
  • Ukraine Advice Project UK
    A group of volunteer legal professionals with immigration and asylum expertise is providing a free service to connect Ukrainian citizens and others fleeing Ukraine with free legal advice on UK immigration, visas, and asylum from qualified and regulated lawyers.
  • Webflow Refugee Relief Support
    Founded by refugees, the Webflow refugee relief support is calling on members of the community to join them in helping fund relief efforts for millions of refugees around the world. The team has selected five organizations aiding refugees from Ukraine, Afghanistan, Syria, and Venezuela to support with donations, which Webflow will match 4:1.

Have you heard of other websites that provide support or jobs for people affected by the war? Please post them in the comments below to spread the word. Thank you!

Advent Calendars For Web Designers And Developers (December 2021 Edition)

Once again, the web community has been busy with creating some fantastic advent calendars this year. As you’ll see, each and every one of these calendars are sure to cater for a daily dose of web design and development goodness with stellar articles, inspiring experiments, and even puzzles to solve.

It doesn’t really matter if you’re a front-end dev, UX designer or content strategist, we’re certain you’ll find at least something to inspire you for the upcoming year. Use this month of December as a time to slow down, and your time to reflect and plan ahead — you won’t regret it.

Advent of JavaScript

If you sign up to the Advent of JavaScript, you’ll be getting an email every day that outlined a JavaScript challenge. Each of the given challenges include all of the HTML and CSS you need to get started, allowing you to focus on the JavaScript. You’ll also receive a brief on how to get started, ways to push yourself, and steps to help you get started. You can get the challenges for free (or pay for the solutions).

Advent of CSS

For folks who’re more into CSS, there’s the Advent of CSS where you can sign up for a daily email outlining a CSS challenge that includes all the assets you need to get started — including a Figma design file. (If you don’t have a Figma account, don’t worry, it’s free.) Before accepting this challenge, you really should know basic HTML and CSS.

JVM Programming Advent Calendar

The Java Advent 2021 is here! To make the advent season even sweeter for JVM enthusiasts, there will be a new article about JVM-related topic everyday. The project started in 2012 with the idea of providing technical content during the Christmas Advent period, so keep looking for nice things under the Java Christmas tree! 🎄

Advent of Code

If you prefer a puzzle over an article, take a look at Advent of Code. Created by Eric Wastl, this is an advent calendar of small programming puzzles for a variety of skill sets and skill levels that can be solved in any programming language you like. You don’t need a computer science background to participate — just a little programming knowledge and some problem solving skills will get you pretty far. Go ahead and give it a go!

Perl 6/Raku Advent Calendar

Back in October of 2019, “Perl 6” was renamed to “Raku”. It’s the 6th year since (what was then called) Perl 6 was released, and the 13th year in a row for this Raku Advent calendar. Stay tuned for lots of articles on metaprogramming, applications, useful Raku modules, programming techniques, guides on how to work with Raku inside containers, and even how to migrate from good ol’ Perl.

24 Pull Requests

24 Pull Requests is a yearly initiative to encourage contributors around the world to send 24 pull requests between December 1st and December 24th. The project is available in twenty languages, and encourages all kinds of contributions to open-source projects — including non-pull-request contributions. There’s a new contribution form on the site that allows you to record the contributions you’ve made each day that wouldn’t usually make sense as a pull request. Join in!

HTMHell Advent Calendar

If you’re already familiar with the HTMHell website, then you can guess how interesting its advent calendar is going to get! Take a peek behind each door of the HTMHell calendar where you’ll find an article, talk or tool that focuses on HTML. To be fair, HTMHell isn’t just about bad practices — Manuel also shares good practices and useful HTML tips and tricks. 🔥

PerfPlanet Calendar

An advent calendar that has been publishing since 2009 is back again. Good ol’ PerfPlanet is back for another season with all things speed and web performance. Anyone is welcome to contribute to the calendar, so do feel free to reach out with a topic or tool you’re passionate about, or a technique you’d like to teach and tell the web performance community about.

C# Advent Calendar

It’s time for the fifth annual C# advent calendar that will feature two pieces of content every day. Anyone can contribute by sharing their blog posts, videos, articles or podcast episodes dedicated to C# development. In case all of the spots are already claimed, you can always sign up to be a substitute author. Rock on! 🎸

Inclusive Design 24

The good folks at Inclusive Design 24 are sharing their favorite talks from previous years of the good ol’ #id24 online-only conferences while counting down the days until the New Year. All videos have even been manually re-captioned, just so they’re all at their best.

Lean UXMas

Lean UXMas has been publishing each advent since 2014 and is a collection of the most popular articles from this year’s Agile and Lean UX latest news. If you find yourself impatiently waiting for the next article to be posted, you can always check out the previous advent calendars smashing the year in the base URL, or simply search for them below the website’s header.

Code Security Advent Calendar

If you’re up for a challenge that involves spotting security vulnerabilities, then the Code Security Advent Calendar is just the right one for you. Every day, there will be a code security puzzle and/or riddle announced on Twitter to which you’re welcome to join and share with your friends to discuss solutions together. The most active players with the best solutions will be contacted to receive a cool swag pack. 🎁

Advent of Cyber

Security can be a daunting field. With Advent of Cyber, you can get started with Cyber Security by learning the basics and completing a new, beginner friendly security exercise every day. For each task you get correct, you get a raffle ticket and on the 26th December, meaning the more questions you answer, the more chance you have of winning. Every day you complete a challenge, you get entered into another prize draw for the chance to win a mini-prize. So, what are you waiting for?

24 Days In December

“PHP is not just a language. PHP is a group of people, a community of developers who build things for the web. The PHPamily spans the globe, and while we might not always agree or get along, we have one thing in common, we’re passionate about what we do.” Jonathan Bossenger hits the nail right on the head as he welcomes everyone to participate in the 6th edition of 24 Days in December. We’re all look forward to hearing your personal journey and stories with PHP! 🌈

Umbraco Christmas Calendar

It’s the 10th year of 24 Days In Umbraco and it’s time to learn more about Umbraco (otherwise known as the ‘Friendly CMS’). If you’re interested in it but not sure where to start, you can always check out the articles by tag(s) and find the answers to your questions. The calendar was first started back in 2012 so there’s plenty of content to sift through.

Festive Tech Calendar 2021

With over 2K subscribers on YouTube, the Festive Tech Calendar is back at it again this year with videos from different communities and people around the globe. As you’ll see, you’ll quickly be able to find an entire collection of videos from all of the previous years, and topics as well as the diversity of speakers both don’t fall short indeed. By the communities, for the communities indeed.

SysAdvent

SysAdvent is back this year! 🙌 With the goals of sharing, openness and mentoring, you’re in for some great articles about systems administration topics written by fellow sysadmins. Tune in each day for an article that explores the wide range of topics in system administration.

IT Security Advent Calendar

“Don't store sensitive data in the cloud; keep it entirely disconnected from the web.” Yup, that’s the credo delivered in the first advent door of the good ol’ IT Security Advent Calendar this year. Counting down to Christmas, this calendar is dedicated to sharing a new tip for protecting your devices, networks, and data each day.

Bekk Christmas

This year’s Bekk Christmas features opinion pieces, tutorials, podcasts, deep dives and lots of other formats. Pick the ones that seem interesting to you, and consume them whenever you like. It’s worth digging through the archives (see e.g. 2020) — there’s a golden gem hidden in each one of them!



It’s nice to find some calendars in languages other than English, too! Here are a few we stumbled upon:

24 Jours De Web (French)

24 Jours De Web is a lovely French calendar which first appeared back in 2012, and has been continuing the lovely tradition of online advent calendars ever since. 24 authors come together each year and publish an article on UX, accessibility, privacy, and other topics related to the good ol’ web.

SELFHTML Adventskalender (German)

This year’s SELFHTML Adventskalender is dedicated to accessibility — a topic that concerns everyone. Why? Because accessibility is good for all of us. Accessible websites are simply better websites. At the end of the day, everyone in the world hits a large key faster and more reliably than a small key. To all the German-speaking developers out there, you’ll understand why it’s important to include accessibility as much as possible. Also, make sure to bookmark the SELFHTML wiki so you can have the latest documentations and tutorials at hand.

WEBアクセシビリティ Advent Calendar (Japanese)

This Japanese advent calendar has been running since 2013 and is moderated by @hokaccha. Its focus lies on web accessibility, with a new author exploring a topic each day — from web accessibility to all the different types of programming languages you may want to explore for your projects. Once logged in, you can save a spot on the calendar and have your article or work published on that particular day.

Kodekalender (Norwegian)

Knowit is one of the Nordic region's leading consulting companies. They have once again brought their Norwegian calendar to life, and it is just the kind of holiday calendar for those of you who love programming. Behind each hatch hides a task you have to answer in the form of a simple text string or a number. The hatches vary in degree of difficulty and design, but common to all is that they are best suited for solving with code. Solve as many slots as possible to increase your chances of winning! Good luck! 🙌


Do you happen to know any other advent calendars that have been created in languages other than in English? Please do feel free to reach out to me on Twitter and I’ll be sure to add them to this list.

Oldies But Goodies

Christmas Experiments (2018)

Christmas Experiments started back in 2012, with the goal to deliver great experiments and highlight top web creative as well as newcomers. It was a pretty cool WebGL advent calendar that featured a daily new experiment that was quite obviously made with love by digital artists. Unfortunately, it did not continue after the 2018 edition.

24 Accessibility (2019)

An advent calendar we surely miss is the 24 Accessibility. The site hasn’t had a new article since 2019, but still offers a good resource of articles on all subjects related to digital accessibility. Whether you are new to accessibility or a veteran, a developer, designer, user experience professional, quality assurance analyst or project manager, you’ll find an article of interest during the run of the series.

It’s A Shape Christmas (2019)

It’s A Shape Christmas is a digital calendar that counts down to Christmas and reveals a bespoke illustration each day themed around four different shapes (Square, Triangle, Circle and Hexagon) and Christmas. The project was started in 2011 by a UK design agency called Made by Shape. The website still showcases some of the best from the previous seasons. I’m sure you’ll agree: they’re all just too good not to be shared! ✨

24 Ways (2019)

First initiated by Drew McLellan, 24 ways started out as a simple website that published a new tip or trick each day leading readers through December up until Christmas. It launched in 2005 and still has all of the calendars available online. Unfortunately, the last one was published in 2019 and will be taking a well-earned break after that year’s “final countdown”.

Perl Advent (2020)

The Perl Advent started back in 2000 and is perhaps the longest running web advent calendar that many know of. You’ll find insightful articles written by diverse author submissions from all types of Perl programming levels. A different Perl module will be featured each day for the twenty four days of advent, and an extra module on Christmas day. Make sure to go through the previous Perl advent calendars — it’s worth it.

PWAdvent (2020)

PWAdvent is a nice advent calendar for everyone who’s excited about the web platform and Progressive Web Apps, of course. Take a look at all the great stuff the web has to offer in last year’s calendar, in which a new progressive browser feature was introduced every day by Nico Martin himself and others.

A11y Advent Calendar (2020)

Heydon Pickering once said, “Accessibility is not about doing more work but about doing the right work.” Last year, Kitty Giraudel decided to publish an accessibility tip a day in his very own #A11yAdvent. Some of the tips are probably common knowledge for many, yet each of the posts cover so many of the important aspects of accessibility that will still hold true for years to come.

Last But Not Least...

Of course, we wanted to join in the fun ourselves and brought our very own #SmashingAdvent to life! As you already probably know, the Smashing team has been organizing conferences and events since 2012, so there are plenty of gems to shine the spotlight on. Do give @SmashingConf a follow on Twitter where we’ll be sharing our favorite talks and interviews with speakers from all over the globe.

On behalf of the entire Smashing team, we’d like to say thank you to each and every one involved in these projects — we see you! The communities in our web industry wouldn’t be able to learn so much and thrive if it wasn’t for your time, hard work and dedication. We all sincerely and truly appreciate each and every one of you. 🙏

And of course, if there’s a calendar that isn’t mentioned here, please do post it in comments section below.

#4 – Dan Maby on the Importance of the WordPress Community

About this episode.

On the podcast today we have Dan Maby.

Dan has been a user of WordPress for many years. As an agency owner he’s used it to build client websites, but, as is so often the case, he came for the software and got caught up in the community.

Starting out by attending some local WordPress meetups, he engaged with his fellow WordPressers and enjoying the events he was attending. Attendance turned into organising and over time Dan became the lead of four WordPress Meetups spread all over the UK.

Meetups led to an interest in WordCamps, where he again stepped up to take on leadership roles at WordCamp London.

In the podcast today we talk about the importance of the WordPress community, not just to him as an individual, but to the future of the project as a whole. After all, it’s software created by people, and the health of that community will have a direct impact upon the contributions they make.

We recorded this podcast at a time unlike any other. In person events have had to stop; the WordCamps and Meetups have all gone virtual. Perhaps there’s light at the end of that tunnel, but it’s a perfect time to look back and see how the community has adapted to these new circumstances.

We get into whether hybrid WordPress events should be the new norm, what lessons the community can learn from the past year, and what Dan and his colleagues have done to stay connected and part of a vibrant community. They’ve built a platform to enable events and plan on releasing it as a WordPress plugin soon.

We also discuss an event which Dan has been a key player in organising – WordFest Live, a 24-hour online event with a focus upon learning and positive mental health. 

It’s a lovely episode with a member of the community who has been giving back for many, many years.

Useful links.

WordFest Live

Big Orange Heart

WordPress Meetups

WordCamp Central

Transcript
Nathan Wrigley

Welcome to the fourth edition of the Jukebox Podcast from WP Tavern. My name is Nathan Wrigley. Jukebox is a podcast for the WordPress community. Each month, we bring you someone who is part of that community to give you an insight into a topic or person who you might not be familiar with. If you enjoy the podcast, you can subscribe to future episodes by going to wptavern dot com forward slash feed forward slash podcast.

If you’ve got any feedback about the podcast, which could be a suggestion of a potential guest or a subject, then head over to wptavern dot com forward slash contact forward slash jukebox. There’s a contact form there for you to complete, and we’d certainly welcome your input. Thanks in advance. If you reach out.

Okay, so on the podcast today, we have Dan Maby. Dan has been a user of WordPress for many years. As an agency owner, he’s used it to build client websites, but as is often the case, he came for the software and got caught up in the community. Starting out by attending some local WordPress meetups, he engaged with his fellow WordPressers and enjoyed the events he was attending. Attendance turned into organizing, and over time, Dan became the lead for four WordPress meetups spread all over the UK. Meetups led to an interest in WordCamps, where he again stepped up to take on leadership roles at WordCamp London. In the podcast today, we talk about the importance of the WordPress community, not just to him as an individual, but to the future of the project as a whole. After all it’s software created by people, and the health of that community will have a direct impact upon the contributions they make. We recorded this podcast at a time unlike any other. In-person events have had to stop the; WordCamps and meet-ups have all gone virtual. Perhaps there’s a little light at the end of the tunnel, but it’s a perfect time to look back and see how the community has adapted to these new circumstances.

We get into whether hybrid WordPress events should be the new norm. What lessons the community can learn from the past year, and what Dan and his colleagues have done to stay connected and part of a vibrant community. They’ve built a platform to enable events and plan on releasing it as a WordPress plugin soon.

We also discuss an event which Dan has been a key player in organizing, WordFest Live. It’s a 24 hour online event with a focus upon learning and positive mental health. It’s a lovely episode with a member of the community who has been giving back for many, many years.

If any of the points raised here, resonate with you, be sure to head over and find the post at wptavern dot com forward slash podcast, and leave a comment there.

And so without further delay, I bring you Dan Maby.

Am joined on the podcast today by Dan Maby. Hello, Dan.

Dan Maby

Good. Speak to you.

Nathan Wrigley

Yeah, it’s really nice to have you on the podcast today. Dan and I have a long history of chatting with each other, so this may end up being quite informal at times, but nevertheless, we’re going to talk today about the WordPress community and events in general.

To paint some context into that, I wonder Dan, if you wouldn’t mind spending just a couple of moments, introducing yourself and perhaps explain your history. Not just with WordPress, the software, but also your history with WordPress as a community.

Dan Maby

Yeah, absolutely. I guess my journey started 15 years ago with WordPress. Funnily enough, we had obviously the 18th birthday quite recently of WordPress, and I was looking back at my history, trying to figure out what had been doing with it. And I realized that I’d started with version 1.5, which at the time was really quite a major introduction. Lots of features in that 1.5 update that we still recognize today in the platform. And it’s been, an interesting journey with WordPress and the community. One that I’ve absolutely loved over that 15 year journey. But really the journey for me with the community started, I think it was around 2012. I was looking for a way to connect with people that were working with and were interested using WordPress. I was working in London at the time in the UK, looked at a meetup. I came across, there was a WordPress meetup that was being run by Keith Devon at the time, the WordPress London meetup. So I went, I headed over to the meetup, came from my day job at the time, which means I was suited and booted. Wandered into this, a room with a bunch of WordPress developers and users. And felt entirely out of place in that in that first meeting. I was the only person there in a suit. Everybody else was nice and casual, but the welcome that I received in that meetup was second to none. It was really an incredible experience, a first experience of the, the wider WordPress community.

And it was actually at that event that Keith had asked if anybody was looking to get involved and support in the delivery of the event and that having been there literally for my first time, stuck my hand up, and that’s really where it all started. And very quickly moved into a situation where Keith decided to step away from the event to focus on other things, focus on his agency, et cetera. I’ve been running the event ever since. And the WordPress London meetup has been a key aspect to everything that I’ve been doing within the community. It’s been a real pleasure to be able to be a custodian of a that event.

Nathan Wrigley

You have a lot more strings to your bow than just the WordPress London meetup. Do you want to tell us a little bit more about some of the other things that you’re, well, were involved in? We’ll get onto that a little bit later, about the way that things have had to cease, but tell us apart from the WordPress London meetup, tell us about the other things that you were doing on a monthly basis.

Dan Maby

Sure, so, for me the community was really the important bit, the people within the community. I really grew to develop a, a passion for the people that we were connecting with. And from that point from the running of the WPLDN event, I realized that actually there were other areas that were lacking in meetups across the UK. There were plenty of people running, plenty of meetups, and I was really enjoying being part of that kind of organizers community, if you like a meetup organizers community. But as I said, I noticed that there were areas that were lacking events, even in my local area, as well as further a field, I actually got to the point where I was organizing and leading four meetups a month across the UK, which saw me traveling quite substantial miles on a monthly basis, just to enable these communities to grow and develop.

And it was a real pleasure to be able to work with local communities. I always encouraged community members within the local area to come on board as co-hosts and enable them to take the lead and to sow the seed and then move on and help that community thrive. And it was going fantastically well. You know we had, as I say, we have four meetups running across the UK, and then suddenly, obviously we’re thrown into the situation where we couldn’t physically come together in person.

Nathan Wrigley

Before we move on to that, perhaps we could paint a little picture about the importance of WordPress in your life, because it strikes me that many people, they may use WordPress as a piece of software. And that’s the end of it. They have really no understanding that there is a community which can support you in your WordPress knowledge, but also it can be much more than that. And I think it’s fair to say that in your case, many of the people that you’ve met through WordPress have become actual friends who you actually socialize with. Enjoy their company and stray into non WordPress things as well. So I’m just wondering if you could tell us how it has helped you, but perhaps get into the stuff that’s not to do with WordPress. Have you met people that you’ve really jelled with and found camaraderie with.

Dan Maby

I think this is the the beauty of the WordPress community. It’s so much more than just the technology. I found it to be quite a unique community as well, in that the way people are open, the way people will communicate and discuss and talk about topics, which, by all rights where we attended an event together, we’re essentially often competing with one another. I run an agency which focuses on design and development services, and I will go and speak with many other people that also run agencies. And essentially we are competitors, but that level of competition doesn’t really surface too much in the WordPress community. It’s predominantly a community that’s very supportive and people are very open to discussing issues. Myself, I was seeking out connection, I wanted to be around like-minded individuals because I was in a situation where I was very isolated. I was looking for people to connect with that had an understanding of what I was experiencing. And that’s really what the community has been about for me. It has been about this idea of having similar experiences, having, understanding of the challenges that we can face if we’re working alone. And my company has run with distributed team members, so I don’t have a central office with a team that all works together. We work in our home offices. You miss out on that ability to be able to have those conversations that you would have, potentially in-person. That for me was where I was seeking out the community, and as I did that, I realized that this community really was very open to discussing many issues and very open to sharing experiences and knowledge, which was unique for me at the time. And as you say, that’s then led on to building of relationships and those relationships have gone further afield outside your outside of specifically WordPress related. Very happily, I’ve got some wonderful friends across the community now, and they are friends and the people that I will hopefully have the pleasure of knowing for the rest of my life. Nathan, I count you in amongst that I can remember a conversation you and I had in a car park post a meetup many years ago and, it’s been wonderful to watch the journey that you as an individual have gone on through your experiences of WordPress and podcasting, et cetera, and the many branches and tendrils that we have within the community. It’s a very rich experience. I would say being part of the WordPress community.

Nathan Wrigley

Yeah, I would completely agree. And for those people who perhaps listening to this podcast, obviously this audio will go on in perpetuity, it may be that they’re listening to this and the world has become more normal. Shall we say? Perhaps we’re allowed to meet up in person again. If that were the case, what would be your best advice for digging into that community? What would your best search be? What would be the best way to go about finding where your local events are taking place?

Dan Maby

First off is look for meetups. There are thousands of meetups across the globe that are run by local communities, and I really would encourage anybody if you haven’t previously. Take a look head over to you know, there are various sites, whether it’s meetup dot com, Eventbrite, et cetera, all those kinds of events websites. Do a search for your local area for WordPress meetup event. Sign yourself up and head over. My personal experience and something that I’ve spoken about many times historically is simply getting involved in these events. We have this wonderful ecosystem of WordCamps across the WordPress space. And these WordCamps are, you’re basically taking a meetup onto a grander scale, again, encouraging local communities to try and run those WordCamps and larger events, but that can sometimes feel quite daunting, just simply turning up to an event. So if you can get yourself embedded in some way, and volunteering is by far and away, the simplest and best way to do that. Every single one of these meetups and WordCamps are run by teams of volunteers. So signing up as a volunteer, simply putting your hand up and saying, yes, I’ll get involved in some way. It gives you a purpose within the event. So you’re not simply having to be there and trying to figure out where you fit within it. You’re there and you have a role. And this was certainly my experience of getting into the WordCamps space. I’ve volunteered. I can remember experience at WordCamp Europe, or I was doing some meeting and greeting as people were arriving, and it just opened up so many interesting and wonderful conversations with people that I still have very interesting, wonderful conversations with today. And it’s just that embedding yourself in it and enabling yourself to be part of that community. First step I’d say, check meetup, look for an event. Sign yourself up, head over there. And if there’s any way that you can get involved, do. Most meetup organizers are so grateful for anybody putting their hand up and say, yeah, look, I’ll get involved or stepping forward and saying look, do you need any help with this at all? And that help can vary in so many ways. As a meetup organizer, there’s an awful lot often goes on behind the scenes that maybe attendees aren’t always aware of that really go into delivering these events.

Nathan Wrigley

What is the difference between a meetup and a WordCamp? Probably, if you’ve attended, either of those you’ll know the difference, but if you’re new to this whole WordPress community thing, it might be good to paint a bit of clear blue sky between those two different things.

Dan Maby

So if I use London as an example. Our WordPress London meetup, when we were in person delivering these events, we were seeing the, of an average of a hundred people in attendance every month. So this would run every once a month in our local environment. So the focus for both WordCamps and meetups really are about encouraging local organizers to run them. So our meetup, we feature between two and three speakers on a night. It’s usually around two, two and a half hours long. And then post that within, have a bit of a social gathering. Where we continue doing a bit of networking, et cetera. The meetup is a really a trimmed down version, should we say? Or that’s probably negative, a negative way of putting it to be honest. The WordCamp is an enlarged version of meetup. Probably the best way of putting it and WordCamps are essentially that. We’re taking the concept of a meetup, but on a much, much grander scale. And they don’t have to be enormous. I’ve attended some you know, a hundred attendee WordCamps and they’ve been absolutely spectacular, really personal. And I really enjoy the kind of smaller hundred, hundred and fifty attendee WordCamps, but equally we also have some much, much larger ones. So again, if I look at WordCamp London, the last event we ran we had around 650, I believe was 650 attendees at that event. If we then look at the regional WordCamps. So the likes of WordCamp US, WordCamp Europe or WordCamp Asia. Yeah, WordCamp Europe. I believe there’s three and a half thousand attendees at the last event, the last in-person event. So they’re often spread across multiple days as well, but not always often there’s a, a single day WordCamp as well, but the one telling difference between a WordCamp and a meetup is the WordCamps often have what we call a contributor day associated with them as well, which is a day focused entirely on contributing to WordPress in some way, shape or form. And there are so many ways to contribute. We’re not just simply talking about writing code and contributing in that way. There’s documentation, there’s marketing, there’s the multi-lingual there’s many ways to get involved. So I really, again, would encourage anybody that’s thinking about attending a WordCamp, once we are back to a situation where we are safe to be able to return to in-person events. And obviously some of the virtual events I really would encourage joining the, contributor day in any way that you can.

Nathan Wrigley

So with all of these events going on, obviously we’ve got a thriving piece of software, which is turning out to be widely used over 40% of the web. We have the statistic now using WordPress. So the software is one side, but obviously we’ve also, as you’ve just painted a picture that we’ve got this thriving community as well. An awful lot of the project perhaps was going on, at these community events, a lot of things were being organized, so contributor days, possibly different teams meeting up at various times at these events. And then sometime last year, the world paused and is still in a state of pause. I’m wondering if you have any thoughts on whether the project as a whole has been stifled. I know that we’ve gone online and we’ll come onto that in a moment, but I’m just wondering if you’ve got any thoughts about the impact that the world pausing and not being able to meet up in person. If the project itself has been stymied by that.

Dan Maby

I think this is a really interesting discussion. I can sit on both sides of the fence here. I think there is definitely an element of fatigue within the community at this stage. And I think that fatigue is being born out of the fact that potentially we are not having those in-person connections, the wonderful conversations that can be born out of the hallway track, you know it’s spectacular, what can happen, and by hallway track, you’re simply wandering around the event itself and not necessarily being in a session, but there’s, the people are mingling around and the conversations that can be born out of those chance meetings, really are spectacular. Many times I’ve run into individuals in the hallway, or we’ve just started the conversation and then somebody else has jumped in, somebody else has jumped in and before we know it, there’s, there’s a really interesting round table conversation going on about the future of the project. Because as an open-source project, we all have the potential to influence them the potential to participate in the project in some way, shape or form. I think in this virtual environment that we’re currently in, on a personal level, I believe that we’ve lost some of that. We’ve lost that ability in many ways. And it’s created this fatigue where we’re not necessarily having the opportunity to have those discussions and those new ideas, those new thoughts, or those alternative ways of looking at a problem. I think the project has possibly suffered for that, in some respects, I think is partly why WordPress as the software has been so successful is because of WordPress the community has had that really strong in-person connection and that really strong coming together as a community. Having said that equally, there are many benefits to the concept of the virtual environment that we’re in. But yes. I certainly think there are some challenges that we have come up against and we’ve tried to work towards resolving to some degree as a community in this virtual environment.

Nathan Wrigley

We’re in a strange dichotomy in that we were probably better prepared than almost any industry to move everything online at the drop of a hat, because the WordPress community is online. We understand how to put websites together and turn those websites into virtual events and all of that kind of stuff. Conversely, and perhaps somewhat unexpectedly. We were also a community, that needed to be offline in order to push the project forward. And so in some sense, we were not prepared for that. Two sides of one coin, very well prepared from the technological point of view. But perhaps we didn’t really understand that these in-person events, the interactions, the little coincidental meetings that might’ve happened, that pushed things forward. The fact that the contributor days, they were a great way of pushing the project forward. All of these little things that required us to be in-person well, they just evaporated and we weren’t really prepared for that and that’s kinda my take on it. It feels like from the tech point of view, everything’s a-okay. We can manage that side really well, but the unexpected consequences from the community going away have become slightly more obvious. And I feel it’s not really in any way, catastrophic, it’s just little paper cuts. Things haven’t perhaps worked as fluidly, perhaps interactions haven’t been made, perhaps people have become fatigued, logging onto their computer and so on. And of course, there’s the fact that there’s a great deal of excitement around turning up to one of these events and whether that’s a meetup and you just show up for the evening or you go somewhere further afield. You might need to get in the car or get on a train or get on a plane and you may have booked a hotel and your almost seeing it as a little bit of a vacation, something a little bit outside of the normal experience, all of that side has gone. And so there’s less be excited about. And perhaps as you described it fatigue, I’m describing it more as a lack of excitement, perhaps that has had a bit of an impact.

Dan Maby

I think you’re absolutely right. There’s an excitement when you’re coming together in personnel, there’s excitement. You don’t always know what to expect. You don’t always know what’s going to come in those conversations. You may have a good idea, but the ability to come together in person and really thrive off that energy of one another, it really can be quite special, but equally there are many people that don’t thrive off of that there are many people that really struggle with the idea of being in large groups of people, there’s absolutely pros and cons to all of this. And it’s something that we were in our events, in the in-person events, we were trying to be aware of, be mindful of that experience for people. Some people, as I say will thrive off that environment of being around lots of people, but those that need their own space sometimes. The idea of delivering quiet rooms at in-person events is really important because some people do just need that time away from the crowd to be able to re-energize themselves, by being by themselves. This idea of enabling all walks of life, all the variations of people that build up our community to be able to participate. And I think this is really where we’ve got a huge positive in the virtual environment at the moment we’ve brought down so many barriers. For a far greater, far more diverse mix of individuals, whether we’re talking about speakers or attendees, we’ve got some wonderful opportunities right now in the virtual environment. We’re not having to consider visas. We’re not having to consider travel expenses. The limitation that we’re running on right now in terms of attendance of an event is the bandwidth to be able to connect to that event. We were looking at the positive side of this. There are some really good things I think we need to be very mindful of as we move forward. As we move into, as we start to move into a situation where we, if we’re in a safe environment, to be able to return to the in-person events, we also need to be mindful of how do we continue to encourage that very open and very inclusive model that the virtual environment has created.

Nathan Wrigley

Do you see in the future, and we’ll talk more in a moment about specifically what it is that you and your events have done to move online over the last year or so, but just for now, do you see in the future then a model where, let’s say that we all go back and the world returns to how it was in 2018. Everybody’s allowed to get on planes and trains and everybody can move freely once more. Do you think that we have reached a point where hybrid events and by that I mean, many people will come and be present in the room, but also perhaps we need to provide the internet access so the people from further afield who don’t wish to attend, or perhaps they’re literally on the other side of the world and they only want to see two or three of the variety of sessions that are on offer that week. It’s really not worth them getting on a plane for that, but they could log in and watch them online. So do you feel that there’s a hybrid or will we just consign the online events to the realms of history?

Dan Maby

So I’m very hopeful that as a community, we will adopt the hybrid model. However, having said that, I also appreciate that we need to also figure out what this hybrid model looks like. As a meetup organizer, again, the WordPress London meets up. We were taking quite a considerable amounts of kit into the event to deliver the events. And by kit I’m talking about cameras, microphones, tripods, sound equipment, all sorts of stuff, which isn’t that common in the meetup space. And as a meet-up organizer, you don’t need to be thinking about, or how do I get low cameras, et cetera. But what it meant for us is we were pre pandemic we were already in an environment where we were live streaming the sessions. We were accepting questions coming in from the virtual audience that were consuming the content live whilst the in-person community were also consuming that content. That put us in a very strong model as we move forward, which I can get into in a moment. But the issue that I see is, are we going to try and force the experience where we’ve got the in-person and the virtual, combined together at the same time, are we actually going to create a situation where we create the worst of both worlds? So the in-person deteriorates because there’s a need for more equipment, there’s a need for more organizing and there’s need for just a very different experience where you’ve got a lot more things needing to happen from an organizer’s perspective. And then have you then got the virtual side, is their experience going to deteriorate because the organizers are having to focus on the in person. It’s an awful lot to deliver, as an organizer: an event. But to then take that event and say now I need to do at the same time, a hybrid of in-person and live, particularly on the meetup side, I think it’s something we’re going to have to be very careful of and figure out how do we do that? Are we better to have, I don’t know, for example, an in-person event and a virtual event, twice a month. Again, I’m not advocating for this for every single meetup because I appreciate every meetup is run by volunteers. It’s about the capacity for those organizers. I think when we start to look at WordCamps, it gets a little more interesting because obviously WordCamps do have a slightly larger team often, and there is often some funding supported through sponsorship, et cetera, to enable that. But again, we’ve got to look at how do we make sure that the experience is optimal for both the in-person and the virtual. And I’m not sure I have the, certainly I don’t have the answers to that at this stage, but it’s certainly something we’ve been having a lot of discussion around internally. And the platform that we’ve developed for our virtual events at the moment is something that we’re looking to roll into our hybrid model. But again, that we don’t have the answers at this stage.

Nathan Wrigley

I’m also conscious that perhaps if everything becomes available online, it may persuade people who are almost going to attend live to not attend live. It may dwindle the audience that turn up to the live event, if you know what I mean, which would be a kind of an unexpected consequence, but those people who were flip-flopping and maybe I’ll go, maybe I won’t, oh, I’ll just watch it on the screen, which is fine. But obviously you don’t want to get to the point where the in-person event is attended by just a couple of people, because everybody else is just tuning in online because the sort of sense and the purpose of that event and the camaraderie, all the good stuff that you want to happen, in-person disappears.

Dan Maby

So this was something that we discussed, a number of times pre pandemic, when we made the decision to start live streaming, the WPLDN events, and we have that exact concern and it’s a genuine concern. Are you going to deteriorate the experience by somebody has the option to just simply watch it online? It never happened. Our numbers, stayed consistent and we saw a numbers of in-person stay consistent and we saw our numbers online, grow and grow. And that really demonstrates to us that people want that in person connection, as you just said, there’s so much more to the event than simply consuming the the section that’s being delivered. So it is those conversations are happening in hallway tracks. It’s the, all the other elements to the event that you often can’t gain from a virtual environment.

Nathan Wrigley

Okay. So let’s move the conversation a little bit. It was staying on more or less the exact same topic, but I’m curious to know what it is technically that you have done since March last year in the UK, March was the moment where everything ground to a halt, and we were unable to see each other. So I just wondered if you could run us through what challenges you faced, how you’ve overcome them. And I know that you spent a lot of time trying to build a platform and shape a platform, to make this work in your situation. Perhaps explaining that might encourage other people who would like to take their events online, to reach out to you and see if you can lend them a hand.

Dan Maby

Sure. Absolutely. Just to give a bit of context before I get into this, the WPLDN events, along with several other events that we deliver, now come under the umbrella of Big Orange Heart, which is a registered nonprofit with a mission to support, promote positive mental health within remote working communities. So a big focus for us is about continuing ways to help reduce social isolation and the delivery of events do that. Now the reason I’m saying that is because there’s a team of volunteers within Big Orange Heart, that have donated time into helping us deliver them. So what I wouldn’t want to portray is yeah I’m sitting here on my own and it built this platform that enabled the community to continue to do its thing. It’s taken a small village of people to continue to do this. And I appreciate not every meetup has that ability to be able to tap into that. But what we did, we actually back, as I said, previously, we were already live streaming. So we had a pretty good idea of, the, kind of the technical aspects of live streaming content and very fortunate, we’ve got a fantastic team on WPLDN, specifically Leo Mindel, Paul Smart and Diane Wallace and myself come together. Leo comes in with some fantastic technical knowledge to help support the live streaming side of it. And we took the decision back in February, so prior to the government making any announcement here in the UK, we took the decision that was going to be our last event until we had more information in relation to the pandemic. Little did we know that would obviously continue on as it is right now, but we took what we were doing in terms of our live streaming; so we did our final in-person event in February. We jumped straight into trying to do a virtual event in our next event in March. So we delivered one event a month through WPLDN. The first thing we did in March was jumped straight into Zoom and said, yep, let’s get everybody in. Within minutes, we recognize that Zoom was entirely the wrong platform for us to deliver an event on. It’s a great platform, for the purpose of meetings one-to-one or one to many meetings, but it really isn’t a good platform for any kind of event. Because if in an event you want the ability for people to freely move around. And we’ve seen many events that have used Zoom, used multiple Zoom rooms to enable the attendees to jump into different conversations. The problem with that is you don’t know what you’re jumping into. We often refer to it as Zoom roulette because you’ll be jumping into a Zoom call and you don’t know who’s in that Zoom call. You don’t know what you’re jumping into, and it adds a huge cognitive load to the attendees of an event, because not only are they having to figure out where the different Zoom links are, they’re also then having to figure out once they’ve got in who it is that they’re communicating with in that conversation, which it just simply didn’t work for us. So we very quickly started to work on a solution that would enable us to have that ability to have freedom of movement within a virtual environment. Now, this led us on to looking, we’re huge open-source advocates. And we wanted to continue to deliver, we wanted to build something that would tie in and fit with that ethos of the open source projects that we support. So we quickly discovered Jitsi as source video conferencing solution. Ran into many challenges along the way, in terms of building out the platform. But what we ultimately ended up with was a platform that enabled us to use our existing registration process. So all of our attendees are on meetup. So we wanted for people to be able to obviously log in with their meetup credentials. So register for an event on meetup, if they’ve registered, be able to then access the event online. So we built a WordPress site, built a custom app that wrapped around a Jitsi instance, which then enabled us to have this concept of tables within the platform. So attendees would register for the event, jump in. We would be able to stream content into that platform as well as then have this idea of tables where people could freely move around and see exactly who’s on what table before they were jumping in. We delivered that I believe that was around May time of that year. So two months following the decision to go to virtual and we continue to iterate and evolve that platform from that point on, which has been, it’s been a phenomenal experience, the development of this solution. I just wanted to give a shout out to Louis Cowles, who has been doing an incredible job. Taking what I had originally put together, which was this app wrapped around Jitsi and he has turned it into something far more spectacular, which we are now, almost at the stage of being able to deliver as a WordPress plugin. So if anybody has attended any of the Big Orange Heart events or any of the events, the Big Orange Heart supports, have experienced the platform, which includes WordFest. The whole platform that we have developed there will soon be available as a WordPress plugin as well, which we’re really excited about.

Nathan Wrigley

I have to say from my part, it is now feeling incredibly mature and the fact that it will soon be a WordPress plugin is remarkable. Will that be something that anybody can access and therefore use at their own meetups? Presumably there’s some sort of burden of setting up things outside of WordPress. Maybe there’s other containers with the Jitsi software that needs to be done, or does it all get rolled into just the plugin and you’re good to go.

Dan Maby

So there’s still work that we’re working through, how to enable that within the community. Really, what we’re trying to do here is build something that is enabling communities to have the experience that we’ve had with WPLDN, and also, we’re not just simply talking in this current particular space where we’ve got the, just virtual again, referring back to the hybrid model. As a platform would work particularly well for the hybrid model, but yes, there are definitely additional technical elements to it, which we will obviously be looking at how we can mitigate that technical challenge that comes with it. There are hosted versions of Jitsi, which you can simply plug into it as it is right now. So again, we’ll be able to share more information as we move forward with that. We’re really, it’s about enabling the community to be able to continue to have that very broad reach. Even as we, as we move back into the in-person.

Nathan Wrigley

You being you, you weren’t content to rest on your laurels and carry on just doing the WPLDN event. You’ve obviously got this platform and you decided at some point last year, that you wanted to manage and organize an event which spanned the entire globe. And so WordFest was born. I don’t know if WordFest was born, basically out of the fact the world was on pause or whether you’d have plans for this prior to that. But perhaps you could spend a few minutes just outlining what WordFest is and by good coincidence, there is actually a WordFest, if you’re listening to this podcast episode, soon after it was released, there is actually a WordFest event coming up really soon. So perhaps tell us why you started it and then get onto what’s going on in the next few weeks.

Dan Maby

Sure. So as a charity, we always intended to have some form of larger in-person event. Events have been something that’s had a real passion for a very long time. The ethos of bringing people together, helping reduce social isolation of lone workers is something that really fits well with everything that we’re doing in terms of Big Orange Heart. So we wanted to enable people to come together. That had always been on the cards from the very early stages of Big Orange Heart. Of course, when we got thrown into this situation with the pandemic, as I say, we moved into the virtual environment for our monthly events, that platform that I’ve been discussing, we actually opened up to other communities. So we’ve enabled other communities to be able to run their events through our platform, without any charge to them. We just simply wants to be able to create a solution for those communities to continue to come together when they couldn’t deliver them in person. What that actually meant was that we, in the first 12 months that we were delivering events through our live dot Big Orange Heart dot org site, we’d had over 12,000 attendees come through that platform, which has meant that we’d obviously had a huge amount of feedback and we’d been able to iterate very quickly across that solution to get to a point where we actually decided that we want to deliver a larger scale event. It’s always been on the cards. Why not do that as a virtual conference or virtual festival? That’s really where the concept of WordFest was born. And I want to, again, when we give a huge shout out to Brian Richards, particularly of WordSesh. WordSesh has been around, you know, as a virtual WordPress focused virtual event for many years, I can remember way back in the early days of the first WordSesh, the first few WordSesh’s, which were 24 hour events and had a lot of fun attending those. And I remember attending my first one and actually attending for the full 24 hours. So this wasn’t something that was new in our space. We were very aware that there was a desire for it, but we wanted to wrap together the two elements of what we do. Our hearts really are in WordPress, but our focus is really around wellbeing and mental health, positive mental health. So this concept of WordFest was about bringing those elements together. So if you attend WordFest, you will find content that focuses on both WordPress and our individual wellbeing as remote workers. It really was about this concept of a global celebration of our community. We talked about different ways of delivering it. We talked about do we do over multiple days because we appreciate time zones, how do we, how do we factor in a way of enabling anybody that wants to attend to be able to attend? But we didn’t want to just say here’s a set time on this day, here’s six hours that would deliver it or, over a period of days, we’ll do, it was a real challenge. So we, we kept coming back to this 24 hour concept because it would end up, if somebody wants to attend over that one day, there was some point in the day that hopefully they would be able to join us. And it has mushroomed. It’s grown and grown. We set out to deliver the first one back in January, this year, 2021, we set a target of 2000 attendees to the event we had just over two and a half thousand attend. So it was, we completely smashed all our expectations in terms of people attending the event. But also we completely smashed our expectations in terms of the number of sessions that we were delivering. We initially set out a wanting to deliver 24 sessions over the 24 hours. That turned into 36 sessions actually ended up being 48 sessions through the first event. I’m really happy. I’m not sure it’s the right word, but I’m really happy to say that this time around we’ve actually got 66 sessions that are going to be delivered in the 24 hours. It’s been a phenomenal experience, delivering this as again, as a wonderful team of volunteers, sitting behind this people like Michelle, Cate, Hauwa, Paul, just wonderful people that are really enabling us to be able to continue to grow this event into a much larger scale event than it ever was initially. So the next WordFest live is taking place on the 23rd of July. So we’ll be featuring 66 sessions over a 24 hour period. And it is, I think one of the most wonderful things I took away from the last WordFest was, as an organizer, having organized many in-person events, there’s always a connection with your co-organizers. Certainly if you’re running a larger event, such as a WordCamp, for example, you build up this rapport and you build up this relationship that on the day of delivering the event often it’s, it’s, it’s tiring. There are, yeah, there are moments of challenges, but there are just wonderful moments as well. But you experience all of those things together as a team. What I took away from WordFest live, which was a genuine surprise to me was we managed to create that same experience. We managed to create that same shared experience as we were delivering the event. I’ll never forget sitting here, I think I was in about hour 36 of because I’d been up some time before the event and I was sitting there and just the silence that was actually happening as a bunch of organizers, we all knew how, what we were experiencing in that moment. And it was just a real special time. We use various tools to deliver it. And one of the key secret ingredients for us as organizers was Discord. So having an open audio Discord channel for us to be able to just simply be able to speak to one another as we needed in that moment, it worked incredibly well for us.

Nathan Wrigley

So the event, just tell us one last time. What are the dates and where do we go if we wish to sign up and perhaps importantly, tell us how much does it cost?

Dan Maby

I’m laughing because it costs you absolutely nothing. WordFest Live is a free event, the next event is taking place on the 23rd of July where we’ll be starting at midnight UTC. So time zones are always fun in an event like this. So we base it around UTC. So midnight UTC on the 23rd of July running for 24 hours. So that’s the Friday 23rd. You can join us at any point over that 24 hour period, we will be running across six continents. Our time zone starts off in the Australia, Australian time zones. We’ll move on to Asia, Africa, Europe, south America, and ending up in North America. And then we’ve got Antarctica. You can chill out in our community tent all day long. So over that period, we would love to see you join us. As I say, registration is entirely free. There is an optional $10 donation that you can make when registering, all funds go directly into Big Orange Heart, which was the say is a registered nonprofit. There is also an option there to sign up as a micro sponsor. Should you choose to. Micro sponsorship is charged at $250. And for that, we will obviously get some exposure of your company. And it’s really a more a reflection of what it actually costs for us to put this together, in terms of the attendees tickets.

Nathan Wrigley

This podcast episode, you could probably sum it up with one word and that word would probably be community. If I was to show up to WordFest live and I had ambitions to socialize with other people. That kind of thing is possible? It’s not just about show up to the event, watch the speakers and then wait for the next speaker to start. You’ve provided opportunities to socialize. So maybe as a final thing, just explain how that works. What’s the provision for meeting up with other people and breaking out into different groups and so on.

Dan Maby

So this was as equally important as finding fantastic speakers. We also needed to make sure that the ability for people to be able to connect, the community, to be able to come together has been a focus for us. So this is where the custom solution that we’ve been developing comes into play. So if you are attending WordFest, you can obviously consume, we’ve got two tracks running over the 24 hour period. So at any point you have a choice of at least two sessions to choose from. I say at least because there’s also some evergreen content that will be available for you to consume through the events as well. And then you can head over to our community tent which we are nicknaming Antarctica this time round, where you can connect with the sponsors. So you will see all the sponsors tables, you can jump in and have conversations, discuss with them for whatever reason you need to to connect with the sponsors, highly encourage you to do that. But in the same space, you can also spin up your own community table. And this is, we try to liken it to a sponsors hall at an in-person event. You might wander into the sponsors hall. You’ll have conversations with the sponsors, but equally you might have conversations with your peers, friends, colleagues, in and around the community. So we’ve really tried to, as best we can in the virtual environment, replicates that hallway track experience where you’re not bound to specific calls, you’re not bound to specific tables. You have freedom of movement within that platform to connect with those that you want to connect with. Equally, you also have your own profile within the platform and your own profile then has your own meeting room. So should you want to break out and have you a slightly more private conversation discussion away from the community tent, then again, you have that facility. So it’s really about trying to enable people to come together and have the conversations that are so important.

Nathan Wrigley

Thank you so much, Dan, for putting an event like this on, I know that as you’ve said, it’s not just you, there’s a great large community of people in the background as well. So thank you to them equally and during the last 18 months or so, thanks for being there and making sure that the communities can keep meeting and you’ve endeavored to to keep all of that going. And I fear that unless it was for people like you who’ve really gone the extra mile, perhaps things wouldn’t be quite so bright going forward. From the bottom of my heart. Thank you very much, Dan, for coming on the podcast and for everything that you do.

Dan Maby

Oh I’m deeply appreciate. I thank you. Thank you very much, and likewise. Thank you for all that you do across the community. I appreciate it. I’ll see, you spent a lot of time chatting with people like me sharing some wonderful stories.

Nathan Wrigley

Thank you so much.

How to Create a WordPress Popup Based on Location (Step by Step)

Do you want to create a WordPress popup based on the location of your visitors?

Creating WordPress popups based on location helps you deliver the right marketing message, to the right people, at the right time. This means a better user experience and more revenue for your WordPress site.

In this tutorial, we’ll show you how to create popups based on a user’s location and add them to WordPress.

 How to create a WordPress popup based on location

What Are Location Based Popups?

Location based popups are similar to standard popups, but they only display for visitors from specific locations.

So, visitors from the US will be shown different popups than visitors located in the UK or in Spain.

You can narrow down your location targeting even further, and target specific states and cities. This way visitors in Florida can be shown a different popup than visitors in California.

This process is known as geotargeting, and it lets you encourage your visitors to take specific actions on your site based on where they live.

Why Add WordPress Popups Based on Location?

Using location-based popups in WordPress gives your visitors a highly relevant experience. It shows your visitors that you understand their needs and can lead to better conversions.

This level of personalization can help you reach your website goals, like growing your email list or making money online.

Using geolocation popups can help your business website in a lot of ways.

  • Boost website credibility by showing visitors you’re aware of their location
  • Run eCommerce coupons and specials for visitors in certain areas
  • Promote local events and conferences to your visitors
  • Highlight products that are relevant to visitors in different locations

How to Create a WordPress Location-Based Popup

The easiest way to add popups to your WordPress website is using a plugin.

We recommend using OptinMonster. It’s the best WordPress popup plugin in the market with over 1.2 million users.

You can use the OptinMonster drag and drop editor to simply create a popup campaign in minutes. Plus, you can easily personalize your popups based on what page their viewing, actions they’ve taken on your site, and more.

The first thing you’ll need to do is install and activate the plugin. For more details, see our guide on how to install a plugin in WordPress.

The OptinMonster plugin acts as a link between your WordPress site and the OptinMonster software.

Once the plugin is activated, you’ll have a new menu item called ‘OptinMonster’ in your WordPress admin dashboard.

Open OptinMonster dashboard

Click ‘OptinMonster’ to open your OptinMonster dashboard.

Then, click ‘Launch Setup Wizard’ to connect your site to OptinMonster. If it’s your first time, then you can create a new account for free.

OptinMonster launch setup wizard

After you’re done going through the setup wizard, your site will now be connected to OptinMonster.

To create your location based popup navigate to OptinMonster » Campaigns.

Then, click ‘Add New’ to create a new popup campaign.

Add new OptinMonster popup campaign

Once you’ve done that, select the ‘Popup’ campaign type.

Next, you’ll select the campaign template. Your template forms the foundation for the design of your popup. So, choose a template that closely resembles the design you want.

For this tutorial, we’ll select the Checkout template. Once you find a template you like, hover over it and click ‘Use Template’.

Select OptinMonster template

Then, you’ll need to name your campaign.

This name won’t appear in your design. Instead, it’s to help you remember what kind of campaign you created.

Start building popup

Next, click ‘Start Building’.

This will bring you to the OptinMonster app, where you can customize the appearance of your popup.

Customize location based popup

You can totally customize your popup by adding new blocks, text, headings, and more. Just click on the element you want to edit and the options menu will appear on the left.

Once you’re satisfied with how your location based popup looks, click ‘Save’, then click on the ‘Display Rules’ tab at the top of the screen.

Set popup display rules

This is where you’ll set your location triggers.

The default rule is your popup will appear on any page after a visitor is on the site for 5 seconds.

You’ll need to change the first rule to the visitor’s physical location. To do this, click on the ‘time on page’ display rule, then select ‘Physical Location’.

Set physical location rule

Now you can set the popup to display for visitors who are in a specific location.

You also have the option to include or exclude visitors who are in an EU country.

Popup visitor location settings

We’re going to set the rule so the popup will show when a visitor is in Las Vegas, NV.

Next, click ‘Validate’.

Set visitor location

Now, a popup will appear that lists available locations based on what you entered. Simply select the location you want and then click ‘Next Step’.

OptinMonster also gives you the option to add an animated effect or sound on the next screen, but we’ll leave the default settings.

Once you’ve done that, click ‘Next Step’ again, and you’ll be taken to the summary page where you can review your location popup settings.

Location popup display rules summary

If your settings are correct, then navigate to the ‘Publish’ tab and switch the ‘Publish Status’ from Draft to Publish.

Next, click ‘Save’ and exit the screen.

Publish location popup

Your popup based on your user’s location will now be live on your site.

If you want to create multiple popups based on location, then follow the same process above and change the ‘Display’ rules to the new user location.

With OptinMonster, you can have multiple popup campaigns running at once and provide a targeted experience for all your visitors.

We hope this article helped you add a WordPress popup based on location to WordPress. You may also want to see our list of the best email marketing services and best live chat software to boost your sales.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post How to Create a WordPress Popup Based on Location (Step by Step) appeared first on WPBeginner.

How to Know if Your WordPress Website Uses Cookies

Do you want to know if your WordPress website uses cookies?

Cookies are tiny files used by websites to store temporary information in users’ browsers. Many countries have different cookie laws that require website owners to disclose which cookies they use and what information they track and store.

In this article, we will explain how to find out if your WordPress website uses cookies and how you can manage those cookies to comply with local laws.

How to see which cookies are set by your WordPress website

What are Cookies?

Cookies are small files containing data sent by a website to store in a user’s browser. Cookies play a significant role on the web and are widely used to improve user experience.

WordPress uses two types of cookies out of the box.

First, there are session cookies. These cookies are used to login and are set for all logged-in users on a WordPress website.

Then, there are comment cookies. These cookies are set when users leave a comment on your WordPress blog. Their purpose is to store user’s name, email address, and URL information so that they don’t have to re-enter it the next time they comment on your website.

Apart from WordPress, third-party plugins and tools may also set cookies for your WordPress website.

What are Cookie Laws?

Cookies are a powerful tool that can be used to track a lot of information about users. Considering the privacy risks, many countries and regions have enacted laws that set compliance guidelines for website owners.

For instance, European Union has GDPR Law and ePrivacy Directive. Similarly, countries like Canada, UK, Japan, and many more have laws that require website owners to get user consent and disclose the information they collect, store, and track about users.

That’s the reason why you see cookie popups on many different websites. These banners allow website owners to comply with GDPR, cookie laws, and other privacy laws in different countries.

How to See Which Cookies Are Stored by a WordPress Website

All modern web browsers make it easy to view the cookies set by any website you visit.

Google Chrome

In Google Chrome, first, you need to visit your WordPress website. After that, click on the Padlock or Not Secure icon in the browser’s address bar. This will open a menu where you need to click on ‘Cookies’.

Viewing stored cookies in Google Chrome

This will bring up the cookies popup where you will see all the cookies set by that particular website in your browser.

Cookies stored by a WordPress website

You can also view these cookies by using the Inspect tool. Simply visit your website and left-click anywhere to select the Inspect tool.

This will split your browser window and you’ll see the developer console panel. From here you need to switch to the ‘Application’ tab.

Viewing cookies using developer tools

Next, you need to click on the Cookies menu from the left column and you’ll be able to see all the cookies stored on your site. More importantly, you’ll be able to see the data stored by the cookie under the ‘Value’ column.

Mozilla Firefox

In Firefox, you need to visit the website you want to check and then right-click anywhere to select the ‘Inspect Element’ tool.

This will split the browser window and you’ll see the developer console panel. From here, you need to switch to the ‘Storage’ tab and click on ‘Cookies’ to view all the cookies.

Viewing cookies set by WordPress using Firefox

Plugins That Allow You to Turn Off Cookies

Now when reviewing cookies set by your WordPress website, you may notice that there are some cookies set by different WordPress plugins you are using.

As a website owner, you may not want to use these cookies to comply with cookie laws in different countries and limit your liabilities.

However, not all WordPress plugins come with easy ways to turn off cookies and make your website compliant. Following are some of the plugins that allow you to easily turn off cookies without breaking plugin functionality.

1. MonsterInsights

MonsterInsights is the best Google Analytics plugin on the market. It allows you to properly install Google Analytics and setup EU compliance addon.

First, you need to install and activate the MonsterInsights plugin. For more help, see our article on how to install Google Analytics in WordPress.

Once you have set up the plugin, go to Insights » Addons page and install EU Compliance addon.

EU Compliance addon for MonsterInsights

The addon works out of the box, and there are no settings for you to configure. You can see it’s enabled by visiting Insights » Settings page and switching to the Engagement tab.

EU Compliance addon status

The addon will now automatically anonymizes IP addresses, disable the Demographics and Interests Reports, turn off user and author tracking, and more. It also integrates with Cookie Notice and CookieBot plugins automatically.

2. WPForms

WPForms is the best WordPress contact form plugin on the market. It allows you to easily create GDPR compliant forms for your WordPress website.

First, you need to install and activate the WPForms plugin. For more details, see our step by step guide on how to install a WordPress plugin.

Upon activation, you need to visit WPForms » Settings page and switch to the General tab.

WPForms settings

From here you need to scroll down to the GDPR section and check the box next to GDPR enhancements option.

WPForms GDPR settings

Checking the option will expand it and you’ll see the option to disable user cookies and user details for all forms.

WPForms also allows you to make individual forms GDPR compliant. For more details, see our article on how to create GDPR compliant forms in WordPress.

3. OptinMonster

OptinMonster is the best lead generation software on the market. It helps you create GDPR compliant optin forms and lead campaigns for your website.

It allows you to easily add a Privacy Policy with a customizable checkbox. Users can then only submit the form once they’ve checked the box. It also allows you to enable double optin for your forms.

Adding privacy policy checkbox to OptinMonster campaigns

Plus, OptinMonster lets you target visitors based on their location. That way, you can make sure you’re showing GDPR-compliant optins to customers in EU countries. OptinMonster only creates cookies to improve user experience on your website and these cookies can only be utilized for on-site tracking.

4. Smash Balloon

Smash Balloon is the best social media plugin for WordPress websites. It allows you to create social media feeds that are compliant with cookie and GDPR laws.

Smash Balloon GDPR compliance

The plugin detects if you have a cookie notification plugin enabled and then holds any cookies until user give cookie consent.

More Ways to Comply with Cookie Laws for WordPress Websites

It is the responsibility of a website owner to comply with cookie laws in different regions. Here are some basic steps to make your website more compliant.

1. Add a Privacy Policy Page

A privacy policy page is legally required to comply with privacy and cookie laws in different regions. See our guide on how to easily add a privacy policy page to your WordPress website.

2. Install a Cookie Notification Plugin

Cookie notification plugins show a notification on your website that it uses cookies and seek consent from the users.

Cookie Notice and CookieBot are two of the most popular cookie notification plugins that are compatible with many other popular WordPress plugins.

For more options, see our list of the best WordPress GDPR plugins to improve compliance.

3. Keep an Eye on Plugins and Tools that Use Cookies

Check your website cookies to make sure that you can connect each cookie to a installed plugin and tool on your website. When installing new WordPress plugins or third-party tools, make sure to check if they have options to make them GDPR and cookie law compliant.

We hope this article helped you learn how to check if your WordPress website uses cookies and ways to make your website compliant with cookie laws.

You may also want to see our WordPress security guide to make sure that any data that you collect on your website is properly secured.

If you liked this article, then please subscribe to our YouTube Channel for WordPress video tutorials. You can also find us on Twitter and Facebook.

The post How to Know if Your WordPress Website Uses Cookies appeared first on WPBeginner.

How Microservices Empowered the UK's DWP to Pivot During COVID-19

In the beginning of 2019, the U.K.’s Department of Work and Pensions (a British government department responsible for welfare and pension policy) began work on an API library. DWP integration lead Jaqui Ledgetter credits this library (which can be used across government agencies) with empowering the DWP to respond to the COVID-19 crisis with alacrity.

Hi everyone, I’m jaegadigital

We run a digital marketing company which was established back in 2016 called Jaega Digital.

Before starting my business in Digital Marketing, I had spent nearly 20 years in the digital space, which is since I started university in 2000. During that time I've managed various large web development projects and national digital marketing campaigns.

In detail I spent roughly around 5 years working with two of UK's leading digital marketing agencies, and managing projects for some of the UK's largest retailers with a total monthly budget up to 60K. Sectors included the Motor industry, Finance (Insurance and Banking), Homewares / DIY Retail, Fashion and Telecommunications.

As a freelancer I was able to provide digital marketing consultation to much smaller companies with smaller budgets, where their primary need was education for bringing digital marketing in-house or to better understand their existing performance through the implementation of best practices.

I also provided both large and startup digital agencies with extra support especially when they needed the support with larger projects.

If I ever decide to return digital marketing my ideal role would be in project management and account management. Watch this space.

However, since September 2018 I have been supporting my wife in developing our cafe and catering business.

So far since we opened our business in Sept 2018 we have seen growth of nearly 500% in footfall from around 50 customers a day to 250 a day. We have seen similar increase in revenue but is more near 600%.

We have employed to total of 10 staff over the last year but currently have 4 staff on the payroll.
Our aim is to expand on catering for businesses, and begin deliveries and possibly open more premises.

What to Use Instead of Number Inputs

You might reach for <input type="number> when you're, you know, trying to collect a number in a form. But it's got all sorts of issues. For one, sometimes what you want kinda looks like a number, but isn't one (like how a credit card number has spaces), because it's really just a string of numbers. Even more importantly, there are a variety of screen reader problems.

Hanna Laakso documents the problems for GOV.UK. This is what they landed on:

<input type="text" inputmode="numeric" pattern="[0-9]*">

The inputmode attribute is pretty great, and we have a deep dive on that.

Phil Nash came to (almost) same exact conclusion, and blogged about improving the experience of a two-factor auth code input on the Twilio blog:

<input
  type="text"
  name="token"
  id="token"
  inputmode="numeric"
  pattern="[0-9]*"
  autocomplete="one-time-code"
/>

That last attribute is interesting and new to me. It means you get this super extra useful experience on browsers that support it:

iOS screen with a numeric input and a text message offering to auto-fill the two-factor auth

There are other autocomplete values, as Phil writes:

There are many autocomplete values available, covering everything from names and addresses to credit cards and other account details. For sign up and login there are a few autocomplete values that stand out as useful hints: usernameemailnew-passwordcurrent-password.

Browsers and password managers have very good heuristics to find login forms on web pages, but using the username and current-password values make it very obvious. 

The post What to Use Instead of Number Inputs appeared first on CSS-Tricks.

Most Popular Programming Languages in 2020

With a forecast for 2018 and 2020. It was forecasted that 20 billion apps would be downloaded in 2020 in the UK.

According to the survey reports, the number of downloaded mobile applications is increasing constantly. In the contemporary era, now customers prefer mobile applications to get information about the service or product; however, mobile applications have turned as a success key to stay ahead in the market competition. The high usage of mobile applications has raised to the demand of the mobile application development service with the latest integrated trends such as blockchain and the Internet of things.

Smashing Podcast Episode 7 With Amy Hupe: What Is A Government Design System?

Smashing Podcast Episode 7 With Amy Hupe: What Is A Government Design System?

Smashing Podcast Episode 7 With Amy Hupe: What Is A Government Design System?

Drew McLellan

Amy HupeHave you ever wondered how design systems are used within a government? Also, if you’d want to document a design system the best way you could, how would you do it? I spoke to Design Systems advocate, Amy Hupe, who shares her advice and lessons learned.

Show Notes

Weekly Update

Transcript

Drew McLellan: She’s a Content Specialist and Design Systems Advocate who spent the last three years working as Senior Content Designer at the Government Digital Service. In that time, she’s led content strategy for the GOV.UK design system, including a straightforward and inclusive approach to documentation. She’s previously worked for consumer advocacy company, Which? where she wrote about everything from composting to conveyancing. And a new role for 2020 sees her take up as Project Manager for Babylon Health Design System, DNA.

Drew: She’s a skilled cook, an Instagrammer, and knows how to use language to make services accessible and inclusive. But did you know she once sang backing vocals for Billy Ray Cyrus? My smashing friends, please welcome Amy Hupe. Hello Amy. How are you?

Amy Hupe: I am smashing. Thank you.

Drew: So I wanted to talk to you today about the role of design systems within government organizations generally, but specifically the GOV.UK design system, which I know you’ve done a lot of work with. I guess first of all, what does the GOV.UK design system encompass? And what was your involvement with it while you were at GDS?

Amy: So it encompasses all kinds of things. So I think the most obvious representation of it is the kind of website side, which is GOV.UK/design-system. And there you’ll find all of the kind of documentation. So all of the design guidelines, and the components and patterns, and you’ll see some of the code, lots of examples and lots of advice on how to use it. But thinking kind of more broadly than that, it also encompasses things like the prototype kit, which is a prototyping tool that is used in government to make HTML and CSS prototypes. So quite high fidelity prototypes and it also has its own kind of front end framework, which is called GOV.UK Front End. So that’s all the code that they use to build the services.

Amy: But then I like to think of design systems more holistically. So as well as all of that stuff, there’s also all the processes that sit around it. So things like how people contribute to it and how people come to know that it exists. Things like adoption and awareness and all that sort of stuff. So all of the things that enable people to design and build services in government is how I would define it.

Drew: So what was your involvement while you were at GDS with that? Where did you slot into that system?

Amy: It all kind of happened by chance, I guess. So I joined as a content designer in January 2017, and my intention when I came to GDS was actually to join the Gov UK content teams. So I thought I was going in to start writing guidance for system, and that was my dream. That was what I wanted to do. Then I arrived on day one and got plunked into this little protect team, called the Service Manual Patterns and Tools team.

Amy: At that point the design system didn’t exist, but we had our design patterns and some bits and pieces knocking about in different places. There was an ambition to try and pull those things together. So I was put into that team as a content designer. I didn’t know what a design pattern was, didn’t know anything about code, didn’t know anything really about web design at all. All I really knew was content.

Amy: So it was a pretty steep learning curve and I spent the next six months to a year, I think, helping the team to prototype it and figure out how it would be organized and laid out and how we would write our guidance, and all that sort of stuff. Then, in the midst of all of that as well as working on the content, I also started to look into the contribution side. So how people would contribute to it and how people would come to discover it and, get in touch with us, and what we would do when they did get in touch with us to try and make it better.

Drew: So what does designing content in that sort of context to be involve? What were the sort of daily tasks you were tackling?

Amy: So all kinds of things really. I mean there were weeks at a time I think where I didn’t write a single word and it was more just going out to research and meeting our users and try sort of understand what it was that they wanted from a design system. So yeah, without getting too far into it, there had been attempts to make something like the GOV.UK design system before, which is how we ended up with this kind of slightly disparate set of resources.

Amy: For one reason or another, these things ended up quite spread out, and it was never really one of them that was seen as the central place to go for this stuff. So a lot of it, it was just trying to understand what had happened before and why those things hadn’t necessarily taken off in the way that we had hoped that they would. Trying to understand which bits of our existing landscape were working for people and which bits weren’t.

Amy: So a lot of it was going out with our research [inaudible 00:05:07], and sitting in user research interviews, and taking notes and talking to people, and just understanding what it was that they needed. Then there were days where I did actually get to sit at a keyboard and write some guidance about some stuff, which was nice too. But yeah, it was very different for me. As you mentioned in the intro, my background was working at Which? So it was much more a traditional editorial role and I was used to working on long form content, and just writing really long articles, and pieces. So yeah, it was quite a big change. It was a big leap from that.

Drew: So your users in this context are people who are working in different government organizations? Is that right? Different departments within the government?

Amy: Yeah. Yeah, that’s right. So people working in, I think there’s 25 different ministerial departments in government, and then there’s lots of agencies and local government departments as well. So we were trying to spread out and talk to a really wide range of people from across the civil service. So yeah, lots of traveling in those early days.

Drew: Do you think that designing or working on a design system for a government, essentially, is any different from a design system for a small company or a big sort of enterprise company?

Amy: I think so. I mean I think from what I can kind of gather from conversations I’ve had, and conferences I’ve been to and stuff, every design system is slightly different and the context is always slightly different, and government is no different in that respect. But yeah, I suppose some of the unique challenges to working on something for government, is first of all the scale of it. So the audience is probably the biggest that you could have because government is so big, and all the different kinds of departments and the geographical spread of those organizations. So the scale of it is definitely something that’s slightly different.

Amy: I think also the fact that it’s not commercially competitive. So we weren’t trying to keep everything under wraps. Everything was done in the open as far as possible. Yeah, it’s all run as a big open source project, which was a slightly unusual concept for me. It took me a little while to get used to that.

Amy: Certainly when we first released it, we would see bits of our guidance and code popping up in other people’s design systems. It took a little while for me to feel all right about that. I think at first I was like, “What’s going on? Why are these people taking our stuff?” But actually now, I really like that. I see that as a big compliment, and I think it’s really good to reuse what you can. But yeah, that’s a strange kind of world to enter when you’ve been used to working in a more commercial setting, I guess.

Drew: I suppose the fact that it’s a essentially publicly funded system, means that is uniquely suited to the public taking it and using it, but also worldwide did you see a lot of use outside of the UK?

Amy: Yeah, yeah, there’s been some really exciting projects across the world that have picked it up. So I know that the New Zealand government have used quite a lot of it. I’m not sure what stage they’re at the moment, but certainly I saw their early data design system and they really used a lot of our guidance and our code, our layouts and things. I think the Dutch government is also using the GOV.UK design system primarily as its first proof of concept. The Australian government started with all of our contribution guidelines and have sort of adapted them based on their research. So we’ve been able to take some of that stuff back in. Yeah, so it’s gone pretty global. It’s exciting.

Drew: Would you factor in the fact that people would be using it when making decisions about the sort of next phase of things? Would it factor into your decisions that it’s actually your audience suddenly isn’t just UK government, it actually could potentially be a worldwide audience?

Amy: It’s definitely a consideration and I think at times that definitely made us as a team quite nervous about certain things that we were doing because the our audience and the scope of it suddenly got much bigger when we were thinking about all the different people that were using it. But personally I think you can’t get too caught up in that primarily we are there to serve the UK government. So it’s not practical to consider all of the potential audiences for it. I kind of think it’s up to the teams to adapt it how they need to for their own, their own users. But yeah, definitely it does make you think quite carefully about just throwing things out there before they’re kind of ready tested and stuff.

Drew: So were there any other sort of surprises in working on this design system other than the fact that it was then taken and used more broadly than you’d initially expected? Did anything else spring out and surprise you about it?

Amy: One thing that definitely stood out to me was the range of people in our audience. So not just the size of the audience, but like the variation in people’s level of knowledge, their skills, their confidence, the different kinds of jobs that they did and the kind of contexts in which they were working. I think there’s definitely a lot of variation in there. I think my perception going in was that I had this vision of this like designer front end developer in my head, somebody who has lots of technical knowledge and actually that’s just one type of user. There are lots of other people like content designers and things weren’t necessarily an expected audience for it, but have turned out to be key users.

Amy: So I think, yeah, that that was definitely a surprise to me. Then thinking about how we could cater to all those people with such a broad set of needs with the design system was definitely quite a big challenge. Yeah, I think that was probably my biggest surprise. Then I guess alongside that just how much people had seen to adopt it as their own. So I think after we launched pretty quickly, I was really pleasantly surprised at how many people I would see going out on advocating for it within their own departments and teams and people trying to contribute to it and people getting in touch with us to ask how they could kind of adapt it for their own users. It felt really community owned from day one and that was not necessarily something I expected, but something that was ready really good to see.

Drew: I guess much of the role of a design system is as a way of sort of documenting the design decisions that have been made so that those decisions can be then implemented and understood, and used by people. So I guess a design system is as much as anything, a documentation artifact isn’t it? It’s taking those decisions that have been made and explaining them in a way that people can reuse them. How did you approach as a team they design system as a sort of documentation artifact? How did you document what you were doing?

Amy: So I think it was about getting as much as we could get in a really clear picture of what people needed from that documentation. So this comes back to that point that I made about it being quite a broad reaching audience because there’s a whole range of different needs that people talk about documenting a component or a pattern like it’s a kind of single task. But actually there are loads of different ways that you can do that and there are loads of different needs that you need to take into consideration. So we have people who, for example would just, they would say, “Oh I want to see the research behind this.” For some people that means a number. They want to know that it’s being used in 20 different services so that they can tell their product manager that it’s worth investing the time and the money in implementing it within their service.

Amy: And that’s for them it’s just about getting that evidence-based backing for the decision that they’re trying to kind of push through. But then there’s other people who really care about understanding the research and whether it’s appropriate for their context and what additional research they might need to fill in to fill any gaps that have been missed or perhaps that they are dealing with in their unique situation. So I think the approach was to try and understand all of those different needs and to try and get a sense of priority amongst those and understand like how we could cater to all of the various different requirements that people had from the documentation. It’s not just one kind of one thing that fits everybody.

Amy: So figuring out how to kind of address all of those needs and to signpost the content really well in a way that meant that people could skip over the bits that weren’t relevant for them as well. Because when you are trying to serve such a broad audience, obviously you end up providing quite a lot of information. So making sure it’s really well signposted and organized I think was quite key to what we were doing.

Drew: So am I right in understanding that different departments within the government aren’t actually compelled to adopt the design system? You actually have to effectively sell it into them and persuade them to use it?

Amy: Yeah, so it’s slightly complicated. So in government there’s something called the government service standard and it’s a standard which all government services with over a certain number of users are required to meet in order to get funding and then to go into Alpha and then Beta and then live. One of the points on the service standard ,I left three weeks ago and it’s already dropped out of my head to which number it is, but one of the points of the service standard, it talks about reusing patterns and components and trying to reuse what’s there already. So sort of under that point they are compelled to use it, but it’s loose and it depends on who the assessor is. It’s not sort of heavily mandated. We would all always sort of advocate for doing what’s best in the specific context rather than just reusing patterns out of the box for the sake of it to tick a point on a service assessment. So it’s difficult to force it. So the approach was always much more collaborative and it was always about building support and building advocacy for the design system not shoving it down people’s throats.

Drew: I guess to that end, one of the ways that you’ve managed to do that is by encouraging contribution. Is that right?

Amy: Yeah, definitely. So I’m a big fan of contribution to design systems. I think it’s something that’s really interesting and yeah, certainly in the team we did a lot of work to make it possible to contribute to the GOV.UK design system. One of the real kind of benefits that we saw from that was The net advocates for the design system increasing. So when you get somebody to contribute to it and they then feel kind of more invested in it and what we received, those people would then go out to their teams and they would become our best sales people almost because they’d feel like they had a little piece of it and they had sort of something to show people and they would then encourage more people to contribute. So that effect ends up being quite exponential. Yeah. So we put a lot of effort into making that possible.

Drew: What sort of things did you do to encourage contribution?

Amy: We started really early. So way before we had a public design system, we started to engage with people who we thought would be interested contributors. I should mention here, we had a brilliant service designer on the team. She joined us in, I’m not going to get the dates correct in any way at the moment, but I think she worked with us in the whole of sort of 2018 and her name’s Ignatia and she just did a fantastic job of going around and engaging people. So one of the things that she did was to go and identify all of the different patterns in government and all of the different variations of those patterns. So going out and kind of saying, okay, there’s, there’s 10 different ways to ask for an address in government. Let’s look at them all together and decide which we think is the most appropriate approach.

Amy: How can we consolidate these into one? She ran a big workshop to try and get people looking at those and doing that kind of consolidation as a team. I think definitely her approach to building collaboration in way before we actually released anything to the public really helped with that because it meant that people already have that kind of awareness of it and many people had already contributed to it in some fashion or another before we actually took it public. So put us a few steps ahead. So I think that was really important. And just persistence, like a lot of persistence from the whole team in kind of helping people to contribute. I think there’s an idea that if you get people to contribute to a design system that’s a pretty sweet gig cause you can just get people to do all the work for you.

Amy: And you just sit there and you make your level code fixes and everybody’s actually giving you all the good stuff. But actually as anyone who’s worked on a design system will know, it’s incredibly complex. It’s very difficult to make a centralized solution that works for multiple different teams, and really, unless you’ve worked on a design system, it’s not reasonable to expect anyone to really understand what that takes. So there’s a lot of hand holding. There’s a lot of work involved in supporting contributors to contribute, I think I said this before, but it probably takes longer, I think, to help somebody to contribute to a design system then it would to just make the thing yourself in the centralized team. But I think recognizing the value that it brings and being persistent in your efforts to make people aware of contribution and help them to do it, help them to feel kind of motivated to do it. I think, yeah, that that persistence was really sort of key to our, our success in that area.

Drew: And just practically speaking with managing those contributions from the community, were there any tools or processes or anything that helped with that?

Amy: Yeah, so we had quite a strict process, I would say. Strict in so far as maybe, strict is the wrong word, comprehensive is probably a better word. So yeah, we have a set of contribution criteria which are in the design system. So everything’s as open as possible so people know what to expect. So there’s a set of criteria that we developed with the various people from the government community outside of our team, so again, like trying to involve people in the creation of these processes I think is really important. So there’s a set of criteria that all contributions to the design system have to meet and to make sure that we were being fairly unbiased, I suppose, and fair in terms of making the decisions about whether things met those criteria or not, we enlisted the support of a working group, which was a panel of representatives from across government. All from kind of different departments and different disciplines and people with different levels of seniority.

Amy: So everybody would have a slightly different perspective on the contributions and we would get together with them once a month and ask them to review any new contributions and decide whether or not they had met the criteria. So yeah, it was a sort of process designed to try and democratize the design of the design system I suppose, and to make it representative and ensure that it wasn’t just our team sitting in the middle making all the decisions without really understanding how it would affect the teams using those things.

Amy: Yeah, that was our sort of process. One more post I should mention is there’s a community backlog on GitHub, which anybody can use it. You don’t have to work in government to go and see it. It’s accessible from the design system and it’s basically a place where we try to host all of the research and all of the experimental stuff and the examples that go into their components and patterns in the design system. So again, it’s about pushing for that transparency and working in the open as much as possible so that people can have a voice and they can influence things before they’ve actually been published.

Drew: And do you think that process has worked well? If you were embarking on the same thing again, do you think you’d adopt a similar process or is there anything that didn’t work?

Amy: I think I would adopt a similar process but perhaps go into with slightly different expectations. What I would say is maybe slightly more realistic expectations and having said what I said about how we think that contributing will make things easier and faster. I was definitely in that camp. I think I thought that there would be a spike of work in the beginning to get people familiar with contributing and then over time we’d be able to be more hands off and people would just get the hang of it and it would be fine. But actually that never really materialized. There was always a lot of work involved in helping people to contribute and as I say, I think that that’s sort of to be expected. I don’t think you can really get away from that, but I still think it’s valuable.

Amy: I still think it’s worth investing that time, but perhaps not with an idea that you’re going to speed things up or that you’re going to be able to scale quicker or more from having contribution. So yeah, I think the process worked well. I do think it needs to be tailored to different organizations, so I’m starting a new role on Monday funnily enough, I’m working on another design system and I don’t expect to be able to pick up that process and just move it over there. I think everything has to be tailored to the organization and the context that you’re dealing with, but there’s definitely elements of it that I would like to try and bring over. But yeah, with slightly tempered expectations, I think.

Drew: I’ve talked a couple of episodes ago with Hayden Pickering about designing components, particularly within a design system to be accessible. That’s something you’ve got a lot of experience with too, I believe. Obviously accessibility is really, really crucial when working within a government design system, but many of us would argue that it’s really, really crucial wherever you’re working. Do you think design systems play a role in the accessibility of a design or the implementation of a design?

Amy: So there’s a brilliant talk by Tatiana Mack about building inclusive design systems that touches on this and that was sort of really influential to me and she talks about the sort of multiplication effect of design systems. So we have, with design systems, we’re telling people what good looks like and we’re giving people kind of quick ways to implement what we’re telling people best practices is. So that can work either way. It can work really well if you give people good design and good accessible design, then you have the potential to multiply that accessible design and to make things more accessible and more inclusive by default.

Amy: If you make decisions that exclude people in a design system, in that centralized space, which becomes the start point for people designing services, then you really have the potential to proliferate that exclusionary design. So I definitely think that design systems play a role in promoting and multiplying accessibility. But I think that it all starts with the intention of the teams working on and using the design system to make that happen. A design system is really it’s just the kind of vehicle I suppose and the intention needs to be there to make things accessible.

Drew: One of the things that always fascinates me, particularly with design systems that have such a large and varied audience like the the GFI UK design system, is the process of proliferating changes across the system. So if you, for example, find an accessibility improvement that you could make in a particular pattern and you make it in the design system, how do you ensure that that gets rolled out across such a broad audience? Is that something you’ve got any experience with?

Amy: Yeah. So again, I think that we kind of in the GOV.UL design system team, we put a lot of consideration into how that would work. I have to be honest, a lot of it is to do with how it’s technically implemented and I’m definitely not the right person to talk so much about the technical aspect of the team. I find there’s sort of two camps with design systems and there’s a camp which is like let’s get stuff out there as quickly as possible. Let’s just make it open soon as we can and that will stop duplication of effort and multiplication of effort and then we can iterate it as we go along. Then I think that there’s a slightly more sort of let’s move a bit more slowly camp, which I think I’m in, which favors holding off on releasing stuff until you have a certain level of confidence in it.

Amy: And I think that’s quite important because I think that in general, if you’re designing products and services, then starting with the minimal thing and then iterating as you go I think works great, but I think when you’re building something central that’s designed for lots and lots of people to sort of reuse and give to lots of different audiences, you very quickly use control of the thing and the way that it’s being used. So I think that having a certain amount of confidence in something before you release it and having a kind of assurance process in place, that means that you’ve got some confidence that it’s accessible before it goes out there is quite key and then hopefully the thing is slightly more stable and I think that’s really important for trust. I think trust is quite important when we’re talking about making changes to design systems because if we’re releasing changes all the time, then that makes the system quite unstable to use and I think that that breaks down trust and then people aren’t so likely to install updates and things.

Amy: Whereas I think if you can show that you’re being considerate about what you’re releasing and you’re releasing changes only when necessary, then you have that Goodwill and then people are more willing to make updates and stuff I think. But yeah, I mean I know that a lot of work went into making sure that the update process was fairly smooth and easy to implement in the GPV.UK design system. I’m just not the right person to talk about it, I think.

Drew: So we talked briefly about documentation. If I was looking to document a design system and if I wanted to do a really good job of it, is there anything that you would advise me to do to make sure I was documenting stuff well?

Amy: I never think it’s possible to kind of just give a blanket statement here because it really does need to cater to like the specific audience that you’re dealing with. My thing is to always aim to be just a little bit more inclusive than you maybe feel that you need to be. So if you’re thinking about, especially in a smaller organization that’s maybe scaling, I think that you have to be just as considerate as your future audience and your potential audience as your current audience. So if you have a small organization and you’ve got 10 front end developers and they all know the same sort of stuff and they’re able to talk to each other and communicate fairly freely, then your documentation may not to be as comprehensive as it within the larger organization.

Amy: But I think that in order to help a design system scale and to make sure that it’s equipped to do that, you have to think about who might join the organization in the future and who do you need to kind of leave the door open for? Who do you need to make things clear to? So I think always aim to be a little bit clearer than you feel you need to be in the moment. I think really testing documentation a lot is useful, so there’s lots of different ways to test content and documentation and I think that it’s really important to go out and make sure that it makes sense to other people. I think Caroline Darret always says that if you understand it well enough to know it’s correct, then you know too much to say that it’s clear.

Amy: Have I said that correctly? If you know it well enough to know it’s correct, then you know it too well to say that it’s clear, that’s better I think. And I really sort of agree with that. I think that to write good documentation you have to have pretty good subject matter knowledge or you need to or you end up developing that subject matter knowledge over time and through the process of writing it. By the time you’ve got that subject matter knowledge, it’s really hard to judge whether or not you’ve conveyed it in a way that’s clear to somebody who doesn’t. So going out and testing it with people who don’t know the subject matter like you do and getting them to actually try and use it in a practical task I think is really important. Yeah, that that’s my sort of number one thing. You’ll learn way more by putting it in front of people then you’ll learn by reading around and looking at what other people have done I think.

Drew: And in doing that you’re obviously going to get feedback on that documentation. Do you have any suggestions for how you would approach fixing things based on that feedback? Is there anything specific that you’d be looking for in the feedback to understand how well your documentation had worked?

Amy: Yeah, I mean there’s a few things I think to watch out for. I think it’s is really important to separate preferences and people perhaps not liking the documentation from people actually not being able to use it. So I think any task-based testing with documentation is better because it might be that actually somebody complains their way through an entire guide but they still complete the task that you’ve set them. That’s not to say that that doesn’t matter. If they wanted to do the thing but they actually hated the process, then you of course need to take that into consideration. But I think that some people and I’m probably one of them just can’t help themselves and will start, especially if it’s a content designer, I think we can’t kind of ever quite put that content design mentality aside.

Amy: So I definitely have a tendency to start live editing stuff if I’m supposed to be participating as research candidate on it. So I think yeah, separating preference from actual kind of usability and blockers is quite important. I think that making sure that your really interrogating the need to make changes and to update things. I think sometimes if somebody is particularly engaged with a design system, depending on the sort of person they are, they can be quite vocal about how they think it could be better or how they think that how they would’ve done it perhaps or how it could be clearer. I think it can be quite, especially if you’re sort of trying to build Goodwill and you’re in that early stage with the design system, it can be quite tempting to just immediately respond to that feedback and do what they say or try and make it clearer.

Amy: But then you can end up building it too far in the direction of the loud minority and I think actually really saying like how many people have got this problem? What evidence do we have that this isn’t working for people? And does that warrant a kind of update? I think yeah, trying to resist the temptation to respond to every comment and bit of criticism that you receive is quite important too, yeah.

Drew: I suppose I’m a common theme here with design systems that enable consistent design and give you a reusable resource in your design and about accepting contributions that make those designs stronger and implementing accessible design choices and documenting your design to make it easy to access and use. It really all comes back to sort of inclusion, would you say that was fair that including people as much as possible?

Amy: Definitely. Yeah. I mean I think that a good design system is a representative design system and I don’t think it’s possible to achieve representation by acting on people’s behalf. I think you really need to try and involve people in the process as much as possible. I think often for people working on design systems and certainly it was the case for us at the GOV.UK design system, you tend to be one step removed from your organizations end users. So if you think for the GOV.UK design system, the people that the design system is ultimately there to serve are members of the public and citizens and people using government services. But we in our team, we’re really working directly with those people. Most of the time our direct users are people working in the civil service. So making sure that you’ve got really strong feedback loops between your direct users and then their users to ensure that it’s representative I think is really important and I think that’s where inclusion comes in and yeah, I completely agree. I think it’s a really central thing, like I can’t imagine how you could build a successful design system without a focus on that.

Drew: Is there anything else that you’d like to share with us about your work on the GOV.UK design system?

Amy: I think my sort of main takeaway from working on it is that, I hate using the word physical when I’m talking about anything on the web, but the the visual representation of a design system I think can end up being the thing that we all get really fixated on. We look at how it’s coded and we look at how it’s organized and what it looks like and how it’s documented and what the design is. I think that obviously that stuff is really important. I think that it’s the thing that you can look at and show people and share. So it’s easy to see why we get fixated on that. But I really think that the most important factor of it is the people. I think that having inclusive processes and making sure that you’re kind of fostering safe discussion spaces and that you’re giving people an opportunity to get involved in the work and to participate and feel motivated to help you with it and to feel this sense of ownership over it.

Amy: I think all of that stuff is really important and all of that stuff really happens outside of the code and outside of the documentation. So yeah, I think my key takeaway from working on the GOV.UK design system is how much of it is really just people work and not really anything to do with guidance and code.

Drew: Here’s at Smashing we’re all about learning. So what have you been learning lately?

Amy: Lately I’ve been learning a lot about productivity and focus. I think definitely towards the end of last year I became aware that I was really plate spinning and luckily I don’t think I smashed any of those plates but I found myself kind of working quite chaotically and moving around lots of different projects and saying yes to everything. So this year is the year that I want to really improve my focus. So I’m trying to learn a little bit about mindfulness and organization and how to say no to things strategically so that I don’t get overwhelmed and too distracted. I’ve started bullet journaling so I’ve really become the full 2020 cliche at this point. So that’s what I’m learning at the moment.

Drew: If you dear listener, would like to hear more from Amy, you can follow her on Twitter where she’s @Amy_Hupe or find her on the web at amyhupe.co.uk. Thanks for joining us today. Amy, do you have any parting words for us?

Amy: Stay cool. What? Why did I say that? Just came out, it just came out.

Smashing Editorial (dm, ra, il)

What Is Tech Debt and How to Explain It to Non-Technical People?

Technical debt: explained.

Probably anyone who is connected to software development has heard about technical debt. But both salespeople, account managers and probably even CEOs rarely understand what tech debt means, how to measure technical debt, as well as the necessity to pay it. According to Claranet's survey, 48% of 100 IT decision-makers from the UK, say that their non – technical coworkers have no idea about the financial impact of tech debt.