<?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: Asraful Hoque emon</title>
    <description>The latest articles on DEV Community by Asraful Hoque emon (@asraful_hoque).</description>
    <link>https://dev.to/asraful_hoque</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.us-east-2.amazonaws.com%2Fuploads%2Fuser%2Fprofile_image%2F4255518%2F7c5fd918-4a47-45e4-b684-1e58842d2603.png</url>
      <title>DEV Community: Asraful Hoque emon</title>
      <link>https://dev.to/asraful_hoque</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/asraful_hoque"/>
    <language>en</language>
    <item>
      <title>From Figma to a Live Website: My 4-Step Build Process</title>
      <dc:creator>Asraful Hoque emon</dc:creator>
      <pubDate>Fri, 20 Nov 2026 14:12:28 +0000</pubDate>
      <link>https://dev.to/asraful_hoque/from-figma-to-a-live-website-my-4-step-build-process-5aga</link>
      <guid>https://dev.to/asraful_hoque/from-figma-to-a-live-website-my-4-step-build-process-5aga</guid>
      <description>&lt;p&gt;Clients often come to me with a Figma file and one worry: will the live site actually look like this? It should, and it should load fast and be easy to edit too. This is the process I follow on every build, whether the site ends up in WordPress, Webflow or Next.js.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;1. Brief: agree on the goal before the pixels&lt;/strong&gt;&lt;br&gt;
Before I open the design, I want to know what the site is for. Who visits it, what should they do, and who will update it later? From that I recommend a stack and confirm the scope, the price and the deadline in writing. A clear brief prevents most of the problems that show up at the end of a project.&lt;/p&gt;

&lt;p&gt;Pages and templates needed, and which ones repeat&lt;br&gt;
Content that the team will edit, so I can plan the CMS fields&lt;br&gt;
Forms, integrations and anything that needs a backend&lt;br&gt;
SEO basics: target keywords, existing URLs that must keep working&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;2. Design: check the Figma file like a developer&lt;/strong&gt;&lt;br&gt;
If the design is not finished, I design the key screens in Figma first and we polish them together. If it is finished, I review it the way a browser will see it:&lt;/p&gt;

&lt;p&gt;Responsive states. Is there a mobile and tablet version? If not, I propose one before building.&lt;br&gt;
Components. Buttons, cards and sections that repeat become reusable components, so the site stays consistent.&lt;br&gt;
Type and spacing. I turn these into a small set of design tokens: a type scale, a spacing scale and colours.&lt;br&gt;
Assets. Images are exported at the right size and converted to WebP or AVIF.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;3. Build: frontend, CMS and backend together&lt;/strong&gt;&lt;br&gt;
I build the frontend and the content structure at the same time, so the CMS matches what the design needs. In WordPress that means a custom theme with custom post types and fields. In Webflow, CMS collections with sensible templates. In Next.js, typed components fed by a headless CMS or an API.&lt;/p&gt;

&lt;p&gt;Clients get a staging link early and regular updates, so they can review real pages in a real browser instead of waiting for a big reveal. Semantic HTML, accessible markup and clean headings go in from the start, not as a fix at the end.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;4. Launch: speed, SEO and device checks&lt;/strong&gt;&lt;br&gt;
Before the site goes live, I run through a launch checklist:&lt;/p&gt;

&lt;p&gt;Performance: Core Web Vitals, image sizes, caching and unused scripts.&lt;br&gt;
SEO: titles, meta descriptions, Open Graph tags, schema markup, an XML sitemap and robots.txt.&lt;br&gt;
Redirects from old URLs, so existing rankings are not lost.&lt;br&gt;
Testing on real phones and the main browsers.&lt;br&gt;
Forms and integrations tested end to end.&lt;br&gt;
Then I deploy, connect Google Search Console and hand over a short guide so the team can manage the site on their own.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;A Figma design is a promise. The build is where you keep it.&lt;/strong&gt;&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>wordpress</category>
      <category>beginners</category>
      <category>career</category>
    </item>
  </channel>
</rss>
