<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Justine on Medium]]></title>
        <description><![CDATA[Stories by Justine on Medium]]></description>
        <link>https://medium.com/@wigglykoala?source=rss-2ef1e91e13d9------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*UTqvV5628ghYLaeZ544w6g.jpeg</url>
            <title>Stories by Justine on Medium</title>
            <link>https://medium.com/@wigglykoala?source=rss-2ef1e91e13d9------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 22:42:53 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@wigglykoala/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[Flavours of Design]]></title>
            <link>https://medium.com/code-enigma/flavours-of-design-9b45e3f643f4?source=rss-2ef1e91e13d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/9b45e3f643f4</guid>
            <dc:creator><![CDATA[Justine]]></dc:creator>
            <pubDate>Wed, 24 Jun 2020 11:38:28 GMT</pubDate>
            <atom:updated>2020-06-25T09:34:12.854Z</atom:updated>
            <content:encoded><![CDATA[<h3><em>“What type of designer are you?”</em></h3><p>It comes up in every interview. I’ve missed out on jobs because they didn’t know where to put me in their company. They wanted me, but I didn’t fit into their boxes. (Their loss).</p><p>As Head of Design at Code Enigma, I never want to put anyone in a box.</p><p>Code Enigma is a very technically-savvy company. We’re conscious sometimes we speak in t3ch sp33k and others might not understand us. When I joined, design was fledgeling. We hadn’t done much design work of our own, even though we’d had designers for years. Normally, they would collaborate with external agencies like Stuff and Nonsense to create designs and we’d implement them.</p><p>As the company grew, things changed. We started designing for our clients. We became a profitable team. We’re busy, but we’re not complete. There’s a gap.</p><p>Between the two of us, Aaron and I cover a lot of design base, but we can’t cover everything under the umbrella of “design”. It’s a big umbrella. There are a lot of articles about ‘flavours’ of design on the internet, from architecture, packaging design, communication design and motion design.</p><p>There’s a good diagram which sparked debate a few years ago. Is the diagram complete? Does X cross over Y? I’m not reigniting that argument. I’m looking closer at the parts of design we do and <em>want to do</em> at Code Enigma.</p><figure><img alt="Venn diagram of all the different job roles placed under the design umbrella, it’s chaotic!" src="https://cdn-images-1.medium.com/max/1024/0*T8j313QRqoFviNY4" /></figure><h3><strong>We’re Unicorn designers</strong></h3><p>As much as I don’t want to put people in boxes, we have to assign roles and responsibilities in our team and company. We do this to understand what we’re doing. As there are only two of us we’re able to utilise and overcome our respective strengths and weaknesses.</p><p>We don’t do much motion design and I’m sure we won’t have any architectural jobs coming up. It’s safe to say we rotate within a set of flavours.</p><p>As a relatively small web agency specialising in Drupal, we focus on digital design and disciplines under that umbrella. We’re both good at brand design and both come from a traditional print background. We’re able to create marketing materials for our awesome marketing manger. We do information architecture and user testing, we write code, we make things look aesthetically-pleasing and, most importantly, we solve problems.</p><figure><img alt="A venn diagram showing technology business and design with UX being the center of it all" src="https://cdn-images-1.medium.com/max/1024/0*u_bOzsc7fFJSsbKx" /><figcaption>Caption: We call this our trifecta of design, we cover a lot of bases as a team of two.</figcaption></figure><p>As a team, we believe our role is to gather research and stories to test, validate and refine solutions to our clients’ problems. Our job is to create ease-of-use. We help our clients delight their users in a way that is beautifully simple and effective. We do this under the constraints of being an agency, having a budget and a deadline.</p><p>Together we’re a pretty good team! Currently, I look after the business side of things; from our team goals and analytics to ensure we produce effective code, create robust solutions and that everyone is aware of how to do so.</p><p>Aaron is front and centre when it comes to design. He rebranded the entire company. Everything from the website to mugs and reusable water bottles. He creates thoughtful designs that solve our clients’ problems with usable solutions. He provides value for money and doesn’t over-complicate things.</p><p>We’re close to our developers. Together we turn our designs into Drupal themes. Most of them don’t really like CSS; it’s like showing a vampire a beautiful sunset and they run away, melting. We get it. They’re backend devs for a reason and they don’t have to like it. Just like we’re not so keen on playing with Drupal’s theming layer. That’s why teamwork is key at Code Enigma.</p><p>Though we <em>can</em> do all of these things, we feel there are areas where we lack strength. We’re strong believers in being T or Pi shaped designers (comb-shaped feels like too much, for us). We don’t hide this fact from clients; content design is a flavour we both appreciate, but cannot do it ourselves! (You should see the first draft of this blog post before the awesome marketing manager worked her magic on it).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*ORGIzhMcgm4E8gBv" /><figcaption>Source: <a href="https://twitter.com/lara_hanlon/status/882887063267311616?s=21">https://twitter.com/lara_hanlon/status/882887063267311616?s=21</a></figcaption></figure><h3>It’s clear there’s a gap.</h3><p>We’re missing someone who really <em>gets</em> frontend performance. The beauty of code. We can both do it, but there’s room to improve. We’re passionate about using only HTML and CSS when we can, accessibility is high in our principles and we’re working hard to improve.</p><p>If you feel like you’d be the chocolate in our Neapolitan, the Huey to our Duey and Louie, then we want to make wonderful things with you!</p><p><a href="https://content.codeenigma.net/index.php/asset/1:designer-job-ad">See our job description and contact us here.</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=9b45e3f643f4" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-enigma/flavours-of-design-9b45e3f643f4">Flavours of Design</a> was originally published in <a href="https://medium.com/code-enigma">Code Enigma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Mind yourself, love.]]></title>
            <link>https://medium.com/code-enigma/mind-yourself-love-c1192e0379d8?source=rss-2ef1e91e13d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/c1192e0379d8</guid>
            <category><![CDATA[women-in-tech]]></category>
            <category><![CDATA[women]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[confidence]]></category>
            <category><![CDATA[mindfulness]]></category>
            <dc:creator><![CDATA[Justine]]></dc:creator>
            <pubDate>Wed, 06 Mar 2019 10:25:51 GMT</pubDate>
            <atom:updated>2019-03-07T18:03:50.519Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XX7TwQsEcvyeKwJqfG2RdA.png" /><figcaption>Lego Wonder Woman flying her invisible plane in the sky</figcaption></figure><p>I delivered the first talk of the opening night of <a href="https://www.wespringforward.com/">Spring Forward</a>, and wanted to share it in blog format. It’s my Wonder Woman tool kit, filled with things to help you feel good about you.</p><p>First and most importantly, I really believe that having confidence is to <strong>have belief and faith in yourself</strong> and that can be really hard to do when you don’t know where to start.</p><p>One of the first steps in having faith in yourself, and showing it to those around you, is to learn your own strengths<strong> and</strong> weaknesses. I learned a lot about myself from reading <a href="https://chimpmanagement.com/books-by-professor-steve-peters/the-chimp-paradox/">The Chimp Paradox</a> by Steve Peters. It’s about how everyone has an inner chimp who is emotional and likes to make a lot of noise when feeling distressed.</p><p>Understanding that emotional responses were caused by my inner chimp (Nora) meant that I could learn how to control them better; sometimes it meant shouting back at her, and that’s why naming your chimp is important. Sometimes it meant letting her tire herself out, so taking myself to a safe place, with people I trust, and letting it all out.</p><p>By being in control of Nora, when I do have something to say, I know it isn’t an emotional or triggered response, but something to have faith in, because it’s me speaking and not my emotions. This alone gives me the confidence to speak up in situations I’d normally have kept quiet in.</p><p>It took time to know when to speak up or ask for help. I found myself screwing my toes up in a meeting or fixated at the computer screen fretting over a problem I couldn’t fix. I actually made myself very sick when I was stuck on a big project.</p><p>Learning how your body feels in tense situations is invaluable, so <strong>check in with yourself, regularly. </strong>Not only listening to your inner chimp but your whole body. Preempting the pesky chimp’s behaviour means you can position yourself well in awkward situations. I found meditation really useful here. I use the Headspace app to spend just a few minutes a day checking in with myself, listening to my body, what hurts or feels tense. They are signs you’re not telling yourself how you really feel and that you may need to stop and readdress things.</p><p>Check in with others around you too. They might see you doing things you only do when you’re anxious. Be sure to ask questions when you don’t understand something. <strong>Be comfortable with saying “I don’t know”.</strong> I don’t know but I can find out if you give me 30 minutes. I don’t know, but please can you show me. <strong>Not knowing does not make you weak.</strong> It shows courage. It’s rare and employers value someone who admits when they don’t know something. Learn to be comfortable saying I don’t know.</p><p>Also, “<strong>No.” is a sentence</strong>.</p><p>I was always told you should <strong>communicate more than feels natural,</strong> to be heard. And from experience, I can confirm it’s true. This still happens to me today, I can say something and it will go ignored, then someone — normally a man — will repeat the same thing minutes later and they get the praise. If you find this happening to you, and it’s hindering your career, then you do have the power to speak up — because you’re in control of your chimp. You know you aren’t being emotional and it is important you get the credit for the idea.</p><p>But<strong> sometimes you do have to let it go. </strong>Letting someone take one idea from you may open your path to a better idea. Embrace that and learn from your previous mistake. Over-communicate everything. You need to be able to prove you said it first, write everything down, tell more than one person. A presentation is more powerful than you think it is.</p><p><strong>Back things up with evidence </strong>or try what you want to do in your own time first, then ask for time to do it more in-depth. It truly sucks that we have to do that, but an hours’ homework might make all the difference.</p><p><strong>Learn to tell great stories. </strong>Share evidence you have with real stories, your feelings, be open and raw. There is great power in vulnerability. If your presentations are relatable and personable then they’ll hit home.</p><p>Remember to check in with yourself so you know <strong>when to dig deep and when to take a break</strong>. If you don’t feel like you’re being heard after providing the evidence or digging deep and giving that hours’ homework, you can get another job. <strong>YOU ARE WORTH MORE</strong>.</p><p>Even though you have your chimp under better control, <strong>you will get emotional </strong>and that’s ok. Emotions show that you care.</p><p>Ask yourself: <strong>will this be important in 2 minutes? 2 days? 2 years?</strong> This will help you ground your emotions. <strong>You might need to be angry </strong>because it affects 2 years of your life, so don’t hold that in, but try not to let your chimp control your anger, show your passion, your fire.</p><p>Being angry about something that’s going to be uncomfortable for 2 days or 2 weeks isn’t worth it and it’s probably your chimp talking.</p><p><strong>Find your tribe.</strong> People you look up to. They don’t even need to know you exist. Follow their footsteps, learn about them and how they got to where you want to be. Ensure you have people you can show your chimp to.</p><p>Your tribe must have people that believe in you when you don’t. People who will guide you somewhere when you can’t see the road in front of you. There’s also a lot of research showing women who have a tight tribe of 3 or 4 female friends to confide in and bounce ideas off will succeed more than those with more men in their tribe.</p><p>Now I come from a web development background so for a long time a lot of my tribe was male. I found two key women to confide in and they boosted my confidence for me when I couldn’t.</p><p>You will feel like you don’t belong and <strong>everyone else is feeling the same</strong>. The sooner you know that, the sooner you can be comfortable with it.</p><p>Always <strong>say please and thank you</strong></p><p>If you’re unsure about doing something, <strong>do it and say sorry later.</strong> It’s very likely you won’t have to apologise. There’s no reason to say sorry when asking for help. The only time to say sorry is if you’ve hurt someone’s feelings. Because you want some of their time to do your job better, isn’t anything to apologise for.</p><p>If you feel intimidated by a situation then I recommend <strong>running into the nearest bathroom</strong>. Seriously. This is where mantras boost your confidence. Saying “I can do this” or “I am important” over and over. I used to say that walking up the three steps into the office of my last job. Each step a word. I. Am. Important. Those steps meant something to me, that literally helped me start my work day on the right foot.</p><p>For a greater boost, I love a power pose. Social psychologist, Amy Cuddy has a great Ted Talk on this. I strongly believe <strong>taking two minutes can change your mood </strong>and can help you to fake it until you make it.</p><p>There’s a pose called <strong>the Wonder Woman pose</strong>. Stand with your feet just over hip-width apart. Put your hands on your hips and lift your head and chin up slightly, like there’s a string pulling up from your spine. Now, if you were to stand like this for two minutes your cortisol levels would drop, reducing your stress. Testosterone levels, the power hormone, would go up and you would feel more confident. There’s science behind it, it’s clever stuff, believe in it.</p><p>Above all: keep doing it. <strong>Keep making little changes.</strong> Keep fighting for each 2 minutes, 2 weeks, 2 years.<strong> </strong>Keep focussing on you<strong> </strong>and you will make it. <strong>You will find that faith in yourself.</strong></p><p>You can follow <a href="https://twitter.com/codeenigma">Code Enigma</a> on Twitter.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c1192e0379d8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-enigma/mind-yourself-love-c1192e0379d8">Mind yourself, love.</a> was originally published in <a href="https://medium.com/code-enigma">Code Enigma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[New Adventures Conf]]></title>
            <link>https://medium.com/code-enigma/new-adventures-conf-f8e81c491474?source=rss-2ef1e91e13d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8e81c491474</guid>
            <category><![CDATA[design-process]]></category>
            <category><![CDATA[web]]></category>
            <category><![CDATA[design-thinking]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[designer]]></category>
            <dc:creator><![CDATA[Justine]]></dc:creator>
            <pubDate>Mon, 18 Feb 2019 10:12:50 GMT</pubDate>
            <atom:updated>2019-02-18T11:41:39.019Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>New Adventures Conference 2019</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DVhCFPjwG8wxAFdyx2rcvQ.jpeg" /><figcaption>The stage going up for New Adventures conference.</figcaption></figure><h3>My thoughts</h3><p>I remember learning about NAConf in 2013, thinking “I’ll go next year” and feeling I’d missed out when I heard it was to be the last. I had to go when Simon and Geri decided to run another; the line up looked great and there were workshops I really wanted to attend.</p><p>Jeremy Keith was first and, frankly, his words made my head and heart listen intently. Jeremy compared the web to architecture and showed us the elements we use in our web-world. Architecture is a metaphor I use too, but he took it to a new but relatable level, introducing <a href="https://jods.mitpress.mit.edu/pub/issue3-brand">pace layers</a> (instantly making me want to be a member of <a href="http://longnow.org/">The Long Now Foundation</a>). These show how the components in any system are different sizes and change differently, at different speeds. Working with the layers means we make a better product, one that importantly, fails well. If you ask my feelings on Javascript, you’ll find they are the same as that on fast fashion, so this part resonated with me.</p><p>Jeremy went back to the architect metaphor with consideration to pace layers and how we should look at <em>how well</em> things fail, <a href="https://www.w3.org/DesignIssues/Principles.html">the Principle of Least Power</a>. Consider software; most of it works well, but what’s important is how well it fails. It’s uncommon for anyone other than a sysadmin to consider how well things fail. It’s about selecting things that don’t just work well, but also fail well.</p><p>Jeremy told a harrowing story about how seventy-five construction workers died because of an engineer’s decision, so now, when graduated from an accredited engineering program, engineers take an oath and wear a special <a href="https://en.wikipedia.org/wiki/Iron_Ring">iron ring</a> as a reminder of their responsibilities to the world, and this makes the word engineer too precious for us, we who tinker and enjoy playing in the faster layers of the web. Maybe this makes us the construction worker, the builder, the one who gets down and dirty with the materials of the web. As the girlfriend of a builder, I’ve often considered our work similar. We both build resilient, performant, accessible and beautiful structures. I’m proud to be a builder of the web; someone who rolls their sleeves up and gets stuck into the fundamentals, the slower pace layers.</p><p>I knew Clare Sutcliffe co-founded Code Club, but I didn’t know how it became successful. The hard work and determination to get it running is so motivating. I joined Code Enigma to mature their design team and at times I feel I’m out of my depth and the wrong person for the job. When I was listening to Clare I realised I can do it — <em>I am doing it</em> — I just hadn’t noticed. Clare became a CEO by believing in a cause. I know I’m helping steer our design team in the right direction by believing in the value of design. Believe in what you are doing, and just do it.</p><p>Next was Josh Brewer his talk on demystifying design covered that the misconceptions of design — <em>making things look pretty</em> — is still alive, even though many designers now have a seat at the table. “Good design is good business” and this supported what Aaron and I learned at Design Leaders conf when we discovered the Mackinsey report on the <a href="https://www.mckinsey.com/business-functions/mckinsey-design/our-insights/the-business-value-of-design">business value of design</a>. Josh reminded me that a design mind works differently to an analytical mind and designers need to over-communicate that magical time between receiving a brief and coming up with a design, even if that might be hard for designers to do, because for them the process isn’t linear.</p><p>Jessica White reinforced everything Josh said about communication; how we should force ourselves into development teams, to understand their pain-points, their happy moments, their life. If we want to do this for our users, we should be doing it with our developers. I found this talk confirming my beliefs; I’ve gone full circle from design to frontend dev and Drupal site building and back to design again. I get it, I get the pain devs feel and I don’t think it’s much different to the pain designers feel. Constrained creativity and inconsistent processes or core values are key pain points for both of us. My favourite phrase from this talk was “<em>tiny acts of rebellion</em>”, designers sitting with the devs, asking questions about all the things, shaking it up. A lesson for all.</p><p>Ashley Baxter may just be my new woman crush. She hadn’t been in my bubble until the conference, I knew of With Jack, the freelancer insurance people, but not how it started and much like Clare’s talk, this woman knows what she wants and is going to get it. Ashley’s tact is different to Clare’s because she’s going it alone and happy to do so. She’d rather take it all on herself than pick the wrong people. She’s clearly an ideas person, having many good ongoing side projects. It was only trying to simultaneously do them all that made her realise she wasn’t going to progress <em>any</em> of them, so she focussed on With Jack.</p><p>Being focussed on her customers, responding to their needs, purposely being a small business, a real person at the end of the email, Ashley built With Jack into a business that does more than provide insurance to freelancers but helps them grow their businesses.</p><p>I thought at lunchtime the inspiration would end at the bottom of my brown paper bag but no, Women in Notts did a lunchtime takeover and there were some insights from dealing with imposter syndrome, feeling different because you look different, to building organic websites — using just the slower pace layers of HTML and CSS and the benefits of eating porridge at lunchtime. The people who dared stand up and speak were great and it was comforting to see everyone welcome and applaud them.</p><p>After this it was time for Brendan Dawes. Let me be clear here, I love Brendan Dawes. He was on my radar at university when I was learning about Paul Rand, David Carson, Erik Spiekermann, Neville Brody and Hillman Curtis. Brendan is an inspiration for me, he makes me feel bad for not playing enough and not embracing my creativity more.</p><h3>Justine Pocock on Twitter</h3><p>My head is brimming with fun/useless ideas of things to make with a 3D printer since @brendandawes talk at @naconf and Aldi are emailing me to tell me 3D printers are in this weeks specialbuys... https://t.co/OvbmsTtGrR</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/0*2rRWkTQxPAnObRtR" /><figcaption>Brendan Dawes diagram illustrating how design, art and technology interact for him.</figcaption></figure><p>Honestly, this is the best bit of Brendan&#39;s talk for me: “‘You can’t do this like that’ ‘sod off’” Create to criticise, embrace your creativity, try the untried and don’t let anyone stop you.</p><p>Sometimes the process is messy, don’t get hung up on that. I’ve got lots of ideas for creative projects I can do within my labs time at Code Enigma. I’ve even pulled out my <a href="https://egg-bot.com/">eggbot</a> and finally got it working, after 8 years, because of this talk.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lor8mOz-cThR91RvncYD2Q.jpeg" /><figcaption>Brendan Dawes talking about his creative process on stage</figcaption></figure><p>Helen’s talk reminded me to test my assumptions, and understand the technical privilege we have as people who work with the web every. single. day. 1337 H4x0r sp33k might be a second language to us, but to the people we build websites for, they can struggle with a plethora of obstacles we take for granted. We’re becoming more inclusive with our design and development decisions at Code Enigma, but it’s an area we can continually improve on. There are a lot of helpful resources, but nothing beats meeting the user face-to-face.</p><p>Naz Hamid again spoke about building bridges into other people’s bubbles; anticipating the room and understanding the needs of others. He used the terms “Design by inclusion” and “design for inclusion”. Including people in the design process and ensuring that process designs for all. This talk on diversity and inclusion turned the table round as to why designers need a seat at the table, not to be heard but to listen (and this backed up other talks of the day).</p><p>Ethan Marcotte ended the conference following the theme of responsibility and inclusion. Making all my senses tingle. I still don’t really know how to sum up the talk, but I’m very grateful I was able to hear it, for the first time. To me, it feels that when the rest of the world wide web gets to hear Ethan’s talk, it will change the way we all work. I know I’ve started to consider my actions more. The feeling of how his words hit my stomach and made my eyes tear up and take my breath away hasn’t left me, and I hope you get to feel it too.</p><p>The Era of Engagement needs to end, and the Era of Responsibility needs to start. Just like how Ethan’s <a href="https://alistapart.com/article/responsive-web-design">responsive web design</a> article changed the web 9 years ago, I see responsible web design doing the same.</p><p>The whole conference was thought-provoking and asked bigger questions about the digital world that I hadn’t considered. It was great to break out of my normal self for a day and listen to other people’s perspectives on the future of design and tech.</p><p>I really hope that New Adventures comes back next year.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8e81c491474" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-enigma/new-adventures-conf-f8e81c491474">New Adventures Conf</a> was originally published in <a href="https://medium.com/code-enigma">Code Enigma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Always under construction]]></title>
            <link>https://medium.com/code-enigma/always-under-construction-1ef8f2fea515?source=rss-2ef1e91e13d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/1ef8f2fea515</guid>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Justine]]></dc:creator>
            <pubDate>Fri, 08 Feb 2019 11:46:28 GMT</pubDate>
            <atom:updated>2019-02-08T11:46:28.296Z</atom:updated>
            <content:encoded><![CDATA[<h4>It’s easy to assume an agency like us will take a big project, deliver a site and move on, but we show clients that a website is continually under construction and improvements can always be made.</h4><p>In 2007, the “Global Capacities Alert &amp; Response” (GCR) department of the World Health Organisation (WHO) set up a Learning Management System (LMS) with Moodle. In 2015, they added Drupal to optimise the distribution of training packages and to host communities of practice. In doing so, the learning platform became “<a href="https://extranet.who.int/hslp/">Health Security Learning Platform</a>” (HSLP) that provides content for learners and training packages for trainers.</p><p>All members are identified with the Open ID ADS (Application Directory Service).</p><p>In order to respond to expanding demand on the use of the site by both internal and external users, they needed our help to make some improvements.</p><p>We met with the HSLP team in Lyon last year and had two days of on-boarding, understanding the pain points of the site from the eyes of the maintainers was our first priority because there were development issues the team couldn’t do, such as integrating sign-on and applying security updates.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IOjkIsO2DzUcDCp8Gjfuyg.png" /><figcaption>The original homepage lacked navigation making it hard to find the content.</figcaption></figure><p>We learned about how the HSLP programme is only a small part of GCR and when outbreaks of things such as Ebola then resources and budgets are quickly shifted around so the learning platform doesn’t see consistent development. Understanding how the department works were fundamental in what steps we made next. We knew we needed to keep the HSLP secure and stable as a top priority but in just two days we have a very long list of possible changes we could make to the site and maximum impact in a short amount of time was needed to help the programme get more budget allocated to it.</p><h3>Information architecture and a new header</h3><p>The navigation and homepage became our priority.</p><p>The information architecture was there on the Drupal side. The site had three distinct areas, but you could only reach them via the slideshow in the centre of the screen. The Drupal menu structure provided us with a clear path. Half the task was getting the Moodle menu to follow in the same way.</p><p>We tweaked the top level menu items to sound proactive, depending on the type of user. We identified two types: students who needed to learn and teachers needed to build training courses, both user roles needed to connect and share findings.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*nHzgfYQHOAJaqGWM9OLLaw.png" /><figcaption>Part of the Design decisions PDF created for HSLP to present to the rest of the GCR team.</figcaption></figure><h3>Topics</h3><p>In addition, a new section called ‘<a href="https://extranet.who.int/hslp/?q=content/browse-topic">Browse by topics</a>’ has been added to show online courses and training materials grouped by a specific topic.</p><p>Each topic contains a big picture to add a visual clue what the topic is about, content is then divided by ‘Learn’ and ‘Build’. Some topics have an extra banner at the bottom where users can find more information and this is one of the areas we’re looking forward to improving further.</p><p>With this, users can reduce the time searching courses through the website, and they can see all the content on the same page, providing another journey for users to get to the information they need.</p><h3>Single sign-on</h3><p>One of the main objectives was the implementation of a Single Sign-on in the website.</p><p>Until now, WHO was using OpenID as authentication server but it was causing tons of headaches in the support team because the account providers<br>are WIMS, ADS and Paho, so they were always having to help with people not knowing how to login and passwords…</p><p>To solve this issue, we remove OpenID and implemented <a href="https://en.wikipedia.org/wiki/Active_Directory_Federation_Services">ADFS</a>, as they were fed up with the different types of users not being able to access different platforms. There is currently a separate section for profile management without any synchronization (Drupal and Moodle) and there were remaining glitches when registered members pass from one platform to another with OpenID.</p><p>With ADFS, users have a place where they log in but can do so with any of the previous account providers, making the information and user journey more consistent.</p><h3>Homepage and Calls to Action</h3><p>The final step was to look at the homepage and improve the Calls to Action further. A tagline explaining what you can do on the site and four large CTAs meant the website suddenly felt alive.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cYEmF8ZL3CBAJtErEyuyVA.png" /><figcaption>Removing the slideshow meant we had room for some impact.</figcaption></figure><h3>Outcomes</h3><p>We feel we’ve managed to create a renewed sense of enthusiasm and lease of life within the HSLP team, within a limited budget. With a site that is easier to navigate around and learn from, we’re not finished yet, but we’re making leaps of progress with making the HSLP a place where public health officials want to learn about Health Security.</p><p>We’re looking forward to helping WHO with the next phase of this important and empowering website.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=1ef8f2fea515" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-enigma/always-under-construction-1ef8f2fea515">Always under construction</a> was originally published in <a href="https://medium.com/code-enigma">Code Enigma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Birthday presents needed…]]></title>
            <link>https://medium.com/code-enigma/birthday-presents-needed-8a7b9966e0dd?source=rss-2ef1e91e13d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8a7b9966e0dd</guid>
            <category><![CDATA[content]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[web-accessibility]]></category>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Justine]]></dc:creator>
            <pubDate>Fri, 11 Jan 2019 11:15:39 GMT</pubDate>
            <atom:updated>2019-01-11T11:15:39.123Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*xu2Ya-tWH0X-Qtm7h_C5JA.jpeg" /><figcaption>A woman stands with covered eyes waiting for another woman to present her a neatly wrapped gift tied with a delicate bow</figcaption></figure><p>So, it’s your mum’s birthday and you want to show her you love her so you decide to buy her a present.</p><p>Your first step isn’t to buy the gift bag for it to go in; that’s counterproductive. If you did that first, you’d limit yourself and would probably spend longer than you planned looking for a present that fits into the bag, or buy one that doesn’t fit, looks awful and makes your poor mum think you don’t love her enough to get her something nice.</p><p>Your first step is, of course, to buy the gift. You think of a few things that you know she will like and you narrow it down to one item, that you can afford and will be available in time for her birthday.</p><p>Now your next step is to choose how to wrap it. Now you know what you’re wrapping, you can find the right box/bag/paper to cover it sufficiently.</p><p>Here’s what I’m saying:</p><p>Showing your mum you love her (the big picture)</p><p>The gift (content)</p><p>Wrapping it (design and development)</p><p>Bethany Joy (<a href="http://bethanyjoy.org/">http://bethanyjoy.org</a>) spoke at UX Oxford last night about how content is equally as valid as the design and development of a website and how getting these three right gives you the trifecta of happy websites.</p><p>Regardless of a client’s specific goals, always consider the big picture. All websites follow the basic principle that the website is one of several communication tools used to get closer to set goals. To get closer to your goals, you need others to make moves and take action. Content guides the user to take the right actions, which helps the client get to their end goal.</p><p>Bethany’s process is:</p><ol><li>Big picture</li><li>IA/sitemap</li><li>Draft content</li><li>Functional planning/scoping/naming things</li><li>Designing (pages or components)</li><li>“Final” designs (something for a client to see)</li><li>Dev</li><li>Testing and tweaking</li></ol><blockquote>She says:</blockquote><blockquote>“What is surprising is the number of times that time and money gets wasted because companies don’t approach the creation of their new website in the best way, meaning that their websites aren’t as successful as they could be. Far too many businesses prioritise design and development over content — in other words, they care more about what their site looks like and how it works than they do about what it says.”</blockquote><p>Thank you to Bethany for an eye-opening talk!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8a7b9966e0dd" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-enigma/birthday-presents-needed-8a7b9966e0dd">Birthday presents needed…</a> was originally published in <a href="https://medium.com/code-enigma">Code Enigma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Uniting Inclusive Design and Accessibility]]></title>
            <link>https://medium.com/code-enigma/uniting-inclusive-design-and-accessibility-94288e44e9e5?source=rss-2ef1e91e13d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/94288e44e9e5</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[equality]]></category>
            <category><![CDATA[web-accessibility]]></category>
            <category><![CDATA[a11y]]></category>
            <category><![CDATA[inclusive-design]]></category>
            <dc:creator><![CDATA[Justine]]></dc:creator>
            <pubDate>Wed, 05 Dec 2018 09:27:38 GMT</pubDate>
            <atom:updated>2018-12-05T12:22:54.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GQvUVtk00mFX6tArYh8dSQ.jpeg" /><figcaption>THIS THEORY IS…There is always more learning and knowledge sharing to do when it comes to Inclusive design. Accessibility is an outcome. Inclusive design is a process. (NIST Digital Collections)</figcaption></figure><p>Whether your website will reach two, or two million people, the goal is for it to be usable by everyone who comes in contact with it.</p><p>That’s why you should consider the Inclusive Design methodology when you’re creating a new site or digital platform.</p><p>According to UX Planet*, inclusive design, “<em>Enables people with diverse characteristics to use your product in a variety of different environments.</em>” This means that your product takes into consideration every scenario in which a user might access your site.</p><p>For example, all of the videos featured on your site should include closed captioning. That way a user watching your videos on mute while riding on a crowded train will get the same experience as the user watching your videos at full volume at home.</p><p>However, closed captioning isn’t just an inclusive design principle. It’s also a requirement if you want your site to be accessible.</p><p>When discussing inclusive design, it’s also important to mention web accessibility. Accessibility is a core value of inclusive design but the two concepts are not the same.</p><p>Here are the differences between inclusive design and web accessibility, and how considering both can help you adopt a more inclusive mindset.</p><p><strong>What’s the difference?</strong></p><p>As we just mentioned, inclusive design considers how a site will be used in multiple settings by multiple people. While accessibility means designing specifically for people with disabilities.</p><p>For example, social media platform, Twitter, introduced a night mode option for both mobile and desktop users. Night mode inverts the colours of the user’s screen so that it’s easier to view in environments with less light.</p><p>Twitter’s night mode, considers the large chunk of users who might be scrolling the platform in a dark bedroom before bed, or at the movie theatre.</p><p>This is inclusive design.</p><p>Twitter is also accessible for the visually impaired, as users can choose to enable image descriptions in their account settings. Enabling image descriptions will give users the option of adding a description (or alt text) to every image added to their tweet.</p><p>Image descriptions are important for people who are visually impaired because screen readers cannot “read” images and rely on alternative text to describe a picture to someone who cannot see it.</p><p>This option is designed specifically for individuals with visual disabilities.</p><p>Uniting inclusive design and accessibility</p><p>Inclusive design is proactive. You create something based on the possibility of use. Accessibility tends to be reactive. You redesign something to meet the needs of specific individuals.</p><p>But when you unite the two together from the beginning, or at the conception of your site, you develop a completely inclusive mindset. An inclusive mindset understands that different needs among users exist, and embraces them from the start.</p><p>Adopting an inclusive mindset begins with educating yourself on your audience and their needs. Once you’ve developed concrete user research, you can use the information to influence your product.</p><p>The sooner organisations adopt an inclusive mindset the faster we can work towards a fully inclusive and accessible web.</p><p>*<a href="https://uxplanet.org/6-principles-for-inclusive-design-3e9867f7f63e">UX Planet</a></p><p>Big thank you to Alana at our friend <a href="https://twitter.com/zivtech">ZivTech</a> for her important collaboration on this blog. It’s great to see our passion for inclusivity shared by others.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=94288e44e9e5" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-enigma/uniting-inclusive-design-and-accessibility-94288e44e9e5">Uniting Inclusive Design and Accessibility</a> was originally published in <a href="https://medium.com/code-enigma">Code Enigma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Design leaders conference: 
the best bits]]></title>
            <link>https://medium.com/code-enigma/design-leaders-conference-the-best-bits-fb0d8bdcfe05?source=rss-2ef1e91e13d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/fb0d8bdcfe05</guid>
            <category><![CDATA[customer-experience]]></category>
            <category><![CDATA[customer-service]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[communication]]></category>
            <category><![CDATA[marketing]]></category>
            <dc:creator><![CDATA[Justine]]></dc:creator>
            <pubDate>Mon, 12 Nov 2018 16:42:26 GMT</pubDate>
            <atom:updated>2018-11-12T16:42:26.131Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>Design leaders conference: <br>the best bits</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*RPiaYbMSkXsjiz9Mv6FwDw.jpeg" /></figure><p>Code Enigma’s design and marketing team met up in Dublin last week for the inspiring design leaders conference. We took so much away from it that I thought it’d be good to reflect on it.</p><p>I wrote a summary of everything I learned and soon had 11 pages of insight and actions for our own company. I won’t post those 11 pages here (because one of the things I learned was that clients like to be consulted, rather than spoken at with reams of content).</p><h3>Key takeaways</h3><h4><strong>Branding must reflect you and what you do.</strong></h4><p>Sounds really simple, doesn’t it? But so many don’t hit the mark. You have to consider if another company could fill your shoes if you packed it all in tomorrow. If they could, you aren’t offering anything unique. If you’re doing it right, then you’ll be able to recruit brand ambassadors from your client base, and doing that is a fantastic strategy to boost your success further. The key is staying true to your values and working with like-minded clients.</p><h4><strong>Know what you’re good at</strong>. Be different and stand out in the crowd.</h4><h4><strong>Clients are busy.</strong></h4><p>When you think about how little time a client has, make sure you don’t waste their time when you do have it. Go to them instead of making them come to you. They want to know what we think, but they don’t have time to go looking for it. Ask more questions. Understand their bigger picture.</p><h4><strong>Be proactive.</strong></h4><p>Make things happen. Don’t sit and wait.</p><p>We came back from the conference and talked about it until the early hours, and we’re still buzzing from the ideas we came up with off the back of everything we heard. We picked up so much that has already positively influenced how we’re going to improve our communication and our customer relationships from today.</p><p>Thank you to the organisers and speakers!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=fb0d8bdcfe05" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-enigma/design-leaders-conference-the-best-bits-fb0d8bdcfe05">Design leaders conference: 
