<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:dc="http://purl.org/dc/elements/1.1/">
  <channel>
    <title>DEV Community: ezgihendrickx</title>
    <description>The latest articles on DEV Community by ezgihendrickx (@ezgihendrickx).</description>
    <link>https://dev.to/ezgihendrickx</link>
    <image>
      <url>https://media2.dev.to/dynamic/image/width=90,height=90,fit=cover,gravity=auto,format=auto/https:%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F411701%2F3ff98aee-607c-4025-893c-76d64632365f.jpeg</url>
      <title>DEV Community: ezgihendrickx</title>
      <link>https://dev.to/ezgihendrickx</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/ezgihendrickx"/>
    <language>en</language>
    <item>
      <title>Great GatsbyJS😎</title>
      <dc:creator>ezgihendrickx</dc:creator>
      <pubDate>Sun, 07 Feb 2021 21:29:31 +0000</pubDate>
      <link>https://dev.to/ezgihendrickx/great-gatsbyjs-1ocb</link>
      <guid>https://dev.to/ezgihendrickx/great-gatsbyjs-1ocb</guid>
      <description>&lt;h2&gt;&lt;b&gt;💅 Building a Minimalist CV with Gatsby&lt;/b&gt;&lt;/h2&gt; 

&lt;p&gt;
&lt;a href="https://gatsbyminicv.netlify.app/"&gt; 
🍋 Live&lt;/a&gt;
&lt;/p&gt;



&lt;h4&gt;
  
  
  Helloooo everybody! I've been busy with Gatsby recently and I was trying to learn the basics in a fun way. Therefore I created a minimalist CV with Gatsby. I've built my CV step by step, and in this way you can also create a basic CV with me or just learn the basics along the way. I hope you will like and enjoy it. Oke, let’s dig in!
&lt;/h4&gt;




&lt;h2&gt;
  
  
  🐝 Intro
&lt;/h2&gt;

&lt;p&gt;First we need to set up our development environment.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://i.giphy.com/media/YAnpMSHcurJVS/giphy.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://i.giphy.com/media/YAnpMSHcurJVS/giphy.gif" alt="Gif about starting"&gt;&lt;/a&gt;&lt;/p&gt;




&lt;h2&gt;
  
  
  🌱 Global Installation
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Install &lt;code&gt;Homebrew&lt;/code&gt;. (To install Gatsby and Node.js on a Mac, it is recommended to use Homebrew.)&lt;/li&gt;
&lt;li&gt;If you don't have it already, install the &lt;code&gt;Node.js, npm&lt;/code&gt;. (Node.js is an environment that can run JavaScript code outside of a web browser.)&lt;/li&gt;
&lt;li&gt;Install Git: be able to work with starter templates.&lt;/li&gt;
&lt;li&gt;Install Gatsby globally on your machine &lt;code&gt;npm install -g gatsby-cli&lt;/code&gt;
&lt;/li&gt;
&lt;li&gt;Create a new site from &lt;a href="https://www.gatsbyjs.com/starters/?v=2"&gt;Starters&lt;/a&gt;

&lt;ul&gt;
&lt;li&gt;Choose the one you like or start with a default gatsby starter which is &lt;a href="https://www.gatsbyjs.com/starters/gatsbyjs/gatsby-starter-hello-world/"&gt;hello world&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;TL;DR 🔖 If you’re not sure what you installed before then just check from your Command Line: e.g&lt;br&gt;
 &lt;code&gt;node --version&lt;/code&gt; to learn your version. &lt;/p&gt;
&lt;h2&gt;
  
  
  🐙 Github &amp;amp; Terminal &amp;amp; VS Code
&lt;/h2&gt;

