<?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: Aya Abounacer</title>
    <description>The latest articles on DEV Community by Aya Abounacer (@aya_abounacer_3d229894639).</description>
    <link>https://dev.to/aya_abounacer_3d229894639</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%2F4083773%2F209ab26e-66d6-4cdb-afcf-576faead7fab.png</url>
      <title>DEV Community: Aya Abounacer</title>
      <link>https://dev.to/aya_abounacer_3d229894639</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/aya_abounacer_3d229894639"/>
    <language>en</language>
    <item>
      <title>We built a developer portfolio generator using only the public GitHub API</title>
      <dc:creator>Aya Abounacer</dc:creator>
      <pubDate>Tue, 18 Aug 2026 18:25:39 +0000</pubDate>
      <link>https://dev.to/aya_abounacer_3d229894639/we-built-a-developer-portfolio-generator-using-only-the-public-github-api-26g7</link>
      <guid>https://dev.to/aya_abounacer_3d229894639/we-built-a-developer-portfolio-generator-using-only-the-public-github-api-26g7</guid>
      <description>&lt;p&gt;My collaborator and I have been working on an early version of a project called &lt;strong&gt;RepoFolio&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The idea is simple:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Enter your GitHub username → get a customizable developer portfolio.&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;RepoFolio uses your public GitHub profile and repositories to generate a portfolio that you can then edit and personalize.&lt;/p&gt;

&lt;h2&gt;
  
  
  What it currently does
&lt;/h2&gt;

&lt;p&gt;You can:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Generate a portfolio from a GitHub username&lt;/li&gt;
&lt;li&gt;Automatically pull profile information and repositories&lt;/li&gt;
&lt;li&gt;Select which projects you want to show&lt;/li&gt;
&lt;li&gt;Mark one project as featured&lt;/li&gt;
&lt;li&gt;Edit project titles, descriptions and technologies&lt;/li&gt;
&lt;li&gt;Add experience, education and other sections&lt;/li&gt;
&lt;li&gt;Choose between different portfolio templates&lt;/li&gt;
&lt;li&gt;Customize colors and appearance&lt;/li&gt;
&lt;li&gt;Preview the result on desktop and mobile&lt;/li&gt;
&lt;li&gt;Share the generated portfolio&lt;/li&gt;
&lt;li&gt;Export it as a PDF&lt;/li&gt;
&lt;li&gt;Automatically save edits locally in the browser&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There is currently &lt;strong&gt;no signup or authentication required&lt;/strong&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Current stack
&lt;/h2&gt;

&lt;p&gt;The first version is intentionally simple:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;React&lt;/li&gt;
&lt;li&gt;TypeScript&lt;/li&gt;
&lt;li&gt;Vite&lt;/li&gt;
&lt;li&gt;Tailwind CSS&lt;/li&gt;
&lt;li&gt;GitHub REST API&lt;/li&gt;
&lt;li&gt;localStorage for draft persistence&lt;/li&gt;
&lt;li&gt;Vitest for testing&lt;/li&gt;
&lt;li&gt;Vercel for deployment&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;There is currently &lt;strong&gt;no custom backend or database&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;The frontend talks directly to the public GitHub API, and the portfolio state can be shared through a serialized URL.&lt;/p&gt;

&lt;p&gt;Later, if the project proves useful, we are considering adding persistent URLs such as:&lt;/p&gt;

&lt;p&gt;&lt;code&gt;repofolio.dev/username&lt;/code&gt;&lt;/p&gt;

&lt;p&gt;That would be the point where a backend/database would actually become justified.&lt;/p&gt;

&lt;h2&gt;
  
  
  Why are we sharing it this early?
&lt;/h2&gt;

&lt;p&gt;This is still an &lt;strong&gt;early testing version&lt;/strong&gt;.&lt;/p&gt;

&lt;p&gt;There are important improvements we already want to make across:&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;UI/UX&lt;/li&gt;
&lt;li&gt;portfolio generation quality&lt;/li&gt;
&lt;li&gt;templates and design&lt;/li&gt;
&lt;li&gt;customization&lt;/li&gt;
&lt;li&gt;sharing&lt;/li&gt;
&lt;li&gt;project selection&lt;/li&gt;
&lt;li&gt;overall polish&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;But instead of building everything based only on our own assumptions, we want to see how real developers actually use it first.&lt;/p&gt;

&lt;p&gt;The main question we are trying to answer is:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;Would you actually use a portfolio generated by RepoFolio on your CV, LinkedIn profile, GitHub profile, or job applications?&lt;/strong&gt;&lt;/p&gt;

&lt;p&gt;If the answer is no, we would really like to understand why.&lt;/p&gt;

&lt;h2&gt;
  
  
  Try it
&lt;/h2&gt;

&lt;p&gt;🔗 &lt;a href="https://repofolio-ochre.vercel.app/" rel="noopener noreferrer"&gt;https://repofolio-ochre.vercel.app/&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;No signup required.&lt;/p&gt;

&lt;p&gt;If you try it, feel free to be critical.&lt;/p&gt;

&lt;p&gt;Things that are confusing, unfinished, unnecessary, badly designed, or missing are much more useful to us right now than just hearing that it looks good.&lt;/p&gt;

&lt;p&gt;We also created a short feedback form if you have a few extra minutes:&lt;/p&gt;

&lt;p&gt;📝 &lt;a href="https://docs.google.com/forms/d/e/1FAIpQLScViwT5a1FR1XuvfmSKeHr80gbsRatvn6j_HMtfF5gWskmDHg/viewform" rel="noopener noreferrer"&gt;https://docs.google.com/forms/d/e/1FAIpQLScViwT5a1FR1XuvfmSKeHr80gbsRatvn6j_HMtfF5gWskmDHg/viewform&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;I’d also be interested to hear from other developers:&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;If you were building this, what would you prioritize next?&lt;/strong&gt;&lt;/p&gt;

&lt;h1&gt;
  
  
  react #typescript #webdev #github
&lt;/h1&gt;

</description>
      <category>react</category>
      <category>typescript</category>
      <category>webdev</category>
      <category>github</category>
    </item>
  </channel>
</rss>
