<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Adejolanu on Medium]]></title>
        <description><![CDATA[Stories by Adejolanu on Medium]]></description>
        <link>https://medium.com/@adejolanu?source=rss-3d38ab323a31------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*dmbNkD5D-u45r44go_cf0g.png</url>
            <title>Stories by Adejolanu on Medium</title>
            <link>https://medium.com/@adejolanu?source=rss-3d38ab323a31------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Thu, 19 Nov 2026 13:50:23 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@adejolanu/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[How I Debugged My Budget App and Added an AI Feature (Pocketly)]]></title>
            <link>https://medium.com/@adejolanu/how-i-debugged-my-budget-app-and-added-an-ai-feature-pocketly-52443f2c6c12?source=rss-3d38ab323a31------2</link>
            <guid isPermaLink="false">https://medium.com/p/52443f2c6c12</guid>
            <dc:creator><![CDATA[Adejolanu]]></dc:creator>
            <pubDate>Sat, 18 Jul 2026 10:53:11 GMT</pubDate>
            <atom:updated>2026-07-18T10:53:11.216Z</atom:updated>
            <content:encoded><![CDATA[<p>I built a personal budgeting app called Pocketly. It helps track income, savings, and spending across categories like food, transport, and subscriptions. It sounds simple. It was not always simple to build. Here is what went wrong, how I fixed it, and the AI feature I added at the end.</p><h3>The category that would not update</h3><p>My app lets users set a budget for each spending category, like “miscellaneous” or “food.” I noticed my miscellaneous input would not go past a certain number. I typed in a bigger amount, and it just snapped back.</p><p>At first I thought there was a hardcoded limit somewhere. There was not. The real issue was how I checked the total budget. My code checked the total on every single keystroke. So if I typed “44000” one digit at a time, and an in-between number briefly went over my budget, that keystroke got rejected. The input field looked frozen.</p><p>The fix was simple. Stop blocking the input while typing. Instead, let the user type freely, and just show a warning message if the total goes over budget. This way, typing feels normal, and the warning does its job without getting in the way.</p><h3>The missing naira</h3><p>Next, I found a strange bug. I logged an expense of 3,800 naira. My app showed 3,799. Exactly one naira short.</p><p>I checked my math functions. They were fine. So the bug was not in my code at all. It was a number input trap (scrolling). Number inputs in the browser let you change the value by scrolling your mouse wheel over the field. If your cursor is resting on the input and you scroll the page, the number quietly changes by one.</p><p>The fix was one line. I added a small function that removes focus from the input the moment a scroll is detected. Now scrolling the page cannot accidentally change any number field.</p><h3>Building an API route in the wrong place</h3><p>I wanted to add a feature that recommends a budget split based on income. I started building this as a Next.js API route (I guess i didn’t search properly online). The problem was my app was not built with Next.js. It was built with Vite.</p><p>This mattered a lot. Vite is just a frontend tool. It does not run backend routes on its own. Next.js has a different system for that, with files like route.js inside an app/api folder. None of that works in Vite.</p><p>Once I understood this, I had two paths. I could write the logic to run fully in the browser, since it did not need a server. Or I could build a small backend using Express, a lightweight Node.js server, to handle the request separately from my frontend.</p><p>I first tried the simple browser-only version, since my budget logic was just math based on income tiers. It worked instantly, no server needed.</p><h3>Adding real AI</h3><p>Later, I decided to make the recommendation smarter. Instead of fixed rules, I wanted an actual AI model to look at the user’s income and suggest a budget split. This meant using Google’s Gemini model through the Vercel AI SDK.</p><p>This is where I needed a real backend, because API keys must never sit in frontend code. Anyone could open the browser tools and steal it. So I built a small Express server to hold the AI logic and keep the key safe on the server side, never sent to the browser.</p><p>I ran into a few more bumps along the way. My first attempt used an outdated Gemini model name that had been retired. My server could not find my API key at first, because my .env file was not saved in the right folder. My server also has to run as a separate process alongside my frontend, so I needed two terminals open at once, or a tool called concurrently to run both together.</p><p>Once all these pieces were in place, the feature worked. A user enters their income, clicks a button, and the AI returns a suggested savings percentage, a spending percentage, and a breakdown across categories like food and transport. My app then converts these percentages into real naira amounts and updates the user’s budget automatically.</p><h3>A costly mistake with git</h3><p>While pushing my code to GitHub, I ran into a wall. My push kept failing. It turned out my .env file, the one holding my real API key, had been committed to my repository by accident. I thought .gitignore protected it, but the file was never actually listed there.</p><p>GitHub has a built in scanner that blocks pushes containing exposed keys. This is a good thing. It caught my mistake before it could cause real damage. I had to remove the file from git’s tracking, add it properly to .gitignore, and in this case, rewrite my repository&#39;s history to fully erase the key from every past commit. Then I rotated the key, meaning I deleted the old one and created a fresh one, just to be safe.</p><p>The lesson here is simple. Always check that your .gitignore file actually contains .env before your first commit, not after.</p><h3>Moving to Vercel</h3><p>The last piece was deployment. I planned to host my app on Vercel. But Vercel does not run a server the way my local machine did. It uses serverless functions instead, meaning each request runs on demand rather than through one constantly running process.</p><p>This meant restructuring my backend code. Instead of an Express server with app.listen(), I moved my AI logic into a single file inside an api folder at the root of my project. Vercel automatically treats this as a working endpoint, matching the same /api/recommendation path my frontend already called. No extra server needed. I also moved my API key into Vercel&#39;s own environment variable settings, rather than relying on a .env file at all.</p><h3>What I learned</h3><p>Most of these bugs were not really about budgeting logic. They were about small details: how number inputs behave, where files need to live, what tool is actually running my code, and how to keep secrets safe. Each one taught me something I will carry into the next project.</p><p>Pocketly now does what I set out to build. It tracks spending, warns when a category goes over budget, and uses AI to recommend a smart starting budget based on real income. Simple idea. A lot of small lessons to get there.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=52443f2c6c12" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week in the life of a Frontend Engineer -Bloom After(Part 4 and the end)]]></title>
            <link>https://medium.com/@adejolanu/week-in-the-life-of-a-frontend-engineer-bloom-after-part-4-and-the-end-6a9a02f1ade8?source=rss-3d38ab323a31------2</link>
            <guid isPermaLink="false">https://medium.com/p/6a9a02f1ade8</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Adejolanu]]></dc:creator>
            <pubDate>Sat, 28 Mar 2026 07:45:48 GMT</pubDate>
            <atom:updated>2026-03-28T07:45:48.961Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sfhVXjnDI7mSnnuKcr9zYA.png" /></figure><p>Whewwwwwww, chilee, what a month! This month was a rollercoaster of everything, but this week, this week was when I did the most on Bloom After. <br>Although i’ve still got my final paper on Monday (thanks to the Eid holidays) I decided to put in work into the project and trust me when i say my patience was tested. Bugs are insaneeeee.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8jcsKEs1sdpj36txvpqXDQ.jpeg" /></figure><p>I tried everything to the best of my ability but the carousel that I worked on last week stopped centering the individual cards for some reason. I’m guessing the track width wasn’t wide enough to accomodate the gaps in between the cards in addition to the card width itself(I just spilled some cap to sound intelligent. Don’t be fooled). Anyways I had to stop forming hard girl and ask for help on the team’s slack channel. Grace said she’d look into it (what a lifesaver).</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/500/1*9Lklq_tA34vIMUncUvvWDA.jpeg" /></figure><p>The Crisis Handling page and FAQ on the landing page was also in my jurisdiction and I did that to the best of my ability, handling responsivesness and all. Although there were minor UI changes to what I thought was already good to fly. All in All, I’m glad I was able to contribute to this project. I’m super grateful for the likes of Chijioke, Grace, Nanji, and Prisca, they were really patient with me, especially Nanji.</p><p>Everyone on the team did exceptionally well and I’m glad I got paired up with them. It was a very interesting month but we did it!<br>Catch us live soon and see you next time!</p><p><em>Contributors:</em></p><ol><li>Nanji Lakan — <a href="https://medium.com/@Youtenstudio/bloom-after-week-4-the-last-sprint-the-first-goodbye-80def0e964d1">Medium</a></li><li>Grace Olabode -<a href="https://dev.to/grace_olabode_3be546efe9b/wrapping-up-bloom-after-week-4-polish-full-sprint-retro-p2m">DevTo</a></li><li>Chijioke Uzodinma -Medium</li><li>Prisca Onyemaechi -Medium</li><li>Genevieve Agugua -Medium</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6a9a02f1ade8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week In the Life of a Frontend Engineer (Bloom After) part 3]]></title>
            <link>https://medium.com/@adejolanu/week-in-the-life-of-a-frontend-engineer-bloom-after-part-3-622b55eb4e0a?source=rss-3d38ab323a31------2</link>
            <guid isPermaLink="false">https://medium.com/p/622b55eb4e0a</guid>
            <dc:creator><![CDATA[Adejolanu]]></dc:creator>
            <pubDate>Sat, 21 Mar 2026 10:27:50 GMT</pubDate>
            <atom:updated>2026-03-21T10:39:40.399Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sfhVXjnDI7mSnnuKcr9zYA.png" /></figure><p>This week felt like a marathon (with no medal btw).</p><p>It started with a battle. I went head-to-head with an exam that, frankly, was tough. I’m still waiting on the results, but there’s a specific kind of peace that comes with knowing you gave it everything you had. I did close to my best, that has to be enough… right?.</p><p>But as soon as I closed my textbooks, work slid in.</p><p>I’ve been deep in the trenches of our landing page updates. Everything was moving smoothly until I was told to make a feature carousel on mobile view. I tried to use a framework (Swiper) to get it done, but it just decided to go against me. It kept breaking the code and throwing the design off-balance. After a bit of back-and-forth, I decided to build it from scratch.</p><p>I got to work with my AI companion by my side. I had to understand <em>why</em> it worked. I’m the type of person who doesn’t really know how to rest until a solution is found, so I spent hours tweaking and refining. There’s a unique kind of “fun” in that frustration, the moment it finally clicks and the elements slide perfectly into place.</p><p>Looking at the final result, I’ll be honest: I felt a tiny sting of envy. Seeing the deep functionalities on the other pages made mine feel a bit simple. But then I looked at the site as a whole, it looks superb, and the team has done an incredible job. I’m reminding myself that it’s all about baby steps.</p><p>I’m ending the week feeling good both as a frontend engineer and a student. Now, all my energy is going toward Nanji and Grace for our presentation today. I know they’re going to crush it.</p><p>Stay tuned for more updates the journey is just getting started.</p><p><strong>Contributors</strong>:</p><ol><li>Nanji Lakan — <a href="https://medium.com/@Youtenstudio/bloom-after-week-3-building-the-rooms-nobody-sees-aa9b7dbf8f5a">Medium</a></li><li>Grace Olabode- <a href="https://dev.to/grace_olabode_3be546efe9b/building-with-care-week-3-hardware-hiccups-the-ngo-directory-and-keeping-code-dry-fo8">Medium</a></li><li>Prisca Onyemaechi</li><li>Uzodinma Chijioke</li><li>Agugua Genevieve</li><li>Christine Nyakio</li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=622b55eb4e0a" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week in the Life of a Frontend Engineer — Bloom After (Part 2)]]></title>
            <link>https://medium.com/@adejolanu/week-in-the-life-of-a-frontend-engineer-bloom-after-part-2-35b57ee60ce8?source=rss-3d38ab323a31------2</link>
            <guid isPermaLink="false">https://medium.com/p/35b57ee60ce8</guid>
            <category><![CDATA[front-end-development]]></category>
            <category><![CDATA[teamwork]]></category>
            <dc:creator><![CDATA[Adejolanu]]></dc:creator>
            <pubDate>Sat, 14 Mar 2026 10:28:43 GMT</pubDate>
            <atom:updated>2026-03-14T10:28:43.753Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sfhVXjnDI7mSnnuKcr9zYA.png" /></figure><p>Okay, let’s be real: your girl did <em>not</em> do much this week. If the “Engineer” part of my title was a progress bar, it was hovering at about 15%.</p><p>I spent most of my time wrestling with exams and the entire landing page, trying to make the code actually look like the new Figma designs. It’s still very much “under construction” (aren’t we all?), but it’s getting there.</p><p>The truth is, I’m still figuring out this whole prioritization thing. Being in my final year means exams are currently eating my soul, and the pressure is just… <em>werserrrrrr</em>.</p><p>I’m doing what I can in between past questions and library runs. But trust me, once I get these exams out of my face, I’m back to the dev grind full-time. Catch you on the flip side — we’re almost there, babyyyy! 🚀</p><p>Oh! Big shout out to Nanji Lakan by the way, she didn’t make me feel like a complete loser and completely understood my plight. Thank you queen!!</p><p><em>Contributors:</em></p><ol><li>Nanji Lakan — <a href="https://medium.com/@Youtenstudio/bloom-after-week-2-when-the-code-starts-talking-back-d650a9f7096c">Medium</a></li><li>Grace Olabode — <a href="https://dev.to/grace_olabode_3be546efe9b/building-the-search-my-week-2-progress-on-bloom-after-4cja">Medium</a></li><li>Chinetam Prisca — <a href="https://medium.com/@priscaonyemaechi26/keeping-bloom-after-organized-my-week-1-experience-a693e3affc60">Medium</a></li><li>Uzodinma Chijioke — <a href="https://dev.to/chijioke_uzodinma_d6ae6ef/turning-plans-into-code-my-week-2-progress-on-bloom-after-7jk">Medium</a></li><li>Christine Nyiako — <a href="https://open.substack.com/pub/techbytesbykris/p/bloom-after-scaling-support-through?utm_campaign=post-expanded-share&amp;utm_medium=web">Medium</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=35b57ee60ce8" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Week in the life of a Frontend Engineering Intern ‍ (Bloom After)]]></title>
            <link>https://medium.com/@adejolanu/week-in-the-life-of-a-frontend-engineering-intern-bloom-after-655b42485bfe?source=rss-3d38ab323a31------2</link>
            <guid isPermaLink="false">https://medium.com/p/655b42485bfe</guid>
            <category><![CDATA[teamwork]]></category>
            <category><![CDATA[frontend-development]]></category>
            <category><![CDATA[work]]></category>
            <dc:creator><![CDATA[Adejolanu]]></dc:creator>
            <pubDate>Sat, 07 Mar 2026 07:54:26 GMT</pubDate>
            <atom:updated>2026-03-07T07:54:26.862Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sfhVXjnDI7mSnnuKcr9zYA.png" /></figure><p>Welcome to March and happy women’s month ☺️. Although we just ended the first week of the month, I have already learned a lot. While i have stories to tell for days about how my week went, let’s just put the pin on work. <br>This week, many projects were introduced in honor of IWD — Luminary, Bloom After &amp; Ekehi. I chose to join Bloom After because they target mothers who are battling postpartum depression and help them get the support they need either through foundations or clinics that act as partners — something I would most likely go through.</p><p>After we were provided with the PRD, we got straight to work. We divided roles amongst ourselves and I made sure to steer clear of any leadership role.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/700/1*of9hGvhEHRszd1rinhFyIw.jpeg" /></figure><p>I chose to be one of the Frontend Engineers for this project and although I have worked with a team before (max 3people), I haven’t worked with this large number. On our workspace (ClickUp), which we are still getting used to, we can see all our assigned tasks. Even though they still need to be clear to an atomic level, I’m sure our ClickUp manager would still get the hang of it.</p><h3>What I did</h3><p>Although my task was assigned late, I still made it my mission to complete it well on time.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/259/1*3xF_hGH-Qlzimgx1BekSQA.jpeg" /></figure><p>I worked on the contributions section which highlights team members and their roles and contributions (on hover). I also worked on the partners section which highlights partnering organizations that also believe in this cause. There were some layout issues which I noticed that I also fixed. My tasks went smoothly with no corrections but there were conflicts trying to merge into dev branch (<em>this is an issue we would still gather round to fix). </em>This is a function to display team members in the contributions section which takes data from an array of objects created in same javascript file. (<em>Maybe when we get further and we learn json we can fetch data directly from the Team database</em>)</p><pre>function renderTeamMembers() {<br>  const container = document.getElementById(&quot;contributions-container&quot;);<br><br>  teamMembers.forEach((member) =&gt; {<br>    const memberCard = document.createElement(&quot;div&quot;);<br>    memberCard.classList.add(&quot;team-member&quot;);<br>    memberCard.classList.add(&quot;flex&quot;);<br>    memberCard.classList.add(&quot;flex-col&quot;);<br>    memberCard.classList.add(&quot;text-center&quot;);<br>    memberCard.classList.add(&quot;items-center&quot;);<br>    memberCard.innerHTML = `<br>      &lt;img src=&quot;${member.img}&quot; alt=&quot;${member.name}&#39;s profile picture&quot; class=&quot;team-member-photo&quot;&gt;<br>      &lt;h5&gt;${member.name}&lt;/h5&gt;<br>      &lt;div class=&quot;member-info&quot;&gt;<br>        &lt;p&gt;&lt;strong&gt;Role:&lt;/strong&gt; ${member.role}&lt;/p&gt;<br>        &lt;p&gt;&lt;strong&gt;Contribution:&lt;/strong&gt; ${member.contribution}&lt;/p&gt;<br>        &lt;a href=&quot;${member.github}&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;<br>        &lt;i class=&quot;fa-brands fa-github&quot;&gt;&lt;/i&gt;&lt;/a&gt;<br>        &lt;a href=&quot;${member.linkedin}&quot; target=&quot;_blank&quot; rel=&quot;noopener noreferrer&quot;&gt;<br>          &lt;i class=&quot;fa-brands fa-linkedin&quot;&gt;&lt;/i&gt;&lt;/a&gt;<br>      &lt;/div&gt;<br>    `;<br><br>    container.appendChild(memberCard);<br>  });<br>}</pre><h3>What I can Improve On</h3><p>This new week, I’d make sure to have urgent communications on slack and be more present on ClickUp. I’d also learn how to use my daylight to work and my nights to rest. We did face some communication issues like late replies and redundant information but we’re getting there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/244/1*k-3Wdr8LeaAcWZnqwY18IA.jpeg" /></figure><p>Overall, it was a great ride and I know we still have a lot ahead of us. Kudos to everyone who contributed. See you next week !</p><p><strong><em>Contributors:</em></strong></p><ol><li>Nanji Lakan — <a href="https://medium.com/@Youtenstudio/leading-the-build-of-bloom-after-week-1-of-a-4-week-journey-1cb1e77c0ca7">Medium</a></li><li>Grace Olabode — <a href="https://dev.to/grace_olabode_3be546efe9b/building-with-care-my-week-1-setup-for-bloom-after-3590">Medium</a></li><li>Prisca Onyemaechi — <a href="https://medium.com/@priscaonyemaechi26/keeping-bloom-after-organized-my-week-1-experience-a693e3affc60">Medium</a></li><li>Genevieve Agugua — <a href="https://medium.com/@kelechigenevieveagugua/designing-bloom-after-part-1-building-the-visual-foundation-of-a-maternal-mental-health-platform-d7be67c6346d">Medium</a></li><li>Chijioke Uzodinma — <a href="https://dev.to/chijioke_uzodinma_d6ae6ef/laying-the-data-foundation-my-week-1-as-backend-lead-for-bloom-after-50n">Medium</a></li></ol><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=655b42485bfe" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Reimagining FLAMES — A Case Study in Digital Nostalgia]]></title>
            <link>https://medium.com/@adejolanu/reimagining-flames-a-case-study-in-digital-nostalgia-c469a0a80900?source=rss-3d38ab323a31------2</link>
            <guid isPermaLink="false">https://medium.com/p/c469a0a80900</guid>
            <category><![CDATA[case-study]]></category>
            <dc:creator><![CDATA[Adejolanu]]></dc:creator>
            <pubDate>Sat, 21 Feb 2026 09:16:12 GMT</pubDate>
            <atom:updated>2026-02-21T09:16:12.476Z</atom:updated>
            <content:encoded><![CDATA[<p><em>A personal case study by Adejola Esther</em></p><p>The year is 2026, but some things are timeless. Long before dating apps and sliding into DMs, there was a piece of paper, a pen, and the high-stakes ritual of <strong>FLAMES</strong>. Whether you were a “Lovers” or “Enemies” result, that schoolyard game was the original relationship calculator.</p><p>My teammate and I decided to bring that same delulu energy to the modern web. Here is how we built FLAMES, a web app designed to turn that anxiety you get from crushing on someone into an entertaining game.</p><p>FLAMES isn’t just a tool; it’s a vibe. We designed it specifically for teens and adolescents, those who might have a new crush every two weeks and need a playful way to calculate their fate.</p><p>From the start, we knew the user experience couldn’t just be about the result. We wanted to tell a story. By structuring the app as a single-page with several sections, (Home → About → Destiny States → Calculate My Fate), we ensure users are deep in the nostalgia before getting into calculating anything.</p><p>For our design structure, we made sure we steered clear of serious romance.Love can be clumsy and whimsical, and our design reflects that:</p><p>The Palette: A “Love Month” theme using Blush Red (#e94b6a) for primary actions, balanced with Cotton Candy Pink and Soft Peach for a light, quirky feel.</p><figure><img alt="Color palette for FLAMES" src="https://cdn-images-1.medium.com/max/1024/1*HvcnHEVIDzoesU52qJKAkA.png" /></figure><p>Typography: We paired <strong>Caveat</strong> for that “handwritten secret note” look with <strong>Comfortaa</strong> for clean, modern readability.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/848/1*wSrSFXJtYdGCChhUq-GKzw.png" /><figcaption>Caveat</figcaption></figure><figure><img alt="Comfortaa font type example" src="https://cdn-images-1.medium.com/max/672/1*emCUWTx1QbUUKHcxUopigQ.png" /><figcaption>Comfortaa</figcaption></figure><h3>The Technical Blueprint</h3><p>A simple concept doesn’t mean a messy codebase. We focused on making the app lean, accessible, and modular.</p><h3>1. Semantic HTML Structure</h3><p>We avoided unnecessary divs to keep the DOM tree clean and accessible. By using landmarks like , &lt;header&gt;, &lt;main&gt;, and &lt;footer&gt;, and wrapping logical blocks in &lt;section&gt; tags, we ensured the site is friendly to both SEO and screen readers. For the “Six States of Destiny,” we used &lt;article&gt; tags to define each outcome as a self-contained piece of information.</p><pre>&lt;section class=&quot;about-section flex&quot; id=&quot;about&quot;&gt;<br>        &lt;h2 class=&quot;heading text-xl flex-space-block&quot;&gt;<br>          The Story Behind the Chaos<br>        &lt;/h2&gt;<br>        &lt;article class=&quot;flex-space-flex&quot;&gt;<br>          &lt;img src=&quot;./images/heartIcon.png&quot; alt=&quot;heart&quot; /&gt;<br>          &lt;h3 class=&quot;margin text-lg heading-inverse&quot;&gt;We all have that crush&lt;/h3&gt;<br><br>          &lt;p class=&quot;margin&quot;&gt;<br>            Or three. Or a celebrity that doesn&#39;t know you exist. Or your<br>            barista who spelled your name wrong but smiled anyway.<br>          &lt;/p&gt;<br>        &lt;/article&gt;<br>        &lt;article class=&quot;flex-space-flex&quot;&gt;<br>          &lt;img src=&quot;./images/brainIcon.png&quot; alt=&quot;brain&quot; /&gt;<br>          &lt;h3 class=&quot;margin text-lg heading-inverse&quot;&gt;The Overthinking&lt;/h3&gt;<br><br>          &lt;p class=&quot;margin&quot;&gt;<br>            &quot;Did they look at me for 2.3 seconds or 2.4? Better analyze this for<br>            the next 6 hours.&quot;<br>          &lt;/p&gt;<br>        &lt;/article&gt;<br>        &lt;article class=&quot;flex-space-flex&quot;&gt;<br>          &lt;img src=&quot;./images/starIcon.png&quot; alt=&quot;star&quot; /&gt;<br>          &lt;h3 class=&quot;margin text-lg heading-inverse&quot;&gt;The Solution&lt;/h3&gt;<br><br>          &lt;p class=&quot;margin&quot;&gt;<br>            FLAMES is here to turn that overthinking into entertainment. Because<br>            why stress when you can let math decide?<br>          &lt;/p&gt;<br>        &lt;/article&gt;<br><br>        &lt;!--What is Flames--&gt;<br>        &lt;div class=&quot;flex-space&quot;&gt;<br>          &lt;article class=&quot;description-box shadow&quot;&gt;<br>            &lt;h2 class=&quot;heading-inverse text-xl&quot;&gt;What Even is FLAMES?&lt;/h2&gt;<br><br>            &lt;p class=&quot;text-align-left margin&quot;&gt;<br>              Born in schoolyards across the world, FLAMES is the original<br>              relationship calculator. Before dating apps, before &quot;sliding into<br>              DMs,&quot; there was just you, your crush&#39;s name, and a piece of paper.<br>            &lt;/p&gt;<br>            &lt;p class=&quot;text-align-left margin&quot;&gt;<br>              The rules are simple: write both names, cancel out the common<br>              letters, count what&#39;s left, and let the alphabet gods decide your<br>              fate. Are you Friends? Lovers? Married? Or (heaven forbid)<br>              Enemies?<br>            &lt;/p&gt;<br>            &lt;quote class=&quot;blush-red&quot;<br>              &gt;&quot;It&#39;s giving delulu, and we&#39;re here for it.&quot;&lt;/quote<br>            &gt;<br>            &lt;span class=&quot;blush-red&quot;&gt;— Everyone who&#39;s ever used FLAMES&lt;/span&gt;<br>          &lt;/article&gt;<br>        &lt;/div&gt;<br>      &lt;/section&gt;</pre><h3>Tokenized CSS Architecture</h3><p>We adopted a modular approach. By defining :root variables for colors, spacing, and typography scales, we created a system that is incredibly easy to maintain.</p><pre>/*base.css*/ <br>--color-blush-red: #e94b6a; /* Primary */<br>  --color-cotton-candy-pink: #f7a8b8; /* Secondary */<br>  --color-creamy-white: #fff5ec; /* Accent */<br>  --color-wine-red: #5a0f2e; /* Text */<br>  --color-soft-peach: #ffe3dc; /* Background */<br><br>--space-1: 0.25rem;<br>  --space-2: 0.5rem;<br>  --space-3: 0.75rem;<br>  --space-4: 0.875rem;<br>  --space-5: 1rem;<br>  --space-6: 1.5rem;<br>  --space-8: 2rem;<br>  --space-12: 3rem;<br>  --space-16: 4rem;<br>  --space-24: 6rem;</pre><pre>/*style.css*/<br>@import url(https://medium.com/&quot;./base.css&quot;);<br>@import url(https://medium.com/&quot;./components.css&quot;);</pre><p><strong>Flexbox Mastery</strong></p><p>Our navigation and about sections use display: flex. For the articles, we used flex: 1 1 200px, ensuring they stack naturally on mobile devices without breaking the layout.</p><pre>/*component.css*/<br>.nav-flex {<br>  margin-left: auto;<br>}<br>.about-section {<br>  flex-wrap: wrap;<br>  text-align: center;<br>  background-color: var(--bg-nav);<br>  padding: var(--space-12) var(--space-1-10);<br>  gap: var(--space-2);<br>}</pre><p><strong>Micro-interactions</strong></p><p>We used a global transition variable to make hover effects feel smooth, and added a soft, wine-red tinted shadow to give our cards depth without looking muddy.</p><pre>--shadow-soft: 0 4px 12px rgba(90, 15, 46, 0.1);<br><br>  --scale-sm: 0.98; /* active buttons */<br>  --scale-md: 1.05; /* hover buttons */<br>  --scale-lg: 1.1;<br>  --opacity-sm: 0.8; /* active buttons */<br>  --opacity-md: 0.9; /* hover buttons */<br>  --float-offset: -10px;<br>  --transition-ease-in-out: all 0.3s ease-in-out;<br>  --transition-ease-in: all 0.1s ease;</pre><p>UI Snippets:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*Sq0KUMsBEDcK8B-qTqwyuQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*EhQk8H7HtfjB2Z_Hx2LKyA.png" /><figcaption>Flames Ui snippets</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/proxy/1*k4KE00iikGTKsUBSbVjIjQ.png" /></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/896/1*17SqaFekRfrbC-4f1urJGw.png" /></figure><h3>Lessons in Collaboration</h3><p>Building the tech was only half the journey. This project was a masterclass in teamwork. Collaborating with a peer comes with unique challenges, and I walked away with three major takeaways:</p><ol><li><strong>Trust the Process:</strong> I learned to step back and trust my teammate’s expertise. I realized that giving someone space to do their part well is just as important as the code itself.</li><li><strong>The Art of the Suggestion:</strong> When opinions differed, I learned to air them as suggestions rather than demands. Sometimes, I even chose to hold back during reviews to ensure my teammate felt empowered, not hovered over.</li><li><strong>Constructive Criticism:</strong> I practiced taking feedback without feeling attacked. Turning a correction into a learning moment made the final product ten times stronger.</li></ol><p>Moving forward, our goal is to start even earlier on tasks and tighten our feedback loops on pull requests. Overall, we put our best feet forward and proved that when you combine math, nostalgia, and a little bit of delusion, you get something pretty special.</p><p><strong>Links:</strong></p><ol><li>Vercel link: <a href="https://flames-xi-livid.vercel.app/">https://flames-xi-livid.vercel.app/</a></li><li>Github link: <a href="https://github.com/De-jola/FLAMES">https://github.com/De-jola/FLAMES</a></li></ol><p><strong>Contributors:</strong></p><p><strong><em>Victor Okoukoni</em></strong></p><p>Github: <a href="https://github.com/Okoukoni-Victor">https://github.com/Okoukoni-Victor</a></p><p>Case Study: <a href="https://medium.com/@victorokoukoni/flames-designing-emotion-into-a-frontend-experience-d4ce68dfa274">https://medium.com/@victorokoukoni/flames-designing-emotion-into-a-frontend-experience-d4ce68dfa274</a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=c469a0a80900" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>