&lt;ol&gt;
&lt;li&gt;Create a repository named &lt;code&gt;gatsby-intro&lt;/code&gt;on your github.&lt;/li&gt;
&lt;li&gt;Don't forget to initialize your README file.&lt;/li&gt;
&lt;li&gt;Clone it to your machine.(I personally use VS Code) &lt;/li&gt;
&lt;li&gt;Change the Directory (This says ‘I want to change directories (cd) to the “hello-world” subfolder’. .)&lt;/li&gt;
&lt;li&gt;If you are stuck or lost, type in your terminal &lt;code&gt;gatsby --help&lt;/code&gt; and see the options it gives you.&lt;/li&gt;
&lt;li&gt;Start the development mode.. &lt;code&gt;gatsby develop&lt;/code&gt; This command starts a development server. You will be able to see and interact with your new site in a development environment — local (on your computer, not published to the internet)&lt;/li&gt;
&lt;li&gt;&lt;p&gt;View your site locally: Open up a new tab in your browser and navigate to &lt;a href="http://localhost:8000/"&gt;http://localhost:8000/&lt;/a&gt; &lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--5uK3ETwh--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://www.gatsbyjs.com/static/057f454229859b1752c44dba1580984e/a8c87/04-home-page.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--5uK3ETwh--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://www.gatsbyjs.com/static/057f454229859b1752c44dba1580984e/a8c87/04-home-page.png" alt="HomePage"&gt;&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Your &lt;code&gt;hello world&lt;/code&gt; &lt;strong&gt;&lt;em&gt;index.js&lt;/em&gt;&lt;/strong&gt; file should be like this:&lt;br&gt;
&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;import React from "react"

export default function Home() {
  return &amp;lt;div&amp;gt;Hello world!&amp;lt;/div&amp;gt;
}

{/* you need to always export and this is a  React rule. */}.

&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;


&lt;ul&gt;
&lt;li&gt;Create components in your &lt;code&gt;src&lt;/code&gt;folder. 

&lt;ul&gt;
&lt;li&gt;Components structure should more or less look like below .&lt;/li&gt;
&lt;li&gt;Footer.js&lt;/li&gt;
&lt;li&gt;Header.js&lt;/li&gt;
&lt;li&gt;Main.js

&lt;ul&gt;
&lt;li&gt;About.js&lt;/li&gt;
&lt;li&gt;Contact.js&lt;/li&gt;
&lt;li&gt;Skills.js&lt;/li&gt;
&lt;li&gt;Projects.js&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--7my2BJti--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/p1mkgyszr02bid4582vg.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--7my2BJti--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://dev-to-uploads.s3.amazonaws.com/i/p1mkgyszr02bid4582vg.png" alt="Alt Text"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Sorry for the shiny colors:) I created it rather quickly in &lt;a href="https://www.figma.com/"&gt;Figma&lt;/a&gt;&lt;br&gt;
⚠️ Don't forget to create &lt;code&gt;styles.css&lt;/code&gt;files.&lt;/p&gt;


&lt;h2&gt;
  
  
  💫 Installing Plugins
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;In your &lt;code&gt;gatsby-config.js&lt;/code&gt;file you need to create plugins to work on.. &lt;/li&gt;
&lt;/ul&gt;
&lt;h4&gt;
  
  
  gatsby-plugin-sass
&lt;/h4&gt;

&lt;blockquote&gt;
&lt;p&gt;Provides drop-in support for Sass/SCSS stylesheets&lt;br&gt;
&lt;/p&gt;


&lt;/blockquote&gt;

&lt;p&gt;&lt;code&gt;npm install node-sass gatsby-plugin-sass&lt;/code&gt;&lt;br&gt;
&lt;/p&gt;

&lt;p&gt;&lt;a href="https://www.gatsbyjs.com/plugins/gatsby-plugin-sass/?=scss#install"&gt;How to use&lt;/a&gt;&lt;/p&gt;

&lt;h6&gt;
  
  
  extra: If you have a problem with installing the sass plugin then follow these instructions from &lt;a href="https://stackoverflow.com/questions/64625050/error-node-sass-version-5-0-0-is-incompatible-with-4-0-0"&gt;stackoverflow&lt;/a&gt;
&lt;/h6&gt;

&lt;h2&gt;
  
  
  🎨 Give a shape
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;CSS: Apply some basic CSS. If you feel confident with CSS frameworks then you can implement a framework to your gatsby project. &lt;a href="https://www.gatsbyjs.com/docs/tailwind-css/"&gt;Tailwind&lt;/a&gt; or &lt;a href="https://getbootstrap.com/docs/4.5/getting-started/introduction/"&gt;Bootstrap&lt;/a&gt;.&lt;/p&gt;
&lt;/blockquote&gt;




&lt;h2&gt;
  
  
  🚀 Deploy your work
&lt;/h2&gt;

