<?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 Nick Burd on Medium]]></title>
        <description><![CDATA[Stories by Nick Burd on Medium]]></description>
        <link>https://medium.com/@nickburd?source=rss-58cdc58fec6f------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*zpCIw1B9NiluzgxvsEd7Tg.png</url>
            <title>Stories by Nick Burd on Medium</title>
            <link>https://medium.com/@nickburd?source=rss-58cdc58fec6f------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Mon, 16 Nov 2026 09:28:21 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@nickburd/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[Beating the Imposter Syndrome]]></title>
            <link>https://medium.com/design-bootcamp/beating-the-imposter-syndrome-91ecadd2dd62?source=rss-58cdc58fec6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/91ecadd2dd62</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[imposter-syndrome]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[psychology]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Nick Burd]]></dc:creator>
            <pubDate>Sun, 05 Nov 2023 11:29:59 GMT</pubDate>
            <atom:updated>2023-11-05T11:29:59.733Z</atom:updated>
            <content:encoded><![CDATA[<h4>A Heart-to-Heart for UI/UX Designers</h4><figure><img alt="Beating imposter syndrome" src="https://cdn-images-1.medium.com/max/1024/1*TZ1mFOUaH27FL8jqDXO-jQ.jpeg" /><figcaption>Beating imposter syndrome</figcaption></figure><p>I want to talk about a not-so-talked-about side of being a UI/UX designer — the psychological tug-of-war we often play with something called “imposter syndrome.” Yes, you read it right. It’s that sneaky feeling whispering, “You’re not good enough” or “You don’t belong here” that creeps in just as you’re about to call it a day.</p><p>But guess what? It’s not always as it seems. Most of the time, we are, in fact, our own toughest critics. It’s like having a pesky inner editor who’s always ready to highlight our flubs and downplay our triumphs. So let’s have a friendly chat about why we’re often way better than we realize and how it’s pretty much all in our heads.</p><h3>It’s a Trap — The Imposter Syndrome Trap!</h3><p>For those of us who craft the aesthetics and usability of the digital world, imposter syndrome can feel like being stuck in a maze. We’re constantly learning and improving, and with UI/UX design being such a dynamic field, it sometimes feels like we can’t keep up. The key, however, is to remember that everyone is running this race at their own pace. Excellence is not a finish line but a path we travel with dedication.</p><h3>Grounding Ourselves in Reality</h3><p>When we feel the imposter syndrome edging in, it’s essential to ground ourselves. Let’s put down those wireframes and step away from the screen. Sometimes, we need a fresh perspective, and that can come from anywhere — nature, a museum visit, or a cup of coffee with a friend. This break from routine can reset our inner dialogue to something more positive and constructive.</p><h3>Small Wins Count, Too!</h3><p>Every pixel moved into place, every user flow mapped out, and every accessibility feature integrated is a victory. Let’s start celebrating these mini-milestones. They are the proof of progress, the breadcrumbs that show how far we’ve come on our journey. So next time you solve a design problem or get positive feedback, take a moment to bask in the glory. It’s well-deserved.</p><h3>Getting Out of the Routines</h3><p>Routines can be comforting, but they can also box us in. It’s thrilling to sometimes ditch the routine for spontaneous creativity. Participate in a hackathon, join a design sprint, or simply sketch for fun. Such activities can rejuvenate our creativity and give us a chance to shine without the constraints of our regular project boundaries.</p><h3>Talk About It</h3><p>One of the best ways to overcome imposter syndrome is to talk about it with peers. You’ll be surprised to find how many others share your feelings. These conversations can be eye-opening and reassuring. They remind us that we’re all in this together and that even the most seemingly confident among us have their moments of doubt.</p><h3>Embrace Self-Realization</h3><p>Now, for the most important part: working on self-realization. Understanding our strengths and weaknesses allows us to be confident in what we bring to the table. This doesn’t mean becoming arrogant but rather acknowledging our worth with humility and grace. Keep a portfolio of your work, reflect on feedback (both the glowing and the constructive), and remind yourself of the unique perspective you provide.</p><h3>Mind the Gap (with Learning)</h3><p>Lastly, let’s embrace the gaps in our knowledge as opportunities. No one knows it all, especially in a field as fluid as UI/UX design. So, let’s get curious! Courses, webinars, books, and all the learning tools at our disposal are not reminders of our shortcomings but bridges to our betterment.</p><p>So, dear UI/UX friends, let’s flip the script. Every time we feel the imposter syndrome bubbling up, let’s remind ourselves of the progress we’ve made and the unique skills we possess. After all, every digital masterpiece out there was once a blank canvas that a designer, just like us, bravely transformed.</p><p>Remember, we’re often so much better than we realize — it’s time we start believing it. Now go out there and design with confidence; the digital world awaits your next great creation!</p><p>Stay inspired, and until next time, keep pushing those pixels — brilliantly.</p><p><em>Did you know if you hold the “clap” button a while, that more people have a chance of seeing this story? — Find me on my </em><a href="https://instagram.com/nick_burd"><em>Instagram</em></a><em> for more content and conversation!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=91ecadd2dd62" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/beating-the-imposter-syndrome-91ecadd2dd62">Beating the Imposter Syndrome</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Embracing Inclusive Design and Accessibility in Figma]]></title>
            <link>https://medium.com/design-bootcamp/embracing-inclusive-design-and-accessibility-in-figma-55e77c313626?source=rss-58cdc58fec6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/55e77c313626</guid>
            <category><![CDATA[inclusive-design]]></category>
            <category><![CDATA[accessibility]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[design]]></category>
            <dc:creator><![CDATA[Nick Burd]]></dc:creator>
            <pubDate>Sun, 05 Nov 2023 11:29:56 GMT</pubDate>
            <atom:updated>2023-11-05T11:29:56.692Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="Be inclusive of all users, and position your Figma files accordingly." src="https://cdn-images-1.medium.com/max/1024/1*wjxcY851_seezERhTbVRoQ.jpeg" /><figcaption>Inclusivity means thinking about everyone equally</figcaption></figure><p>In the bustling intersection of design and user experience, inclusive design and accessibility emerge as beacons of responsible creation. In an era that champions diversity, designing with accessibility in mind is not merely a regulatory hurdle but a fundamental component of thoughtful, empathetic design work. Figma, the collaborative interface design tool, empowers designers to weave accessibility into the fabric of their designs from the outset. Let’s explore the whys and hows of incorporating inclusive design into your Figma practices.</p><h3>Why Prioritize Inclusive Design and Accessibility?</h3><p>Inclusive design is about creating products that are as usable as possible for as many people as possible, regardless of age or ability. By prioritizing accessibility, you ensure that your designs serve a broad audience and provide equal access to information and functionality.</p><p>Accessibility is more than a feature; it’s a social trend, a legal compulsion, and a business strategy. When you ignore it, you’re not just sidelining a minority — around 15% of the world’s population experiences some form of disability. You’re risking legal action, damage to your brand’s reputation, and limiting your product’s market reach.</p><h3>Incorporating Accessibility into Your Figma Design Practices</h3><p>In Figma, there are direct actions you can take to make your designs more inclusive and accessible:</p><h3>Start With an Accessibility-First Mindset</h3><p>The first step to inclusive design in Figma is to adopt an accessibility-first mindset. This means thinking about accessibility at every step of the design process, rather than treating it as an afterthought or a final checklist item.</p><h3>Use Figma’s Accessibility Plugins</h3><p>Figma offers a range of plugins to help check and improve the accessibility of your designs. For example, “Able — Accessibility Checker” can evaluate your designs against WCAG (Web Content Accessibility Guidelines) standards, and “Contrast” checks whether your text has enough contrast against its background.</p><h3>Semantic Structure in Components</h3><p>Organize your Figma frames and components in a logical, hierarchical manner. Naming your layers and groups clearly reflects the semantic structure and makes it easier for developers to translate your designs into accessible code.</p><h3>Consider Color and Contrast</h3><p>Ensure that color isn’t the only means of conveying information, and use high contrast between text and backgrounds. Design with color blindness in mind by using textures and patterns to differentiate elements where possible.</p><h3>Design for Screen Readers</h3><p>Use Figma to simulate how your designs will work with screen readers. Create frames that represent the flow of information, ensuring that content is logically ordered and navigation is intuitive.</p><h3>Include Focus States</h3><p>Design clear focus states for interactive elements to support keyboard navigation. This not only helps users understand where they are on the page but also facilitates navigation for those who can’t use a mouse.</p><h3>Test with Real Users</h3><p>While Figma’s plugins and tools are a good starting point, nothing beats real-world testing. Share your designs with individuals with disabilities to get feedback on usability. Figma’s collaborative features make it easy to share and collect feedback in real time.</p><h3>Documentation and Handoff</h3><p>Use Figma to create comprehensive documentation that explains your design decisions, especially those related to accessibility. Make sure to communicate how interactive elements should work and ensure that developers understand the accessibility features that need to be implemented.</p><h3>Ongoing Learning and Advocacy</h3><p>Finally, advocate for and educate about inclusive design within your team or organization. Stay informed about the latest accessibility standards and guidelines, and reflect them in your design practices.</p><h3>Conclusion</h3><p>Figma does more than create opportunities for collaboration and efficiency in interface design; it serves as a platform for advocating and implementing inclusive design and accessibility. By using Figma’s capabilities to their fullest potential, designers can create products that are not just visually appealing but also universally functional. In doing so, we build a more inclusive world, one design at a time.</p><p><em>Did you know if you hold the “clap” button a while, that more people have a chance of seeing this story? — Find me on my </em><a href="https://instagram.com/nick_burd"><em>Instagram</em></a><em> for more content and conversation!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=55e77c313626" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/embracing-inclusive-design-and-accessibility-in-figma-55e77c313626">Embracing Inclusive Design and Accessibility in Figma</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Auto deploy Webflow using Github]]></title>
            <link>https://medium.com/design-bootcamp/auto-deploy-webflow-using-github-26d6e2401c1b?source=rss-58cdc58fec6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/26d6e2401c1b</guid>
            <category><![CDATA[no-code]]></category>
            <category><![CDATA[web-design]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[webflow]]></category>
            <category><![CDATA[github]]></category>
            <dc:creator><![CDATA[Nick Burd]]></dc:creator>
            <pubDate>Tue, 25 Oct 2022 06:45:51 GMT</pubDate>
            <atom:updated>2022-10-25T06:45:51.740Z</atom:updated>
            <content:encoded><![CDATA[<h3>Auto deploy Webflow exports using Github</h3><h4>Webflow no-code, Github Repos and Heroku cloud hosting</h4><p>Webflow is an amazing no-code builder that is gaining popularity among designers and developers right now. There is a bit of controversy over the pricing model, and increases that have been happening so I thought I would share my Webflow solutions with you for basic builds.</p><figure><img alt="Webflow no-code on Heroku hosting using Github repositories" src="https://cdn-images-1.medium.com/max/768/1*T3awitytJT5-U-BtaDP5jw.png" /><figcaption>Build on Webflow, deploy with Github and host on Heroku</figcaption></figure><h4>What is a basic build?</h4><p>First off, Webflow has a few options when it comes to their pricing models. The basic builds with Webflow are without a CMS or e-commerce functionality. The hosting for this could still prove more expensive than other options and if you’re simply looking to host a portfolio site for yourself, or business card style brochure site; this could be the solution for you.</p><p>So when you’re creating your account, make sure you’re not using a theme you have purchased with these functionalities or this method will not work for you. You have to host those options with Webflow.</p><h4>Where to begin…</h4><p>When you’ve built and tested your basic Webflow project and you’re ready to publish, you have the option to export your code with Webflow.</p><figure><img alt="Export options inside Webflow’s toolbar" src="https://cdn-images-1.medium.com/max/1024/1*rxHnPsG8ZfW5cHnngdJcQQ.png" /><figcaption>Export your Webflow code</figcaption></figure><p>Prompting you to export your code, will allow you to see by piece the pages that have been created and styles associated with them. Here you can export into a zip folder to use within your own localhost on your computer.</p><p>I personally, no matter the complexity with projects, use my MAMP localhost to run them. It’s not completely necessary with the exports from Webflow as they’re simple HTML/CSS builds. But do as you wish here. You can simply just open your index.html in your browser to test and make sure you’ve still got a functional website as intended.</p><figure><img alt="Webflow code export interface" src="https://cdn-images-1.medium.com/max/976/1*cGI5S4bk2zmKAfZ-KYxchQ.png" /><figcaption>Export code with Webflow — the interface</figcaption></figure><h4>Into the hub. No, not that hub.. Github!</h4><p>Now it’s time to create a repository for your project inside my favourite platform, <a href="https://github.com/">Github</a>. In here you’ll add a new repo, and fill out the required information. If you’re concerned about remembering the process, you can always save the link to this article there, or be a bit more documented with your process and write out the steps.</p><p>Once you’ve clicked that ‘Create Repository’ button, you’re able to clone it to your machine (find a basic how-to here if you’re unsure of the steps: <a href="https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository">clone a repository in Github</a>).</p><figure><img alt="Repository creation inside Github" src="https://cdn-images-1.medium.com/max/1024/1*HT8Hj6yDm7GeodCMBl4_DA.png" /><figcaption>Creating a Github repository</figcaption></figure><p>Move all of your files from your Webflow zip that you downloaded, into your project folder you just cloned out of your repository and commit them. Make this your first commit, because we’ll be changing some items for hosting purposes and it’s good to keep versioning just incase.</p><h4>Hosting</h4><p>I chose <a href="https://www.heroku.com/">Heroku</a> for hosting. Heroku is a cloud hosting platform that is incredibly reasonable with cost, at about $7 per month or less for your dyno. These costs could go up depending on traffic, so please keep this in mind.</p><p>Create your first application within Heroku and name it accordingly. When you add your app, you’re able to select your deployment methods and you’ll want to connect your Github account here. I personally have 2 primary branches for my personal project, one for updates which are reviewed through a test link and the other is my main branch which when pushed to Github automatically deploys to Github.</p><figure><img alt="Github deployment in Heroku" src="https://cdn-images-1.medium.com/max/1024/1*3tWHpWD0Xy143VEO6U2VKQ.png" /><figcaption>Heroku application deployment method</figcaption></figure><p>If you’re concerned about the auto deployment option, there is a manual deployment. But make sure that your settings are applied in the ‘deploy’ tab. Select the branch that you wish to deploy automatically, and make sure you’re committing your files to this branch that you wish to deploy. If you’re testing and using a different app for that inside your hosting, then I would make sure you name these branches accordingly.</p><figure><img alt="Heroku deployment settings" src="https://cdn-images-1.medium.com/max/1024/1*E9bKx2RD12E4tbnIkTyg0w.png" /><figcaption>Auto deployment within Heroku</figcaption></figure><h4>Ok, now what? How do I publish this sweet sweet project?</h4><p>Heroku doesn’t read .html files directly. You’ll need to create 2 simple files within your project to get your deployment functioning. You’ll need a index.php file, as well as a composer.json file to help the deployment along.</p><p>Create your index.php file first, and have it contain the following code:</p><pre>&lt;?php include_once(&quot;index.html&quot;); ?&gt;</pre><p>Once this is established, we need to create our composer.json file and give it a bit of something to hold on to as well (curly brackets):</p><pre>{}</pre><p>Now that we have the 2 files that Heroku requires to publish, we need to ensure that we have properly set up our PHP dyno within Heroku, and the added the ‘heroku/php’ buildpack under your settings tab.</p><figure><img alt="Heroku PHP buildpack" src="https://cdn-images-1.medium.com/max/1024/1*Ep2dRwk0LeFGUW1gHRAGNA.png" /><figcaption>Heroku PHP buildpack required</figcaption></figure><p>Set up your SSL and DNS settings. I’m no DNS ninja by any stretch so I needed to lean on a bit of help from one of my colleagues to push past this part. I find sometimes the DNS in your registrar settings to be a pain in the butt, but perhaps you have more patience than I do, so go ahead and get that done.</p><figure><img alt="DNS and SSL setup in Heroku" src="https://cdn-images-1.medium.com/max/1024/1*6iKsIsNr34SoWqbiUR1zfQ.png" /><figcaption>Set up your DNS and SSL in Heroku</figcaption></figure><p>Your SSL is managed with the dyno you paid for inside Heroku. You shouldn’t need to purchase one elsewhere. Configuring it is simple once your domain is setup, however you do always have the choice to use a SSL elsewhere depending on your requirements and comfort level.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*cygd_XZKS6calBI8_onjrQ.png" /><figcaption>Heroku SSL settings</figcaption></figure><h4>Deployment time. Cross your fingers!</h4><p>Now we have successfully put together the 3 primary pieces of this Webflow / Github project. These 3 pieces containing our no-code code from Webflow, our Github repository and our cost effective hosting solution with Heroku.</p><p>We recently edited our project code by adding our index.php and our composer.json files but at that time, we didn’t commit and push these files and I did this intentionally with you.</p><p>Right now, we have our Heroku set up to auto-deploy our main branch of our repository. If you were to commit and push your main branch you used, Heroku which is now attached to your Github account will receive these changes and deploy them to your hosting.</p><p>So go ahead and do that.</p><p>After you’ve waited roughly 60 seconds for that process to happen you should be able to reach your domain, which is now resolving as your newly published website.</p><p><strong><em>Congratulations. :)</em></strong></p><p><em>Did you know if you hold the “clap” button a while, that more people have a chance of seeing this story? — Find me on my </em><a href="https://instagram.com/nick_burd"><em>Instagram</em></a><em> for more content and conversation!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=26d6e2401c1b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/auto-deploy-webflow-using-github-26d6e2401c1b">Auto deploy Webflow using Github</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Figma Design Tokens with Github Repositories]]></title>
            <link>https://medium.com/design-bootcamp/figma-design-tokens-with-github-repositories-cb0554156137?source=rss-58cdc58fec6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/cb0554156137</guid>
            <category><![CDATA[ux-design]]></category>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[design-systems]]></category>
            <category><![CDATA[token-design]]></category>
            <category><![CDATA[figma]]></category>
            <dc:creator><![CDATA[Nick Burd]]></dc:creator>
            <pubDate>Sat, 15 Oct 2022 09:34:13 GMT</pubDate>
            <atom:updated>2022-10-24T19:22:50.223Z</atom:updated>
            <content:encoded><![CDATA[<h4>Help keep your design and development consistent</h4><figure><img alt="Use Figma Tokens and Github Repos to keep projects consistent" src="https://cdn-images-1.medium.com/max/768/1*9WwcYowUT8e0Zm_zMFfCLQ.png" /><figcaption>Figma Tokens and Github Repositories</figcaption></figure><p>Design tokens are relatively new. You might be asking at this point ‘what is a design token’, and I’m going to lay that out for you. I’m also going to help walk through the creation of a basic token and the process to sync with a Github repository and why we would want to do that.</p><p>So let’s get started.</p><h4>What is a design token?</h4><p>At this point, many designers have been using a design system. I’ve been using a couple for different projects over the past few years and they’re incredible if you use them correctly.</p><p>Some of the issues you might find with newer systems is the change that happens from design to development, and the little things that get left behind in your backlog and don’t get updated. Or perhaps you have multiple platforms all using the same design system, and you’re manually making changes that have been published to the design system in your projects.</p><p>A design token is a bit of information stored in a file for your front-end developers which was published in your design tool (in our case today, Figma).</p><ul><li>The designer makes the edit within the design tool, and gets it approved</li><li>Next, the changes get published in your design tool</li><li>The tool now pushes a version to your repo, in the specified language for the target platform</li><li>Your front-end developer pulls the code for implementation</li></ul><p>Generally, this could get messy if we’re using the wrong structure to do so. The smart idea here is to use a ‘core’ stylesheet which will contain these tokens. This way when your developer chooses to implement the token updates, they shouldn’t conflict with other sheets in the structure.</p><h4>OK. That’s fancy. But how?</h4><p>I’ve been using the <a href="https://www.figma.com/community/plugin/843461159747178978/Figma-Tokens">Figma Tokens plugin</a> to create my style tokens in Figma. While using this I am able to do some similar things within Figma that you’re already capable of, such as change and publish colors and fonts. But Figma Tokens goes even further and allows for more control for specs such as line-height, letter spacing, opacity, and even gradients.</p><figure><img alt="Figma tokens plugin example." src="https://cdn-images-1.medium.com/max/1024/1*-JxmxPM0tDusjyM5qyCLLg.png" /><figcaption>Figma Tokens — Plugin</figcaption></figure><p>In order to connect these design tokens to your <a href="https://github.com/">Github</a>, you’ll need to open the plugin in Figma and navigate to the <a href="https://github.com/">Github</a> credentials in the settings tab.</p><p>Doing this you’ll need to provide the plugin with the necessary information such as:</p><ul><li>Name of project</li><li>Personal access token</li><li>Repository username</li><li>Default branch</li><li>File path</li><li>Base URL (optional)</li></ul><p>Some items to note in this process are the fact that your <strong>personal access token</strong> can be created in your <em>Github profile &gt; settings &gt; developer settings &gt; personal access token</em>. In here you generate and name the token with the proper repo access.</p><p>Once you’ve created the access token, it is ideal to create your repository or the branch for the project. This choice is dependent on the progress of the project and where you might need this particular token file to be stored.</p><p>If you’re starting fresh, it’s ideal to clone your repo at this stage. If you’re familiar, you can create a couple files to support your project. But if you’re strictly a designer, you can rely on your front-end developer to do this.</p><p>Next, we can use the credentials and repository information inside the Figma plugin. This will allow us to connect the repository to our design token files.</p><figure><img alt="Github connection to Figma Tokens plugin" src="https://cdn-images-1.medium.com/max/1024/1*um6EJz6MAcdbUEaDaJFs8w.png" /><figcaption>Github connection to Figma Tokens</figcaption></figure><h4>OK, now I’ve connected Github to Figma. What next?</h4><p>You’re almost there. It’s a quite simple process and I think that the final stages of this here will be quick and painless.</p><p>Once you’ve saved your credentials, you’ll be presented with a dialogue box inside the Figma plugin which will ask you if you’d like to push your tokens to the repository. It will prompt for a message, and further details. This is something that repository users are familiar with, as it’s a commit message which describes the changes. I would certainly suggest making this a brief but meaningful description for the developers who are accessing the repository.</p><p>Congratulations. You’ve just successfully published your first round of Figma Design Tokens to a Github repository.</p><h4>Following steps</h4><p>After you’ve pushed the design tokens to Github, your developer will be able to access the tokens folder and json file you’ve added. If they simply pull the most recent version, the code will be added to the development files they are using.</p><p>For the developers; if they’re not familiar with the process from here, it’s going to require converting the json styles into variables to be used with CSS. You can do this using <a href="https://amzn.github.io/style-dictionary/#/quick_start">style dictionary</a> by installing using the npm install which will compile the files when your <a href="https://amzn.github.io/style-dictionary/#/config">config.json</a> file is set up in your project (run style-dictionary build in your command line.</p><p>I will do a deeper dive on compiling and updating variables using style dictionary. But for now, you’ll have to rely on the documentation in the link above.</p><h4>Finally…</h4><p>Once this is all achieved, any changes in Figma that are pushed to the repo can be simply pulled by the developer and automatically updated in the project files site wide.</p><p>These changes are all logged and documented in the repository, so if you feel like you need to revert the files — it can be pretty simple to do so. Otherwise, editing and pushing new style variations or changes can be a solution here as well.</p><p>I hope this has been a fun project for everyone. If you have used this method before, and have anything to add please do not hesitate to comment!</p><p><em>Did you know if you hold the “clap” button a while, that more people have a chance of seeing this story? — Find me on my </em><a href="https://instagram.com/nick_burd"><em>Instagram</em></a><em> for more content and conversation!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=cb0554156137" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/figma-design-tokens-with-github-repositories-cb0554156137">Figma Design Tokens with Github Repositories</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A custom Webflow build]]></title>
            <link>https://medium.com/design-bootcamp/a-custom-webflow-build-3243bc6f70d8?source=rss-58cdc58fec6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/3243bc6f70d8</guid>
            <category><![CDATA[ui-design]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[webflow]]></category>
            <dc:creator><![CDATA[Nick Burd]]></dc:creator>
            <pubDate>Tue, 14 Dec 2021 22:00:41 GMT</pubDate>
            <atom:updated>2021-12-15T22:22:43.817Z</atom:updated>
            <content:encoded><![CDATA[<h4>I didn’t expect things to go as smooth with a web builder</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/940/1*Z8SIlaa0aO0PYFajP1nGKw.png" /><figcaption>Webflow — making it pop (web builder)</figcaption></figure><p>I have been struggling for a while with my previous platform of choice… Wordpress. It seems to be the CMS of choice for many, and with good reason as it doesn’t require much in the way of custom coding with all of the plug-in options. The thing is, we build all of our websites at Niteowl Creative from scratch for Wordpress.</p><p>The problems we are facing are, with hundreds of clients it can be quite difficult to keep up on the maintenance for our clients who have opt’d into our maintenance subscription. Therefore we thought maybe reducing this by using Webflow for the simple projects might be applicable here.</p><h3>The pilot project</h3><p>We started a custom Ruby build a year ago.</p><p>After working with many developers we decided that it’s likely not going to be easy to maintain custom functionality within this build, and decided to research a better way to implement simple pages while keeping the core system in Ruby.</p><p>This particular project was Grayman.co – and the landing page for their new polo shirts. This initially seemed like a simple build with the built in e-commerce option but as we dug deeper and unearthed the needs for customizations we found that it might be easier said than done in this platform.</p><figure><img alt="Custom Webflow easement (fit) calculator" src="https://cdn-images-1.medium.com/max/1024/1*fhd0CeycuvXo7K42K47V0g.png" /></figure><h3>The wish</h3><p>To have a custom calculator merged with the e-commerce which uses a query to supply the best possible fit to the customer.</p><p>I consulted many people around what might be possible and how we could build a custom easement calculator for the shirts.</p><blockquote>Easement calculator is a way of finding the proper fit of your shirt. Being the shirt size in inches minus your chest size in inches. The number will give you the room left, and we associated it with the fit of that shirt (fitted, classic, oversized, etc)</blockquote><p>It turned out we needed to revise the plan slightly. Building an easement calculator independent of the cart with an output informing the user of the fit best suited for them.</p><p>Having this working was the biggest hurdle for us, but the end result is flawless and works like a dream.</p><figure><img alt="Grayman &amp; Company" src="https://cdn-images-1.medium.com/max/563/1*cOy_HVxzJLvNNZ56zxLekQ@2x.jpeg" /></figure><h3>In the end</h3><p>I had a great experience. The delay in the project due to learning curves and scope creep are a natural occurrence with many projects.</p><p>This one was no different.</p><p>We have already started another two projects in Webflow with some new clients. Excited to see how these two might work out, I have already started documenting our process and accounting for any possible hurdles.</p><p>The way in which I am attempting to mitigate any surprises in these projects is a bit of pre-dev research to ensure that :rd party applications can be used as effectively as possible (such as Calendly in this particular case), and that Foxy.io is going to help us build more comprehensive ecommerce products.</p><p>Have you used Webflow? What was your experience, and what did you learn in your first project? I love when people share these sorts of stories with me!</p><p><em>Did you know if you hold the “clap” button a while, that more people have a chance of seeing this story? — Find me on my </em><a href="https://instagram.com/nick_burd"><em>Instagram</em></a><em> for more content and conversation!</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3243bc6f70d8" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/a-custom-webflow-build-3243bc6f70d8">A custom Webflow build</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Five HTML & CSS tricks to make your project flow smoother]]></title>
            <link>https://medium.com/design-bootcamp/five-html-css-tricks-to-make-your-project-flow-smoother-5030c62fc829?source=rss-58cdc58fec6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/5030c62fc829</guid>
            <category><![CDATA[html]]></category>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[ux]]></category>
            <dc:creator><![CDATA[Nick Burd]]></dc:creator>
            <pubDate>Fri, 23 Apr 2021 01:53:41 GMT</pubDate>
            <atom:updated>2021-04-23T01:53:41.630Z</atom:updated>
            <content:encoded><![CDATA[<h4>Often disregarded or overlooked methods for an easier coding experience</h4><figure><img alt="Developer’s desk with IDE open on Macbook Pro" src="https://cdn-images-1.medium.com/max/1024/0*tmFN761NDmdQbpov" /><figcaption>Photo by <a href="https://unsplash.com/@silvawebdesigns?utm_source=medium&amp;utm_medium=referral">Nathan da Silva</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>As a web developer and designer, I often code with a team. Typically as a front-end developer, you end up with the start of the project before anyone else so it’s important to start with a good foundation for not only yourself but others as well.</p><p>I want to share a couple of starting points, that for me, usually make it into projects at the start.</p><ol><li><strong>Structuring my files</strong></li></ol><p>In the beginning, I start with a simple structure. I like to template when I’m building so starting with a header, footer, and body for me is important. Having a public folder of my HTML with folders for CSS, SCSS, JS, and Assets follow into that public folder. I use simple PHP to include my header and footer into my body.</p><p>This might not work for all projects. But the more simplistic way to start a small site is my ground zero.</p><figure><img alt="File structure of the beginning of a project." src="https://cdn-images-1.medium.com/max/413/1*QX8VADhZr4W6e1XwmeB3nQ.png" /><figcaption>A screenshot — Starting file structure</figcaption></figure><p>2. <strong>A simple reset</strong></p><p>I like to add a simple reset to my projects in my styles. This helps me weed out any of those weird conflicts I might come across later in the project once I start styling. I apply 0 padding and margin to the document body so that when I’m adding styling to something like a slider I won’t need to adjust the margins with those elements.</p><figure><img alt="Where my projects start with a simple document reset for styling." src="https://cdn-images-1.medium.com/max/730/1*Ft2TCDnLMecpNxr4iAQxDg.png" /></figure><p>3. <strong>Sass and compiling for easier coding</strong></p><p>If you haven’t been using <a href="https://sass-lang.com/">Sass</a> you’re missing out severely. Using a CSS pre-processor and compiling your styles to a single CSS document can help you keep track of what styles are where and make it easier to work with.</p><p>Not to mention the benefits of nesting, variables, and mixins. I’ve begun finding it much more cumbersome to code CSS without using a pre-processor.</p><p>You’ll need to use something like <a href="https://nodejs.org/en/">Node.JS</a> and their <a href="https://www.npmjs.com/package/sass-watch">Sass-watch</a> add-on to compile your Scss into CSS.</p><p>4. <strong>Smooth scrolling</strong></p><p>Now, we’ve all seen websites that have a bit of jitter when scrolling using your mouse. Often enough we use a javascript library to help us achieve a nice smooth momentum when moving the content.</p><p>The problem here is, there are so many and could be hard to find if you’re not looking in the right places.</p><p>I’ve been using in recent projects a vanilla JS plugin called <a href="https://www.cssscript.com/inertial-parallax-scroll-luxy/">Luxy.js</a> for its inertial scroll because it’s so smooth and pretty. It’s installed using node and is quite easy to do so, so follow the instructions on their site. Don’t skip out on this. It’s a great improvement for your users!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/677/1*JCIABl2aaeHqXrAIFx5RgA.png" /></figure><p>5. <strong>Simple responsive HTML using CSS Grid</strong></p><p>Now, I can go a bit deeper with this, and I intend to in a future post. Until then there is a wealth of information available to be used.</p><p>Using CSS grid is somewhat new for me. I’ve been integrating it into my projects for a short time but I’ve completely become un-reliant on frameworks such as Tailwind, Bootstrap, or Foundation.</p><p>Wrapping elements in a div and applying a class with the following CSS can create a really simple grid with great flexibility and responsiveness. CSS grid has an extensive use, and there are so many variations it’s capable of that you would be missing out if you haven’t taken the opportunity to play with it.</p><figure><img alt="A simple responsive CSS grid" src="https://cdn-images-1.medium.com/max/713/1*oKVmV3zD_qBCMRCPCkixVQ.png" /></figure><figure><img alt="CSS Grid output using inspect on Google Chrome at desktop size" src="https://cdn-images-1.medium.com/max/1024/1*jPFURGf8_N7PPxEs-FB0jQ.png" /><figcaption>Desktop sizing — Inspect with Google Chrome shows CSS grid</figcaption></figure><figure><img alt="Tablet size showing inspect of CSS Grid on Google Chrome" src="https://cdn-images-1.medium.com/max/496/1*U_ooIZ8yjsR7iEYh3LJ57A.png" /><figcaption>Tablet sizing — Inspect with Google Chrome shows CSS grid</figcaption></figure><h4>Conclusion</h4><p>As you can see there are plenty of methods in HTML and CSS that can make your coding life easier. These five simple inclusions can improve the outcomes of your project and make your life a whole lot easier in regards to simple front-end development.</p><p>If you’re looking for more examples, StackOverflow is jam-packed with fun and exciting new ways to improve your projects for you to learn.</p><p><em>Did you know if you </em><strong><em>hold the “clap” button</em></strong><em> a while, that more people have a chance of seeing this story? — I also have a </em><a href="http://eepurl.com/hqtY5L"><em>mailing list</em></a><em> if you’d like updates on newly published stories.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5030c62fc829" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/five-html-css-tricks-to-make-your-project-flow-smoother-5030c62fc829">Five HTML &amp; CSS tricks to make your project flow smoother</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Starting with Statamic CMS]]></title>
            <link>https://medium.com/design-bootcamp/starting-with-statamic-cms-f3b2b3faf27?source=rss-58cdc58fec6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/f3b2b3faf27</guid>
            <category><![CDATA[statamic]]></category>
            <category><![CDATA[html]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[wordpress]]></category>
            <dc:creator><![CDATA[Nick Burd]]></dc:creator>
            <pubDate>Sun, 07 Mar 2021 22:56:33 GMT</pubDate>
            <atom:updated>2021-03-08T16:31:22.296Z</atom:updated>
            <content:encoded><![CDATA[<h4>A short log of my initial setup experience and some tips I learnt along the way</h4><p>I’ve been a Wordpress developer for the past decade or more. I’ve learnt plenty but over the last short while I’m finding it more cumbersome and annoying than it is helpful. I wanted to move to a simple CMS that still allows me to build from scratch and gives me more control over the template. As a designer and front-end developer I needed something with minimal hassle to setup.</p><p>See <a href="http://statamic.com/">Statamic</a>.</p><figure><img alt="Screenshot of Statamic’s homepage" src="https://cdn-images-1.medium.com/max/1024/1*KgrE0Tl5ZJ0VGprfOKzOJA.png" /><figcaption>Screenshot — Statamic.com</figcaption></figure><p>Statamic is a Laravel CMS which allows for deep customization or simple integration. It has a few add-ons available for users to purchase, and some that seem to be free. My initial impression so far, is that I’m going to love working with it, and the way that it’s built is simple enough for most developers to understand (better for those with PHP knowledge though).</p><p>For those of you who don’t have in-depth programming skills or have issues, the <a href="https://statamic.com/forum/">Statamic forum</a> is great and the responses are generally quick.</p><h4>Starting my project</h4><p>I started with the how-to section on Statamic’s website and chose the most bare-bones path as the site I’m building is pretty simple. Statamic requires installing CLI installer to your $PATH to use Composer which is required for Laravel projects. You’ll need to use your command line tool to do the installations so make sure you have it open and install CLI. All these instructions can be found on the <a href="https://statamic.dev/installation">Statamic dev site</a> as well.</p><p>Make sure <a href="https://getcomposer.org/doc/00-intro.md">composer</a> is installed before starting.</p><p>Then download the Statamic CLI installer.</p><blockquote>composer global require statamic/cli</blockquote><p>Once cli / Statamic is installed, you should be able to start a new project. Unfortunately for me, I ran into a hiccup and my Mac didn’t know where the proper path was so I had to follow some other steps which aren’t noted on the dev site. You can see the info for that here on <a href="https://stackoverflow.com/questions/25373188/how-to-place-the-composer-vendor-bin-directory-in-your-path/25373254#25373254">Stack Overflow</a> incase you need it.</p><p>When that error I was receiving was resolved I was able to create a new project. Make sure to change directories into your sites folder, and use the following:</p><blockquote>composer create-project — prefer-dist statamic/statamic {site_name}</blockquote><h4>Viewing your test URL</h4><p>I had Statamic successfully installed however in the instructions within the Statamic website it didn’t mention that I’d need to configure MAMP in a specific way to view my test URL. In doing this I needed to create a host file in my localhost which was named and directed to the proper document root of the install.</p><p>Remember when doing this to point the root to your ‘public’ folder within your install, otherwise you will just end up seeing a document root.</p><p>After all of this, I ended up being able to visit the url and received an error which stated “Call to a member function dated() on null”. This was a previous caching error which needed to be solved and could be done through the terminal in your project folder by using:</p><blockquote>php artisan cache:clear</blockquote><p>Reloading the page now showed my Statamic landing page!</p><h4>Create a user</h4><p>Before I could really get started I needed to create a user to access my control panel. Doing this also involved the command line tool, but it’s pretty simple to get through. After entering the proper command, you’re prompted for the user / pass combo to get started. It’s then stored in a document using encryption for the password inside the users folder.</p><blockquote>php please make:user</blockquote><p>Follow the prompts and you’re finished!</p><p>Note: If you decide you need to manually edit your password because you forgot what you entered, make sure to <a href="https://www.md5hashgenerator.com/">encrypt it using MD5</a> for security. You can edit that password in the generated file in the users folder.</p><figure><img alt="Screenshot of Statamic template structure" src="https://cdn-images-1.medium.com/max/558/1*_WCKCmNMmUQRqjZ2aVRWTQ.png" /><figcaption>Files structure — Statamic templates</figcaption></figure><h4>What I did next</h4><p>My next steps had nothing to do with the Statamic install. But I did make sure to create a proper repository for the project in <a href="http://github.com/">Github</a>, and I installed <a href="http://nodejs.org/">NodeJS</a> and <a href="https://www.npmjs.com/package/npm-watch">Node-watch</a> to compile my Sass.</p><p>I’ve started building my site now, and as I’m using Statamic, I’m quite pleased with how flexible the platform seems and look forward to working deeper within the CMS.</p><p>I have decided to build custom ‘antlers’ within the templating system they provide, and use the proper structure for navigation and documents. I’m following some of the <a href="https://statamic.dev/screencasts/">screencasts</a> to help guide me through the process so that I ensure I’m building as intended, which will help me later on if I need to refresh my memory to make changes.</p><h4>Conclusion</h4><p>All-in-all I think I’m on a good path. This is going to help assist in the steps I need to take to improve my business and the services we provide. The intent is to gradually step away from Wordpress as a CMS option as much as possible.</p><p>I’ll continue to create articles to help others with the use of Statamic, so clap, follow and share this if you found it helpful.</p><p><em>Did you know if you </em><strong><em>hold the “clap” button</em></strong><em> a while, that more people have a chance of seeing this story? — I also have a </em><a href="http://eepurl.com/hqtY5L"><em>mailing list</em></a><em> if you’d like updates on newly published stories.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f3b2b3faf27" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/starting-with-statamic-cms-f3b2b3faf27">Starting with Statamic CMS</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[A requirement for better attention to detail in front-end development]]></title>
            <link>https://medium.com/design-bootcamp/a-requirement-for-better-attention-to-detail-in-front-end-development-7806a8be9e92?source=rss-58cdc58fec6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/7806a8be9e92</guid>
            <category><![CDATA[ui]]></category>
            <category><![CDATA[css]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[html]]></category>
            <dc:creator><![CDATA[Nick Burd]]></dc:creator>
            <pubDate>Tue, 02 Mar 2021 04:35:58 GMT</pubDate>
            <atom:updated>2021-03-02T04:35:58.895Z</atom:updated>
            <content:encoded><![CDATA[<h4>Closer pixel perfect outcomes, and continuing to learn new techniques in HTML / CSS for a better web</h4><figure><img alt="Front-end developer learning CSS from a colleague" src="https://cdn-images-1.medium.com/max/1024/0*hR3KXTg_-ozvxqHQ" /><figcaption>Photo by <a href="https://unsplash.com/@sigmund?utm_source=medium&amp;utm_medium=referral">Sigmund</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>I’ve been a front-end developer and designer with a primary focus on HTML/CSS for a little more than a decade. I realize that many focus beyond these initial languages, mostly on Javascript, which makes complete sense. But what I’ve noticed is that most of these developers lack strong, fundamentally essential skills in the initial languages required to build a semantic and beautiful web.</p><p>Many times I’ve handed off designs that have been well thought out and pixel perfect, only to get them back and require multiple rounds of revisions to perfect the layout. In these situations, they need my assistance with HTML and CSS, which usually isn’t a problem, but many designers cannot assist with coding the layout.</p><h4>But where does this problem come from?</h4><p>Many developers start with HTML and CSS, learn enough to be comfortable, and move on. In many cases, this could be sufficient. Both languages have evolved so fast that it can be intimidating for some to learn more.</p><h4>What can we do?</h4><p>We, as developers, should be fluent in HTML and CSS. They’re the initial building blocks of the web, and the outcome of the product depends on it. We won’t even begin to dive into <a href="https://bootcamp.uxdesign.cc/dont-skip-ui-accessibility-3ef35adde631?source=your_stories_page-------------------------------------">web accessibility</a> right now and how dependent on HTML it is, but if you don’t know, that could be part of the problem.</p><p>Design and development require constant learning and upgrading. Otherwise, we get left behind with stale skills. Using tools such as <a href="http://teamtreehouse.com/">Treehouse</a> and <a href="https://www.codecademy.com/">Code Academy</a> a couple of hours a month to brush up on new skills can make a difference in the final product and provide a sense of accomplishment we can be proud of.</p><p>We can also work closely with others who have a more robust knowledge of the skills we lack to learn more. Be humble and understand that not everyone can know everything, and it’s the effort we put forward to realize that separates us.</p><figure><img alt="Ui / Ux tools on a designer’s desk" src="https://cdn-images-1.medium.com/max/1024/0*RuQetNPXaxX8rRpI" /><figcaption>Photo by <a href="https://unsplash.com/@uxstore?utm_source=medium&amp;utm_medium=referral">UX Store</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>Attention to detail</h4><p>In some cases, it might not be the lack of skill or knowledge of coding languages that factor in lesser quality results. In some cases, the simple lack of attention to detail can play a significant factor. One of the main things I like to do with designs is open it in a tab in my browser and switch between my dev and the layout to ensure that things are pixel perfect the way they were intended.</p><p>I’ve learned over the years that you can’t always be 100% in all situations. But the praise you get for making an effort is certainly worth the extra hassle and time spent to make sure the outcome is as close as possible.</p><h4>New techniques to learn now</h4><p>Some new features to pay attention to in the future as a front-end developer could be CSS Grid, variable fonts, text animations, and browser support CSS. You don’t need to master every new feature, but being aware of them is an excellent first step.</p><ul><li><a href="https://www.w3schools.com/css/css_grid.asp">CSS grid</a><br>This is a great way to make modular layouts that adapt well to devices with minimal breakpoints (or none at all). CSS grid is awesome when paired with <a href="https://www.w3schools.com/css/css3_flexbox.asp">Flexbox</a>, and you won’t even need <a href="https://getbootstrap.com/">Bootstrap</a> bloating your product either.</li><li><a href="https://v-fonts.com/">Variable fonts</a><br>At the time of writing this, it’s still a pretty new concept. A handful of fonts can be used at the moment, but the idea is a file containing each variation of the font the user could require.</li><li><a href="https://freefrontend.com/css-text-animations/">Text animations</a><br>Floating, growing, and scrolling fonts are becoming used to increase the interactions and visual interest in websites. Dynamic fonts can help change how users interact and read our content.</li><li><a href="https://developer.mozilla.org/en-US/docs/Web/CSS/@supports">Browser support CSS</a><br>Using the @support query, you can create browser-specific rules to determine what code is used depending on which browser is supported. Learn more from the <a href="https://developer.mozilla.org/en-US/docs/Web/CSS/@supports">Mozilla website.</a></li></ul><h4>Conclusion</h4><p>All-in-all, the web is a pretty big place. It’s rapidly growing with hundreds of thousands of websites every month and new and impressive CSS and HTML features. Developers cannot be expected to know everything, and that’s quite okay. But we can be expected to learn some basics and new features of the core languages that the web is built. I know that sometimes they’re not always fun and exciting for others, but they can help develop a more pleasant web for everyone.</p><p>Suppose you want to foster good relationships with your designers and business owners or clients. Some of the skills here are important to improve or grow as a front-end developer.</p><p><em>Did you know if you </em><strong><em>hold the “clap” button</em></strong><em> a while, that more people have a chance of seeing this story? — I also have a </em><a href="http://eepurl.com/hqtY5L"><em>mailing list</em></a><em> if you’d like updates on newly published stories.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7806a8be9e92" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/a-requirement-for-better-attention-to-detail-in-front-end-development-7806a8be9e92">A requirement for better attention to detail in front-end development</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Dealing with entropy in product design]]></title>
            <link>https://medium.com/design-bootcamp/dealing-with-entropy-in-product-design-6f5db9c097a6?source=rss-58cdc58fec6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f5db9c097a6</guid>
            <category><![CDATA[design]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[product-design]]></category>
            <category><![CDATA[research]]></category>
            <category><![CDATA[business]]></category>
            <dc:creator><![CDATA[Nick Burd]]></dc:creator>
            <pubDate>Sat, 20 Feb 2021 02:43:28 GMT</pubDate>
            <atom:updated>2021-02-20T13:23:46.691Z</atom:updated>
            <content:encoded><![CDATA[<h4>About the necessity of steady design improvement over time</h4><figure><img alt="Designer wire-framing on paper with pen." src="https://cdn-images-1.medium.com/max/1024/0*6J_UAreGl8IiYkce" /><figcaption>Photo by <a href="https://unsplash.com/@kellysikkema?utm_source=medium&amp;utm_medium=referral">Kelly Sikkema</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>Entropy is the increase of disorder over time. Meaning that once something exists, it starts along the path of deterioration or non-existence. It sound’s grim, but when you think about it, it couldn’t be more accurate.</p><p>I want to talk about design entropy and how it affects our clients, products, and deliverables. Digital product design, in many cases, is severely impacted by entropy, considering there are often a dozen sprints that pass before we get the initial release of our product out to the world. This means; meanwhile, we are likely finding new and exciting ways to present the information. Now, this isn’t to say that your work you’ve completed is now worthless or obsolete. Your work has instead shown the opportunity for improvement.</p><p>The market for your product could change, new resources could be available, the project’s speed due to resources could be limited, hiring could be difficult or timely, and the overall needs could have changed.</p><figure><img alt="Product design meeting at an agency" src="https://cdn-images-1.medium.com/max/1024/0*2eYlYNEmvClh0C6a" /><figcaption>Photo by <a href="https://unsplash.com/@austindistel?utm_source=medium&amp;utm_medium=referral">Austin Distel</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>The reality</h4><p>In reality, there are very minimal opportunities or projects where we continuously work alongside the business team to improve the products over time. That’s just merely the cold-hard fact of the situation being a designer or developer.</p><p>In some cases, entropy can be sped up by <a href="https://bootcamp.uxdesign.cc/design-debt-its-real-939718d3c0f">design or development debt</a>. Moving quickly through a sprint and publishing new work as we finish a 2-week sprint could encourage lousy practice to meet these timelines, which leads to a higher rate of entropy in that product. A sure way to do this is to properly plan out the path beforehand to reduce the debt in those scenarios.</p><p>But often, when working with larger projects or timelines, the vision could change quite substantially by the time the finished product is produced that the previous efforts require revision. Still, there simply isn’t the time or budget to address the concerns.</p><figure><img alt="Product teams working together with a common goal using laptops and tablets" src="https://cdn-images-1.medium.com/max/1024/0*l9Px_1uftTi7Bsj0" /><figcaption>Photo by <a href="https://unsplash.com/@marvelous?utm_source=medium&amp;utm_medium=referral">Marvin Meyer</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><h4>In a perfect world</h4><p>What we need as designers and developers is the affordance of time and direction. This will allow more accurate research and planning for the future of the product.</p><p>During the initial stages of the project, you would need the opportunities to sit and brainstorm and realize the product’s future path. Brainstorming will benefit in the long run because we can listen to the research and the user surveys to imagine new functionalities or improvements required to serve our current and future user base best.</p><p>There are many products that we use on a day-to-day basis that work in this way. Companies such as <a href="https://apple.com/">Apple</a>, <a href="https://www.invisionapp.com/">Invision</a>, <a href="https://www.atlassian.com/">Atlassian</a>, or <a href="http://figma.com/">Figma</a>, for example, are currently working years ahead of where they’re sitting currently with their products. They have multiple teams dedicated to improving the product now but also planning future features of their product.</p><h4>But how do we delay or slow entropy?</h4><p>I realize that many of us cannot have three teams of 10 designers and developers working for years at a time. It’s, for many of us, just merely unrealistic, at least right now.</p><p>What we can do right now is more substantial research. Every product or feature deserves its time in exploration and complete planning to delay degrading. By considering the following:</p><ul><li>Accurate user testing and personas</li><li>Research into similar products</li><li>Mimicking larger team processes at a modified version for your team</li><li>Working smarter during design and development to lessen debt</li></ul><p>Hopefully, we can develop products that have great success, which could turn into future affordability for continuous improvement.</p><p><em>Did you know if you </em><strong><em>hold the “clap” button</em></strong><em> a while, that more people have a chance of seeing this story? — I also have a </em><a href="http://eepurl.com/hqtY5L"><em>mailing list</em></a><em> if you’d like updates on newly published stories.</em></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f5db9c097a6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/design-bootcamp/dealing-with-entropy-in-product-design-6f5db9c097a6">Dealing with entropy in product design</a> was originally published in <a href="https://medium.com/design-bootcamp">Bootcamp</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How You Should Look After Body When Designing a Product]]></title>
            <link>https://nickburd.medium.com/how-you-should-look-after-body-when-designing-a-product-7f7981a39ddc?source=rss-58cdc58fec6f------2</link>
            <guid isPermaLink="false">https://medium.com/p/7f7981a39ddc</guid>
            <category><![CDATA[health]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[startup]]></category>
            <category><![CDATA[design]]></category>
            <category><![CDATA[ui]]></category>
            <dc:creator><![CDATA[Nick Burd]]></dc:creator>
            <pubDate>Thu, 18 Feb 2021 10:36:34 GMT</pubDate>
            <atom:updated>2021-05-30T17:33:03.884Z</atom:updated>
            <content:encoded><![CDATA[<h3>How To Look After Your Body When Designing a Product</h3><h4>It’s important to look after body when often being seated</h4><figure><img alt="Ergonomic workspace" src="https://cdn-images-1.medium.com/max/1024/1*tE_hy8FFezCbzJjHZ_sp1Q.jpeg" /><figcaption>Photo by <a href="https://unsplash.com/@jamesm?utm_source=medium&amp;utm_medium=referral">James McDonald</a> on <a href="https://unsplash.com/?utm_source=medium&amp;utm_medium=referral">Unsplash</a></figcaption></figure><p>If you’re working the majority of your day’s sitting down like myself, you might be finding the odd time that you’re waking up with body aches or even just having trouble sleeping.</p><p>Sitting down for 8+ hours a day at a desk can be taxing on your body, and it’s essential to stay active at a minimum level. When your body gets too used to sitting, you run the chance to pull muscles or causing strain when you perform other activities, which could end up in injury.</p><p>I’m no stranger to a little hot/cold cream now and then, but I do my best to prevent it.</p><h3>Some Stretching</h3><p>Other than being seated ergonomically and paying attention to the position and angle of your arms and back while working, it is crucial to at least get a little stretch in here and there — bonus points for incorporating a <a href="https://www.amazon.ca/Best-Resistance-Bands-Exercise-Guarantee/dp/B01AVDVHTI/ref=sxin_9?ascsubtag=amzn1.osa.0a99e5b2-4ffb-4419-9bc7-5946c33e9de5.A2EUQ1WTGCTBG2.en_CA&amp;creativeASIN=B01AVDVHTI&amp;cv_ct_cx=resistance+band&amp;cv_ct_id=amzn1.osa.0a99e5b2-4ffb-4419-9bc7-5946c33e9de5.A2EUQ1WTGCTBG2.en_CA&amp;cv_ct_pg=search&amp;cv_ct_we=asin&amp;cv_ct_wn=osp-single-source-earns-comm&amp;dchild=1&amp;keywords=resistance+band&amp;linkCode=oas&amp;pd_rd_i=B01AVDVHTI&amp;pd_rd_r=30bcf3eb-9eeb-4da4-995d-c85ced0b29e1&amp;pd_rd_w=GPS63&amp;pd_rd_wg=yl7Dj&amp;pf_rd_p=d7f4a0ee-9fbf-4903-b4f2-352da205617c&amp;pf_rd_r=K40C5N66SX9V97DR9P8E&amp;qid=1612131046&amp;sr=1-3-64f3a41a-73ca-403a-923c-8152c45485fe&amp;tag=workingmotherbonnier_os_ca-20">resistance band</a> as well into your stretches.</p><p><strong>Stretch 1</strong> — Reach above your head with both arms, and grab your elbow with each hand. Lean-to the sides slowly and hold for 10–15 seconds, repeat on the opposite side.</p><p><strong>Stretch 2</strong> — Take your left foot and place it on the knee of your right leg while sitting straight up. Lean forward slowly until you feel it pull on your back/butt. Hold this for 10–15 seconds and repeat on the other side.</p><p><strong>Stretch 3 </strong>— Hold a resistance band using both hands. Stretch your arms out in front of you and pull the band horizontally. Continue this for 10–12 reps and 3–5 sets.</p><h3>Ergonomics</h3><p>We’re hearing a lot these days about chairs, pads, desks, etc. So I’m going to share a few of the items I use and a few ‘nice-to-have’ items I’d even like to consider in the future.</p><p><a href="https://www.amazon.ca/Memory-Keyboard-Support-Cushion-Computer/dp/B07CTHNVM5/ref=sr_1_18?dchild=1&amp;keywords=mouse+and+keyboard+wrist+support&amp;qid=1612131290&amp;sr=8-18">Keyboard / Mouse wrist pads</a> — These are great for ensuring your arms are at the proper angle for using your peripherals. There are many types, sizes, and shapes, but it’s well worth it.</p><p><a href="https://www.hermanmiller.com/">A comfy &amp; supportive chair</a> — One might argue this is paramount to anything. Your chair is where you’ll be parked for the day, so it’s ok to splurge a little. Herman Miller makes phenomenal chairs, and they’re built to the specific size of your body, so make sure to measure correctly for the best support.</p><p><a href="https://www.amazon.ca/Ergonomic-Support-Airplane-Footrest-Non-Slip/dp/B08J3XC3DR/ref=sr_1_7?crid=2JENNKCE1C78P&amp;dchild=1&amp;keywords=ergonomic+foot+rest+under+desk&amp;qid=1612131484&amp;sprefix=ergonomic+foot%2Caps%2C165&amp;sr=8-7">Ergonomic foot rest</a> — Now, I don’t have one of these anymore (dog ate it.), but it was terrific. Now that I realize it, I may have to re-purchase. They’re great for encouraging you not to keep your legs in one specific position bent 90 degrees or laid straight out in front of you.</p><p><a href="https://www.wayfair.ca/furniture/pdp/inbox-zero-electric-standing-desk-c004239881.html?piid=1470884271">Standing desk </a>— I don’t currently have a standing desk. I do have a plan for the future, and I see a massive benefit to having one. I think circulation is vital when you’re at a desk all day, which is an excellent way to achieve it. There are a couple of standing desks, be it mechanical or the kind that sits on your regular desk. The choice is yours. Obviously, one is more cost-effective.</p><h3>Final Thoughts</h3><p>Above all, try and get up and move around. Stretch, don’t slouch, have a proper height desk and chair, don’t work on your couch (as I’m writing this, I am guilty. Whoops), and ensure you’re hydrated / fed and getting a little bit of distance from your monitors through the day.</p><p>Our health is important. Before we know it, we’re in our mid 70’s and looking back on the poor choices we made, wishing we bought that $1000 standing desk that could have saved us a lot of current back or hip pain.</p><p>You only have one body. Protect it, exercise it, feed and water it, and you’ll be laughing your way through your later years!</p><p>Want more? <a href="https://olhabahaieva.ck.page/52893cef89">Download 100+ UX/UI design tools collection</a> for free.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=7f7981a39ddc" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>