<?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: Patrick Ofilada</title>
    <description>The latest articles on DEV Community by Patrick Ofilada (@pcofilada).</description>
    <link>https://dev.to/pcofilada</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%2F321065%2F2061369d-e5bb-4885-8c65-78ca2875a1f7.png</url>
      <title>DEV Community: Patrick Ofilada</title>
      <link>https://dev.to/pcofilada</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/pcofilada"/>
    <language>en</language>
    <item>
      <title>I rebuilt my portfolio as a chat window with live visitors</title>
      <dc:creator>Patrick Ofilada</dc:creator>
      <pubDate>Sat, 14 Nov 2026 13:45:10 +0000</pubDate>
      <link>https://dev.to/pcofilada/i-rebuilt-my-portfolio-as-a-chat-window-with-live-visitors-493i</link>
      <guid>https://dev.to/pcofilada/i-rebuilt-my-portfolio-as-a-chat-window-with-live-visitors-493i</guid>
      <description>&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw33arf29848vn4a1pv81.gif" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fw33arf29848vn4a1pv81.gif" alt="demo" width="720" height="739"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;My new site, &lt;a href="https://patrickofilada.dev" rel="noopener noreferrer"&gt;https://patrickofilada.dev&lt;/a&gt;, is one page that behaves like an AI chat. It "thinks" through a few steps, streams in a short intro, and answers "show me your work" with my work history.&lt;/p&gt;

&lt;p&gt;The idea comes from Eduardo Alba's site (&lt;a href="https://eduardoalba.com" rel="noopener noreferrer"&gt;https://eduardoalba.com&lt;/a&gt;). I liked it so much that I built my own version.&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;How it's put together&lt;/strong&gt;&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Next.js on AWS Amplify. The work history loads only when someone asks for it, so the first page stays light.&lt;/li&gt;
&lt;li&gt;Live visitors on a Cloudflare Worker with a Durable Object. One small service tracks who's on the page, shares cursors and clicks, and counts visits by country for the dotted world map. It runs on the free plan, and if it goes down the page simply works without it.&lt;/li&gt;
&lt;li&gt;Weather in the footer comes from MET Norway's free forecast, cached for 30 minutes so the API isn't hit on every visit.&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkqz5yauircsy0hvjz3aj.png" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fkqz5yauircsy0hvjz3aj.png" alt="experience" width="800" height="477"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;&lt;strong&gt;What I'd tell anyone building something similar:&lt;/strong&gt; make every live part optional. The page should be complete without it, and the live layer should add to it.&lt;/p&gt;

&lt;p&gt;Open it in two tabs, or with a friend, and you'll see the cursors.&lt;/p&gt;

</description>
      <category>ai</category>
      <category>productivity</category>
      <category>programming</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Simple React Folder Structure</title>
      <dc:creator>Patrick Ofilada</dc:creator>
      <pubDate>Tue, 25 Aug 2020 02:54:14 +0000</pubDate>
      <link>https://dev.to/pcofilada/simple-react-folder-structure-31lj</link>
      <guid>https://dev.to/pcofilada/simple-react-folder-structure-31lj</guid>
      <description>&lt;p&gt;So you manage to finish all of those tutorial and you already run those generate commands, so what's next? Most of the time after generating new react project developers don't know where to put or organize their codes.&lt;/p&gt;

&lt;p&gt;&lt;a href="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fjivw790nf88oen304aup.jpg" class="article-body-image-wrapper"&gt;&lt;img src="https://media2.dev.to/dynamic/image/width=800%2Cheight=%2Cfit=scale-down%2Cgravity=auto%2Cformat=auto/https%3A%2F%2Fdev-to-uploads.s3.amazonaws.com%2Fi%2Fjivw790nf88oen304aup.jpg" alt="Developer" width="800" height="535"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;p&gt;After doing some research, trial and error on different react projects, I found the folder structure that works best for me and for my team.&lt;/p&gt;

&lt;p&gt;This article is opinionated and you are welcome to adjust it for your own use case. Here's how I organize my React applications:&lt;br&gt;
&lt;/p&gt;

&lt;div class="highlight js-code-highlight"&gt;
&lt;pre class="highlight plaintext"&gt;&lt;code&gt;.
├── README.md
├── package.json
├── tsconfig.json
├── public/
└── src/
    ├── index.tsx
    ├── routes.ts
    ├── api/
    ├── assets/
    ├── config/
    ├── containers/
    ├── context/
    ├── types/
    ├── utils/
    └── components/
        └── common/
&lt;/code&gt;&lt;/pre&gt;

&lt;/div&gt;



&lt;h4&gt;
  
  
  Here's a quick overview for each item or folder.
&lt;/h4&gt;

&lt;p&gt;&lt;code&gt;src/&lt;/code&gt; - Contains all of our react codebase.&lt;br&gt;
&lt;code&gt;index.tsx&lt;/code&gt; - Base react component. If you are not using typescript just change this to &lt;em&gt;'index.js'&lt;/em&gt; or &lt;em&gt;'index.jsx'&lt;/em&gt;.&lt;br&gt;
&lt;code&gt;routes.ts&lt;/code&gt; - App navigation. If you are not using typescript just change this to &lt;em&gt;'routes.js'&lt;/em&gt;.&lt;br&gt;
&lt;code&gt;api/&lt;/code&gt; - Api call related functions.&lt;br&gt;
&lt;code&gt;assets/&lt;/code&gt; - Images, fonts and other static files.&lt;br&gt;
&lt;code&gt;config/&lt;/code&gt; - Config files&lt;br&gt;
&lt;code&gt;containers/&lt;/code&gt; - &lt;a href="https://medium.com/@thejasonfile/dumb-components-and-smart-components-e7b33a698d43" rel="noopener noreferrer"&gt;Smart Components&lt;/a&gt;&lt;br&gt;
&lt;code&gt;context/&lt;/code&gt; - &lt;a href="https://reactjs.org/docs/context.html" rel="noopener noreferrer"&gt;React context&lt;/a&gt;&lt;br&gt;
&lt;code&gt;types/&lt;/code&gt; - Typescript related files or functions.&lt;br&gt;
&lt;code&gt;utils/&lt;/code&gt; - Helper functions&lt;br&gt;
&lt;code&gt;components/&lt;/code&gt; - &lt;a href="https://medium.com/@thejasonfile/dumb-components-and-smart-components-e7b33a698d43" rel="noopener noreferrer"&gt;Dumb Components&lt;/a&gt;&lt;br&gt;
&lt;code&gt;components/common/&lt;/code&gt; - Shared components&lt;/p&gt;

&lt;p&gt;You can check this folder structure &lt;a href="https://github.com/pcofilada/simple-react-starter" rel="noopener noreferrer"&gt;here&lt;/a&gt;.&lt;br&gt;
If you are also using redux on your react application you can check how does it looks &lt;a href="https://github.com/pcofilada/simple-react-starter/tree/redux" rel="noopener noreferrer"&gt;here&lt;/a&gt;.&lt;br&gt;
I have implemented it with React Native application also, check it &lt;a href="https://github.com/pcofilada/simple-react-native-starter" rel="noopener noreferrer"&gt;here&lt;/a&gt;.&lt;/p&gt;

&lt;h2&gt;
  
  
  Wrap Up
&lt;/h2&gt;

&lt;p&gt;If you have any questions or recommendations, please leave them in the comments below.&lt;/p&gt;

&lt;p&gt;Thanks for reading.&lt;/p&gt;

</description>
      <category>react</category>
      <category>javascript</category>
      <category>typescript</category>
      <category>beginners</category>
    </item>
  </channel>
</rss>