&lt;p&gt;&lt;code&gt;gatsby build&lt;/code&gt; You need this command to build your project.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Always push your work on github (at least 3 times per hour)&lt;/li&gt;
&lt;li&gt;Drag and Drop your &lt;code&gt;public&lt;/code&gt; file to &lt;a href="https://app.netlify.com/drop"&gt;Netlify&lt;/a&gt;, so we can see your CV online!&lt;/li&gt;
&lt;/ul&gt;




&lt;h2&gt;
  
  
  Well done! Nice job 👏
&lt;/h2&gt;

&lt;p&gt;&lt;a href="https://i.giphy.com/media/YRuFixSNWFVcXaxpmX/giphy.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://i.giphy.com/media/YRuFixSNWFVcXaxpmX/giphy.gif" alt="Gif about starting"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  🎣 Tools
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://code.visualstudio.com/"&gt;Visual Studio Code&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.markdownguide.org/"&gt;Markdown&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.gatsbyjs.com/"&gt;Gatsby Framework&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.gatsbyjs.com/starters/?v=2"&gt;Starter Libraries&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.npmjs.com/"&gt;npm&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.netlify.com/"&gt;Netlify&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;




&lt;h3&gt;
  
  
  🖤 Please check my &lt;a href="https://github.com/ezgihendrickx/gatsby-workshop"&gt;Github Repo&lt;/a&gt;&lt;br&gt;
&lt;/h3&gt;

&lt;p&gt;Thank you for reading.&lt;/p&gt;

</description>
      <category>gatsby</category>
      <category>javascript</category>
      <category>react</category>
      <category>webdev</category>
    </item>
    <item>
      <title>11 Golden Rules for A11Y</title>
      <dc:creator>ezgihendrickx</dc:creator>
      <pubDate>Wed, 16 Dec 2020 19:10:29 +0000</pubDate>
      <link>https://dev.to/ezgihendrickx/11-golden-rules-for-a11y-146c</link>
      <guid>https://dev.to/ezgihendrickx/11-golden-rules-for-a11y-146c</guid>
      <description>&lt;h1&gt;
  
  
  Let's make our websites accessible for everyone!
&lt;/h1&gt;

&lt;p&gt;As a self-taught front-end developer, when I discovered the concepts of accessibility and inclusive design a few months ago, I did not know much about it. But I realised that many of us, in this web dev field, also don't know much about it. It is regrettable but accessibility is not the best field to invest in these days. It is just a popular buzzword which sometimes comes in and out of our attention. But we can really make a difference when we decide to start learning more about this. And possibly this would just be a small drop in the ocean but we really need that to achieve our goals. &lt;br&gt;
&lt;em&gt;Are you ready or eager to learn more?&lt;/em&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What does &lt;code&gt;a11y&lt;/code&gt; stand for?
&lt;/h2&gt;

&lt;blockquote&gt;
&lt;p&gt;“a11y” stands for “accessibility.” It is a numeronym, with 11 representing the count of letters between the letter a and the letter y. Other numeronyms you may be familiar with include: i18n (internationalization), P2P (peer to peer) etc.&lt;/p&gt;
&lt;/blockquote&gt;

&lt;h2&gt;
  
  
  11 Golden Rules for Accessibility
&lt;/h2&gt;

&lt;h3&gt;
  
  
  Which steps should we follow when we create a website?
&lt;/h3&gt;

&lt;p&gt;The below rules are important and deserve our attention not only for accessibility but also for the usability of your website.&lt;/p&gt;