the best bits</a> was originally published in <a href="https://medium.com/code-enigma">Code Enigma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[My trip to a11yLondon 23rd October]]></title>
            <link>https://medium.com/code-enigma/my-trip-to-a11ylondon-23rd-october-4b044290e0ab?source=rss-2ef1e91e13d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/4b044290e0ab</guid>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[user-experience]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[disability]]></category>
            <category><![CDATA[web-design]]></category>
            <dc:creator><![CDATA[Justine]]></dc:creator>
            <pubDate>Tue, 30 Oct 2018 15:06:11 GMT</pubDate>
            <atom:updated>2018-10-30T15:06:11.939Z</atom:updated>
            <content:encoded><![CDATA[<p>Last week I went to my first @a11yLondon meetup and I thought I’d tell you about it. It was the group&#39;s 19th and I’ve been meaning to go for ages, and now I’ll be going each month!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*K_jvJxSPmFEg3rBdTFn8aQ.png" /></figure><p>The meetup was live streamed on <a href="https://www.youtube.com/watch?v=1_JRI1hvSHo">YouTube</a>, but there’s nothing better than meeting new people, learning their stories and asking questions in person.</p><p>The meetup is the second biggest @a11y[location] meetup in the world. Chicago is the biggest but we’re catching them up. It’s organised by <a href="https://twitter.com/dugboticus">Alistair Duggin</a>, Head of Accessibility at GDS and sponsored by <a href="https://twitter.com/BarclaysAccess">Barclays Access</a> who do a lot of accessibility work; providing food, drinks and live captions by <a href="https://twitter.com/mycleartext">@mycleartext</a>. It was hosted at <a href="https://twitter.com/sainsburys">@sainsburys</a> and what a wonderful venue!</p><p>The first speaker was <a href="https://twitter.com/PBepey">Paul Bepey</a>, Head of Assistive Tech Strategy at the BBC. As a visually impaired person, he never thought he’d get a job like this. Coming from a programming background, he landed the role because the <a href="https://www.bbc.co.uk/aboutthebbc/insidethebbc/whoweare/mission_and_values/">BBC’s values</a> boast inclusivity, ensuring internal systems are accessible to employees. He spoke about how they have manual tests for their approved software, and they run only N-1 (latest version plus the last) for all software. When a person [with a disability] joins, they gather their requirements, software/hardware is purchased and the existing software must work with the new. That’s a lot of testing. It takes about 8 weeks.</p><p>Paul expressed concern about cloud-based software and how it’s hard for the BBC to use because an update (which the end user doesn’t know about) could break accessibility and suddenly the software isn’t usable to staff. He was talking software rather than websites, but it was interesting to think of the internal side of a11y.</p><p>Some of us suffer from migraines; Redmine doesn’t work so well with the brightness down and we can fix this. Important information fields are scattered, meaning a person squinting will move their head more to see the screen. We can ensure we don’t use repetitive patterns that trigger a migraine. If doing something like this makes our lives better then really, everyone is winning: us, our clients — we have no idea if any of these people have a disability, they could be the ones that email us instead of using Redmine because it’s easier for them.</p><p>The second talk was the AMAZING <a href="https://twitter.com/feather">Derek Featherstone</a>, my new favourite speaker. He has tutorials on <a href="https://www.linkedin.com/learning/accessibility-for-web-design">LinkedIn</a>, which the team have started working on. He made inclusive design and accessibility sound manageable, interesting and fun in a way I’ve been trying to explain for a while now! The core of his talk was about considering the extremes to make life better for everyone. Short people like me and tall people like Greg alike!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/480/1*2AjrrcdNjiRWC3loEryNIg.jpeg" /></figure><p>Andre the giant is pretty big… in this photo, he is holding a breakfast cereal for a very entertaining 1980s advert. The individual cereal is 1 inch wide, his finger pad is… a tad bigger. If Andre the giant had an Apple watch, how would he be able to use it seeing as the screen is marginally wider than that… (surely he just duct tapes an iPhone X to his wrist?).</p><p>Derek showed us many manual tests they do in their inclusive design process to ensure they are designing things correctly. Such as the Straw test — looking through a straw at the screen to resemble that of someone with low vision, the Dory test — someone who forgets, has cognitive disabilities might forget important information whilst filling out a form. They create a set of tests as projects come up depending on the user research, they then become a library of tests to use on other similar projects, these tests then get tested with real users. Nothing replaces real users, but this does reduce early mistakes. I can’t find the examples of these tests online but I will be building a set of resources we can all use.</p><p>He reiterated a designer’s favourite question over and over.<em> “Why?” “Why are we doing it? what is the problem we are trying to solve?”</em> …By asking this question the content on a page, its layout and functionality is all greatly improved because the tests allowed them to think of the extreme cases.</p><h4><strong>Accessibility is an outcome. Inclusive design is a process.</strong></h4><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=4b044290e0ab" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-enigma/my-trip-to-a11ylondon-23rd-october-4b044290e0ab">My trip to a11yLondon 23rd October</a> was originally published in <a href="https://medium.com/code-enigma">Code Enigma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Customising Indico]]></title>
            <link>https://medium.com/code-enigma/customising-indico-80318625dd1b?source=rss-2ef1e91e13d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/80318625dd1b</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[devops]]></category>
            <category><![CDATA[indico]]></category>
            <dc:creator><![CDATA[Justine]]></dc:creator>
            <pubDate>Fri, 15 Dec 2017 10:28:01 GMT</pubDate>
            <atom:updated>2017-12-19T10:32:07.833Z</atom:updated>
            <content:encoded><![CDATA[<p>I hadn’t heard of Indico before coming to Code Enigma but recently I was tasked with making an instance of Indico look like a clients main site. I found very little documentation online for customising it, so here are my findings.</p><p>Following <a href="https://blog.codeenigma.com/indico-on-a-vm-f0ce13786636">Steve’s blog post on how to install Indico on the Code Enigma VM</a> was pretty straight-forward. Although, I did forget to add an entry to my /etc/hosts file which made me think it was broken for a good few hours… but we’ve all been there, right?!</p><p>In the case of my build, it was 192.168.56.2 indico.codeenigma.com. The VM’s IP address and the base URL that I chose in the install process.</p><p>I also found that sudo su is your friend when doing anything with the build.</p><h3>Creating a theme</h3><p>CE VM shares my Sites folder on my mac so I could put the theme files there to easily access them in a text editor. I created a customisation directory inside my indico directory called indico-theme. Imaginative huh?!</p><p>Then I needed to make it visible to indico.</p><p>ssh into the VM, sudo su and symlink the sites file to /opt/indico</p><pre>ln -s /vagrant/indico-vm/indico-theme/ /opt/indico/</pre><p>In /opt/indico/etc/indico.config add to the bottom the customisation path and turn on debugging. Also you can add a logo URL, I found I couldn’t get a relative url to work, but I was probably having another moment!</p><pre>CUSTOMIZATION_DEBUG = True<br>CUSTOMIZATION_DIR = ‘/opt/indico/indico-theme’ <br>LOGO_URL = &#39;/ecmwf2013/logo.png&#39;</pre><p>Now you can tail the indigo log file<br>tail -f /opt/indico/log/indico.log <br>each time you reload the site in the browser you’ll be greeted with a list of template files that are used.</p><pre>2017–12–05 17:45:04,321 DEBUG 27ba495ba5f04dad indico.customization Customizable: core/footer.html (original: /opt/indico/.venv/local/lib/python2.7/site-packages/indico/web/templates/footer.html, reference: ~footer.html)</pre><p><strong>Customizable</strong> means what to call your file,<br><strong>Original</strong> is… well, the original, <br><strong>Reference</strong> is how to extend the file in your new templates.</p><p>You have the option of copy and pasting the original into the new theme location we made or, the preferred way, referencing the template using and extend.</p><pre>{% extend ‘~footer.html’ %}</pre><p>Once you’ve made your changes to the HTML, reload nginx and uwsgi. systemctl restart uwsgi.service nginx.service. Maybe there’s a better way, but this worked for me.</p><p>Also if you leave the project by vagrant halt and come back to it later then you might find you need to run it again to get the customisations to show.</p><h3>Useful resources</h3><p>Right at the bottom of <a href="https://github.com/indico/indico/blob/771e6eaca4a6f01182bdc34daf047f9b21c4fc1b/indico/indico.conf.sample">this sample config file</a> is all the documentation I could find on how to customise Indico.</p><p>Natalia Karina Juszka from CERN <a href="https://indico.cern.ch/event/614422/contributions/2703408/">gave a talk</a> on how to do this. Watching it back was pretty useful. Also this site is using Indico, so if you haven’t checked it out yet, this is a great example.</p><p>We’re hiring! Experienced <a href="https://www.facebook.com/drupal8/?fref=mentions">Drupal</a> or <a href="https://www.facebook.com/pages/PHP/108057495889706?fref=mentions">PHP</a> developer, EU based, work from home? Join our friendly distributed team and help us continue to make great websites! Check out our ad: <a href="https://www.codeenigma.com/build/page/expand-our-drupal">https://www.codeenigma.com/build/page/expand-our-drupal</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=80318625dd1b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-enigma/customising-indico-80318625dd1b">Customising Indico</a> was originally published in <a href="https://medium.com/code-enigma">Code Enigma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Who really designs websites?]]></title>
            <link>https://medium.com/code-enigma/who-really-designs-websites-8ea834b6fcc3?source=rss-2ef1e91e13d9------2</link>
            <guid isPermaLink="false">https://medium.com/p/8ea834b6fcc3</guid>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Justine]]></dc:creator>
            <pubDate>Mon, 11 Sep 2017 08:23:04 GMT</pubDate>
            <atom:updated>2017-09-11T12:07:57.964Z</atom:updated>
            <content:encoded><![CDATA[<h4>Hi I’m Justine, I’m the new Web Designer at Code Enigma, I feel its best to introduce myself before I get into this post because it might help you see where I’m coming from.</h4><p>I did New Media at University, mostly because my art teacher pointed out all my work had some kind of typography in it. I went to a University open day where the Graphic Design course looked a bit pants and the other course they were offering was recently renamed from New Typography to New Media… so I took it as a sign and went with it. Since then I’ve been a graphic designer making <a href="http://by-justine.co.uk/portfolio/uk-nea">massive books</a>, leaflets, signs, and the odd website which is what took me to Drupal. I then got a job as a frontend Drupal developer, turning flat designs into real life websites… and shortly after HTML designs, thankfully. And for the past three months I’ve been here at Code Enigma working on designing a wide range of sites.</p><h3>Fast forward to today</h3><p>I went to Antwerp, the home of Drupal, for <a href="https://drupalcamp.be/">Drupalcamp Belgium</a>. I was absolutely honoured to be asked to give a talk on Basic Design Principles. Which you can read about <a href="https://medium.com/@wigglykoala/basic-design-principles-for-developers-7f83f243c745">here</a>, but this blog post is about a question at the end of the talk.</p><p>The very first question was from a frontend developer who came to my talk just to ask this question.</p><blockquote>Why do designers not consider longer headings and test real content in their designs?</blockquote><p>Sometimes she gets designs from a designer where they’ve failed to test for long titles/names etc. She wanted to know why designers do it?</p><p>I’ve been there, I’ve had the same frustrations and I feel there’s not one single answer to that question, there could be a number of reasons as to why things like longer headings haven’t been tested. I thought I’d write about my thoughts on why this so frequently happens.</p><h3>The designer doesn’t understand testing</h3><p>Firstly maybe your designer doesn’t understand that designing with real content is best. Maybe they came from a time where Lorem Ipsum is fine and they usually make a design, get paid and leave. That doesn’t seem likely but if that’s the case point them to the oodles of research that says content comes first. Content is the key to your website, it’s the reason why people go there, it’s the solution to their problems. <br><a href="https://alistapart.com/blog/post/content-first-design">https://alistapart.com/blog/post/content-first-design</a><br><a href="http://uxmyths.com/post/718187422/myth-you-dont-need-the-content-to-design-a-website">http://uxmyths.com/post/718187422/myth-you-dont-need-the-content-to-design-a-website</a></p><h3>Component Driven Design</h3><p>Now I’m all for this but I think there’s one problem with how many people are doing it. The whole point of these design systems is that you design small parts of the website and not the whole page. I’m all for keeping things simple and not reinventing the wheel where necessary and that is what these systems are great for. You can clearly see what bits you have to make up your website, if nothing fits your needs, you make another.</p><p>But I feel that working from a wireframe/basic approach upwards means that real content is forgotten, you can’t see the wood for the trees with this approach, you’re not solving the problem of getting the content to the user if you’re not designing with content from the onset. Faker is great at providing different text lengths but we’ve removed the content first aspect from the design workflow. At Code Enigma, we’ve created a tool to try and resolve this, we’re still in the testing phase right now but we hope it’s something we’ll be able to release soon.</p><h3>Not enough time</h3><p>It’s possible that after solving the mound of overarching problems the client threw at them that there was just not time left in the budget to look at these things. I assume that if you ask any designer if they are 100% happy their work is finished how they wanted it to be they’d say no. There’s always something more to do, test, fix, tweak, re-do, try, test again.</p><p>And now that designers are working in HTML some of them might be working a little slower because they’re working with newer tools. Again the “Should designers code?” Question has been asked/answered millions of times, on Medium alone… so I’m not going to go there but I think lack of time is a valid consideration.</p><h3>The real problem…</h3><p>I feel that Designers are not the end of the design process.</p><p>In most cases the rest of the team believe that the designs don’t have anything to do with them. They’ve been signed off, what they see on the prototypes/PSDs/component libraries is final and shouldn’t be changed. They feel they’re job is to copy exactly what they see into a website that fits a whole load of specification they’ve been given and if it looks different then they haven’t done their job right.</p><p>I feel this mindset is wrong and it happens because the process is wrong. The design of a website should be a multi-discipline approach. The conversation with the designer shouldn’t be over when the development phase starts. The design at that point is the look and feel of the product/company combined with the findings of the UX research. The big problems are solved but not necessarily the ‘smaller’* ones. Remember websites are ‘living’ documents, things change, and like with children, they change quickly when young. The development team should be able to question why something has been done that way or be able push back on multiple instances of the same type of information.</p><ul><li><em>I’d love to be here saying that accessibility and user experience are actually the top priority, but when coming to a new project, understanding a clients problems as well as the users, their content, their goals etc and turning that into a new website is a big job and they are the first and most important tasks to be able to provide a great user experience.</em></li></ul><blockquote>Most people make the mistake of thinking design is what it looks like. People think it’s this veneer — that the designers are handed this box and told, “Make it look good!” That’s not what we think design is. It’s not just what it looks like and feels like. Design is how it works.<br> — STEVE JOBS</blockquote><p>I’ve had this type of conversation with designers several times in my role as a frontend developer:</p><blockquote>Me: “Why does this event teaser have an image with a different aspect ratio to the blog teasers? Did you want them to work differently or could we just use one of these styles to save making so many image styles that are hard to maintain“</blockquote><blockquote>Designer: “Oh yeah sure, go for blog one, its got a better aspect ratio for the profile images — but could you ensure that the image doesn’t show on mobile for events please? I don’t want the blog image to crop too much either”</blockquote><p>Woo! Instantly I don’t have to make another image style, can probably remove a whole load of CSS and I’ve learned something I didn’t pick up from the designs, that original images should be resized then cropped…</p><p>In an ideal world these things would be documented, but we’re only human, and we’ve got deadlines, things get missed. Constantly talking to each other is key! Not being afraid to push back and tell the designer that this bit of code is hard to change for the design or questioning why something is like it is a good thing. Most of the time I imagine the designer will be open to changing the design to fit the code but even if it’s a vital bit of design you’ll be able to understand their reasoning for it and probably come to some compromise to ensure a better site for the end user.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mKQLfA1z6ksZQYJJTSRUbA.jpeg" /><figcaption>Designing websites doesn’t stop at the look and feel, everyone on the project has a part to play.</figcaption></figure><p>We’ve all got a part to play in designing a website, regardless of our job titles, the buck doesn’t stop with the designer.</p><p>Ask questions, give feedback!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=8ea834b6fcc3" width="1" height="1" alt=""><hr><p><a href="https://medium.com/code-enigma/who-really-designs-websites-8ea834b6fcc3">Who really designs websites?</a> was originally published in <a href="https://medium.com/code-enigma">Code Enigma</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>