<?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: Emilio</title>
    <description>The latest articles on DEV Community by Emilio (@emilio_fe2e094086422b655f).</description>
    <link>https://dev.to/emilio_fe2e094086422b655f</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%2F3997889%2Fc05b41c1-d405-4bb4-adbf-090f9b9339cb.png</url>
      <title>DEV Community: Emilio</title>
      <link>https://dev.to/emilio_fe2e094086422b655f</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/emilio_fe2e094086422b655f"/>
    <language>en</language>
    <item>
      <title>I built a developer portfolio template with React, Vite &amp; Tailwind — here's what I learned</title>
      <dc:creator>Emilio</dc:creator>
      <pubDate>Tue, 23 Jun 2026 03:50:27 +0000</pubDate>
      <link>https://dev.to/emilio_fe2e094086422b655f/i-built-a-developer-portfolio-template-with-react-vite-tailwind-heres-what-i-learned-4113</link>
      <guid>https://dev.to/emilio_fe2e094086422b655f/i-built-a-developer-portfolio-template-with-react-vite-tailwind-heres-what-i-learned-4113</guid>
      <description>&lt;p&gt;As a systems engineering student and frontend dev, I wanted a portfolio that&lt;br&gt;
looked professional without spending days fighting with design. So I built one —&lt;br&gt;
and ended up turning it into a reusable template.&lt;/p&gt;

&lt;p&gt;Here's what I focused on while building it:&lt;/p&gt;

&lt;h2&gt;
  
  
  1. Customization from a single file
&lt;/h2&gt;

&lt;p&gt;The biggest pain with most templates is digging through components to change&lt;br&gt;
your info. I put everything — name, bio, projects, skills, social links — into&lt;br&gt;
ONE config file. Edit that, and the whole site updates.&lt;/p&gt;

&lt;h2&gt;
  
  
  2. Light &amp;amp; dark mode
&lt;/h2&gt;

&lt;p&gt;Developers love dark mode, so I made it the default, with a smooth toggle for&lt;br&gt;
light mode. Both are fully themed.&lt;/p&gt;

&lt;h2&gt;
  
  
  3. Mobile-first &amp;amp; responsive
&lt;/h2&gt;

&lt;p&gt;Most people will view a portfolio on their phone, so I built it mobile-first&lt;br&gt;
and tested it down to small screens.&lt;/p&gt;

&lt;h2&gt;
  
  
  4. Easy deployment
&lt;/h2&gt;

&lt;p&gt;It works out of the box with Vercel or any static host, with a beginner-friendly&lt;br&gt;
setup guide in the README.&lt;/p&gt;

&lt;h2&gt;
  
  
  The stack
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;React + Vite&lt;/li&gt;
&lt;li&gt;Tailwind CSS&lt;/li&gt;
&lt;li&gt;Formspree-ready contact form&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;You can see the live demo here: devfolio-template-vercel-app.vercel.app&lt;/p&gt;

&lt;p&gt;I also made it available as a template if it's useful to anyone: &lt;a href="https://payhip.com/b/t1VUk" rel="noopener noreferrer"&gt;https://payhip.com/b/t1VUk&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;Would love to hear your feedback — what do you look for in a developer portfolio?&lt;/p&gt;

&lt;h1&gt;
  
  
  react #webdev #tailwindcss #showdev
&lt;/h1&gt;

</description>
      <category>frontend</category>
      <category>react</category>
      <category>showdev</category>
      <category>tailwindcss</category>
    </item>
  </channel>
</rss>