&lt;ol&gt;
&lt;li&gt;&lt;p&gt;Always use a meaningful &lt;code&gt;Alt text&lt;/code&gt;:&lt;br&gt;
&lt;strong&gt;Screen readers&lt;/strong&gt; may read out ugly, nonsense filenames to describe images. We don't want that as responsible developers right 😏 ?&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Define the level of accessibility of your website and follow the &lt;strong&gt;guidelines&lt;/strong&gt; : &lt;a href="https://www.w3.org/WAI/WCAG21/quickref/" rel="noopener noreferrer"&gt;Web Content Accessibility Guidelines&lt;/a&gt; &lt;br&gt;
This website should be your holy book when you want to get inspired 📕 .&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Optimise &lt;strong&gt;Color Contrast&lt;/strong&gt;: &lt;a href="https://www.getstark.co/" rel="noopener noreferrer"&gt;Getstark&lt;/a&gt; This is one of the color optimization platforms where you can find more information about optimising colours for accessibility. &lt;br&gt;
&lt;a href="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fwww.getstark.co%2Fsketch-action-2.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fwww.getstark.co%2Fsketch-action-2.png" alt="Color optimization on Sketch"&gt;&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Simplify&lt;/strong&gt; the language: We don't need complicated or sophisticated words to have a website. Someone once said that if you cannot explain your work simply then you don't understand it well enough.. Keep your content always simple and understandable, and keep your layout clear.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;&lt;strong&gt;Lead&lt;/strong&gt; the users: e.g. Always use form labels to describe input fields and place holders. Keep in mind that acceptable input field examples are really handy and useful.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Always provide &lt;strong&gt;captions&lt;/strong&gt; for video content. Without captions it is meaningless to a person with a permanent or temporary visual problem. Never ever have your video automatically begin playing.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Don't forget to test &lt;strong&gt;keyboard navigation&lt;/strong&gt;. A user should have the right to use his/her keyboard to navigate the website. We cannot take this advantage away from them.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create &lt;strong&gt;large buttons!&lt;/strong&gt; You don't have to be a designer to create large buttons. In this way it is more clear that this is a clickable button and it calls an action. &lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Create &lt;strong&gt;understandable links&lt;/strong&gt;: Have you ever thought: "I don't know where to click or where to go"? Yes! This is the reason why we need to be clear when we create links. Every link should have a meaningful reason behind it. So don't just make a href because you love a href..&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Use &lt;strong&gt;semantic&lt;/strong&gt; HTML elements: What on earth is semantic markup? Semantic elements mean elements with a meaning.&lt;br&gt;
&lt;br&gt;
&lt;code&gt;&amp;lt;main&amp;gt;, &amp;lt;nav&amp;gt;, &amp;lt;header&amp;gt;, &amp;lt;section&amp;gt;, &amp;lt;article&amp;gt;, &amp;lt;form&amp;gt;&lt;/code&gt;&lt;br&gt;
&lt;br&gt;
and so on. Semantic elements clearly define its content.&lt;/p&gt;&lt;/li&gt;
&lt;li&gt;&lt;p&gt;Use &lt;strong&gt;ARIA landmark&lt;/strong&gt; roles to add feature context to HTML elements.&lt;br&gt;
&lt;a href="https://www.w3.org/TR/wai-aria-practices/examples/landmarks/main.html" rel="noopener noreferrer"&gt;Aria Landmark Features&lt;/a&gt;&lt;/p&gt;&lt;/li&gt;
&lt;/ol&gt;

&lt;p&gt;If you followed all the golden rules and are not sure where to ask, then ask the community: &lt;a href="https://www.a11yproject.com/" rel="noopener noreferrer"&gt;A11Y Project&lt;/a&gt;; they have the Accessibility Checklist for beginners to guide and enlighten you.. &lt;/p&gt;

&lt;p&gt;In a nutshell, Accessibility and Inclusive Design are really import to increase web content quality and make the standards higher on the web. Everyone has the right to reach your content. We should be more aware of these different aspects of web design and development.. I encourage you to everyday apply one new accessibility guideline on your website and enjoy while teaching to others.&lt;/p&gt;

&lt;p&gt;Useful links to learn more: &lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;&lt;a href="https://www.w3.org/WAI/standards-guidelines/wcag/" rel="noopener noreferrer"&gt;https://www.w3.org/WAI/standards-guidelines/wcag/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.a11yproject.com/" rel="noopener noreferrer"&gt;https://www.a11yproject.com/&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.edx.org/course/web-accessibility-introduction" rel="noopener noreferrer"&gt;https://www.edx.org/course/web-accessibility-introduction&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="https://www.webaccessibility.com/" rel="noopener noreferrer"&gt;https://www.webaccessibility.com/&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Please do not hesitate to give any comment and add more sources or knowledge about accessibility. &lt;/p&gt;

&lt;p&gt;Thank you for reading.&lt;/p&gt;

</description>
      <category>a11y</category>
      <category>webdev</category>
      <category>career</category>
    </item>
  </channel>
</rss>
