<?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: Ahmad Shadeed</title>
    <description>The latest articles on DEV Community by Ahmad Shadeed (@shadeed).</description>
    <link>https://dev.to/shadeed</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%2F162782%2Fb2a28184-1234-4059-9c90-23523bc86710.jpeg</url>
      <title>DEV Community: Ahmad Shadeed</title>
      <link>https://dev.to/shadeed</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/shadeed"/>
    <language>en</language>
    <item>
      <title>The Process of Implementing A UI Design From Scratch</title>
      <dc:creator>Ahmad Shadeed</dc:creator>
      <pubDate>Wed, 01 May 2019 15:59:03 +0000</pubDate>
      <link>https://dev.to/shadeed/the-process-of-implementing-a-ui-design-from-scratch-4cea</link>
      <guid>https://dev.to/shadeed/the-process-of-implementing-a-ui-design-from-scratch-4cea</guid>
      <description>&lt;p&gt;&lt;em&gt;This post has been originally shared on my blog and it's a bit long, so I will share the introduction and you can continue reading it on the blog.&lt;/em&gt;&lt;/p&gt;

&lt;p&gt;There are many ways to build a layout in HTML &amp;amp; CSS, and every developer has his own way of doing it. Getting to know the thinking process inside a Front End Developer mind is extremely useful, as it gives us different perspectives on how to solve certain problems.&lt;/p&gt;

&lt;p&gt;In this article, I will dive into the journey of building some of the components in a project I called “Nadros”, and write down my thought process, from the perspective of a designer and a developer.&lt;/p&gt;

&lt;p&gt;Nadros is an imaginative idea for an online video courses platform. In this article, I’ll focus on building the header component.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--8q6JX6ZZ--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/3rfvyhm4emxffkmrpv0v.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--8q6JX6ZZ--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/3rfvyhm4emxffkmrpv0v.png" alt=""&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Design Components
&lt;/h2&gt;

&lt;p&gt;I extracted all components into one page so I could look at them together. This would make it easy to find inconsistencies between UI elements. Also, having all of them at once can lead to ways for unifying some UI components, or to create a variety of specific components.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://res.cloudinary.com/practicaldev/image/fetch/s--AXSoYool--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/x3biy5v5ubslepkjhsdz.png" class="article-body-image-wrapper"&gt;&lt;img src="https://res.cloudinary.com/practicaldev/image/fetch/s--AXSoYool--/c_limit%2Cf_auto%2Cfl_progressive%2Cq_auto%2Cw_880/https://thepracticaldev.s3.amazonaws.com/i/x3biy5v5ubslepkjhsdz.png" alt=""&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Continue reading my &lt;a href="https://ishadeed.com/article/building-ui-design-scratch/"&gt;blog&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Let me know your thoughts please!&lt;/p&gt;

</description>
      <category>design</category>
      <category>css</category>
      <category>frontend</category>
    </item>
  </channel>
</rss>
