<?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: Franco kaddour</title>
    <description>The latest articles on DEV Community by Franco kaddour (@francokaddour).</description>
    <link>https://dev.to/francokaddour</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%2F3773074%2F3da02d45-dfb4-4df1-b281-f09f8fd73436.jpg</url>
      <title>DEV Community: Franco kaddour</title>
      <link>https://dev.to/francokaddour</link>
    </image>
    <atom:link rel="self" type="application/rss+xml" href="https://dev.to/feed/francokaddour"/>
    <language>en</language>
    <item>
      <title>A screenshot can't show a site that moves, so I rebuilt my portfolio around videos</title>
      <dc:creator>Franco kaddour</dc:creator>
      <pubDate>Tue, 17 Nov 2026 01:06:34 +0000</pubDate>
      <link>https://dev.to/francokaddour/a-screenshot-cant-show-a-site-that-moves-so-i-rebuilt-my-portfolio-around-videos-25n4</link>
      <guid>https://dev.to/francokaddour/a-screenshot-cant-show-a-site-that-moves-so-i-rebuilt-my-portfolio-around-videos-25n4</guid>
      <description>&lt;p&gt;For a long time my portfolio was a grid of screenshots. The problem: most of the sites I build &lt;em&gt;move&lt;/em&gt;. A loader, a scroll-driven hero, a checkout flow. A screenshot shows none of that.&lt;/p&gt;

&lt;p&gt;So I rebuilt it with one rule: &lt;strong&gt;every project is told part by part, and every part has a video of the real site working.&lt;/strong&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What's in it
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A home page with an introduction and a wheel of projects you move through by scrolling.&lt;/li&gt;
&lt;li&gt;A projects page grouped by type: e-commerce, landing pages and portfolios.&lt;/li&gt;
&lt;li&gt;A case study for each project: the problem, what was built, the decisions and the outcome, each part with its own video.&lt;/li&gt;
&lt;li&gt;An identity page with the logos and brand pieces I designed for clients.&lt;/li&gt;
&lt;li&gt;An about page with technologies, education and GitHub activity refreshed on every build.&lt;/li&gt;
&lt;li&gt;Three languages, light and dark mode, and a contact form with no backend of its own.&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/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fxr8jt1wslw3uoym0zheh.webp" 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%2Fxr8jt1wslw3uoym0zheh.webp" alt="Each project, part by part" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Three decisions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Why walk through each project part by part?
&lt;/h3&gt;

&lt;p&gt;Because a screenshot doesn't show an animation or a checkout. Each part has a video of the production site next to the text that explains that decision. And if the visitor prefers less motion (&lt;code&gt;prefers-reduced-motion&lt;/code&gt;), they get a still image instead of the video.&lt;/p&gt;

&lt;p&gt;Recording those videos was its own small project. Real-time screen capture stuttered on my machine, so I ended up recording frame by frame with Playwright and a virtual clock injected into the page, which gives perfectly smooth video no matter how slow the computer is.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Why a page just for identity?
&lt;/h3&gt;

&lt;p&gt;On several projects I also designed the brand. Putting logos, variants and graphic pieces together in one place shows that work without mixing it with the development.&lt;/p&gt;

&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%2Fgnx2xkeeg6e8vhw66otg.webp" 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%2Fgnx2xkeeg6e8vhw66otg.webp" alt="The identity page" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Why three languages and two themes on a personal site?
&lt;/h3&gt;

&lt;p&gt;Because different people read it: local clients and teams abroad. All the copy lives in translation files, with parity between languages checked by tests, and the theme switches with one tap.&lt;/p&gt;

&lt;h2&gt;
  
  
  Result
&lt;/h2&gt;

&lt;p&gt;The portfolio is live, the code is public on GitHub, and automated tests and checks run on every change. It's where I add each new project, and it's also the best sample of how I work.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Live: &lt;a href="https://francokaddour.com" rel="noopener noreferrer"&gt;francokaddour.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Code: &lt;a href="https://github.com/FrancoKaddour/portfolio-web-franco-kaddour" rel="noopener noreferrer"&gt;github.com/FrancoKaddour/portfolio-web-franco-kaddour&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Stack: React, TypeScript, Vite, Tailwind, GSAP, i18next, Vitest.&lt;/p&gt;

&lt;p&gt;Feedback is very welcome, especially on the case study format.&lt;/p&gt;

</description>
      <category>react</category>
      <category>typescript</category>
      <category>portfolio</category>
      <category>showdev</category>
    </item>
    <item>
      <title>I built a website for my taxi driver friends in Buenos Aires: a scroll-driven flight, fixed fares and WhatsApp booking</title>
      <dc:creator>Franco kaddour</dc:creator>
      <pubDate>Tue, 17 Nov 2026 01:05:49 +0000</pubDate>
      <link>https://dev.to/francokaddour/i-built-a-website-for-my-taxi-driver-friends-in-buenos-aires-a-scroll-driven-flight-fixed-fares-4apk</link>
      <guid>https://dev.to/francokaddour/i-built-a-website-for-my-taxi-driver-friends-in-buenos-aires-a-scroll-driven-flight-fixed-fares-4apk</guid>
      <description>&lt;p&gt;Some friends of mine are taxi drivers. They've been driving in Buenos Aires for years, and recently they teamed up to offer fixed-price transfers from Ezeiza and Aeroparque airports and the cruise terminal. They had good cars and years on the street, but no site of their own: work came through referrals or through apps that take a cut.&lt;/p&gt;

&lt;p&gt;On the other side there's the traveler who lands at 6 a.m. with no idea what the ride will cost or whom to trust. That's who the site is for.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A cinematic hero: a drone flight over the Obelisco, synced to the scroll, frame by frame.&lt;/li&gt;
&lt;li&gt;Fixed fares in US dollars per route, with a quote tool that writes the WhatsApp booking message.&lt;/li&gt;
&lt;li&gt;A fleet showcase: six real cars with passenger and luggage capacity.&lt;/li&gt;
&lt;li&gt;Destination and tour pages in Spanish, English and Portuguese.&lt;/li&gt;
&lt;li&gt;The brand identity: logo with its variants, a 3D plane, and a business card with QR codes.&lt;/li&gt;
&lt;li&gt;SEO for Google and AI assistants: structured data with the fares, a multi-language sitemap and &lt;code&gt;llms.txt&lt;/code&gt;.&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/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fnw3fj5ao7ctmja7qihqs.webp" 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%2Fnw3fj5ao7ctmja7qihqs.webp" alt="The hero: a flight over the Obelisco" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Three decisions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Why a scroll-driven sequence instead of a background video?
&lt;/h3&gt;

&lt;p&gt;Because the user flies it: you come down from the sky to the street at your own pace. It isn't a &lt;code&gt;&amp;lt;video&amp;gt;&lt;/code&gt;: the frames are drawn one by one on a canvas (AVIF, with WebP as a fallback), with a landscape version for desktop and a portrait one for mobile. A video tied to the scroll stutters on phones, and most passengers will open the site from their phone, right after landing. The sequence also waits for the page to load so it never slows down the first view.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Why Blender and Higgsfield on a taxi website?
&lt;/h3&gt;

&lt;p&gt;To get a shot that didn't exist. I previsualised the route in Blender and generated the flight and the brand's plane with Higgsfield. The result is an original piece made for the site, not something from a stock library.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Why WhatsApp as the only booking channel?
&lt;/h3&gt;

&lt;p&gt;Because that's where the drivers and their passengers already are. No backend, no online payments: the quote tool shows the fixed price and writes the message, and on the other side a real driver answers.&lt;/p&gt;

&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%2Fwilxtxzutzxbaewk61qu.webp" 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%2Fwilxtxzutzxbaewk61qu.webp" alt="Booking over WhatsApp" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  A note on working with AI
&lt;/h2&gt;

&lt;p&gt;The presentation film for this project was made with Claude (Fable 5.2), and honestly, I was surprised by the quality we reached. It wasn't pressing a button: it was reviewing, correcting and trying again many times. But I wouldn't have gotten this far on my own, and I want to say that with some humility.&lt;/p&gt;

&lt;h2&gt;
  
  
  Where it stands
&lt;/h2&gt;

&lt;p&gt;The site is in its final stage, before launching on the drivers' own domain. It's not a big project and there's no big budget behind it. It's a site made with care for people I know, and if you ever land in Buenos Aires and need a ride, now you know whom to ask.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Full case study with videos: &lt;a href="https://francokaddour.com/projects/buenos-drivers" rel="noopener noreferrer"&gt;francokaddour.com/projects/buenos-drivers&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Stack: Next.js, React, TypeScript, GSAP, next-intl.&lt;/p&gt;

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

</description>
      <category>nextjs</category>
      <category>gsap</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
    <item>
      <title>Building a landing page for a medical cannabis club: trust, an 18+ gate and all the content in one file</title>
      <dc:creator>Franco kaddour</dc:creator>
      <pubDate>Tue, 17 Nov 2026 01:04:57 +0000</pubDate>
      <link>https://dev.to/francokaddour/building-a-landing-page-for-a-medical-cannabis-club-trust-an-18-gate-and-all-the-content-in-one-da8</link>
      <guid>https://dev.to/francokaddour/building-a-landing-page-for-a-medical-cannabis-club-trust-an-18-gate-and-all-the-content-in-one-da8</guid>
      <description>&lt;p&gt;Together with &lt;strong&gt;Gonzalo Isaias&lt;/strong&gt;, I recently finished the landing page for &lt;strong&gt;Villurcann&lt;/strong&gt;, a medical cannabis grow club in Villa Urquiza, Buenos Aires. The club operates under Argentina's Law 27.350 and the REPROCANN programme.&lt;/p&gt;

&lt;p&gt;It's not an e-commerce or an app. It's a landing page. But the field adds conditions you don't see on a typical landing, and I wanted to share the three decisions that mattered most.&lt;/p&gt;

&lt;h2&gt;
  
  
  The problem: in this field, trust is everything
&lt;/h2&gt;

&lt;p&gt;A medical grow club has to explain clearly and seriously what it is, how it works and what it takes to join. If the site looks improvised or the legal information is messy, people leave.&lt;/p&gt;

&lt;p&gt;So the page is organised in this order: the legal framework, the requirements, and the path to membership. Every enquiry ends in WhatsApp, which is where the club already answers.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we built
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A one-page landing: About, Membership, REPROCANN, Requirements, FAQ, Transparency and Contact.&lt;/li&gt;
&lt;li&gt;An animated brand intro, with the mark (a V with a lotus) drawn in SVG.&lt;/li&gt;
&lt;li&gt;An age gate before entering, and a video hero.&lt;/li&gt;
&lt;li&gt;WhatsApp contact with a pre-filled message that depends on the section it's sent from.&lt;/li&gt;
&lt;li&gt;Production on Cloudflare with security headers and its own domain.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Decision 1: an 18+ notice before anything else
&lt;/h2&gt;

&lt;p&gt;The content is for adults and the club works within a specific legal framework. The age notice isn't there just to tick a box: it sets the first impression and makes clear from the start that this is a serious, regulated space.&lt;/p&gt;

&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%2Fjfd9jey7y3cyoyum6na3.webp" 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%2Fjfd9jey7y3cyoyum6na3.webp" alt="The age gate" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 2: all the content in a single file
&lt;/h2&gt;

&lt;p&gt;Copy, links and images live in one content file, separate from the components. Whoever manages the relationship with the club can update the information without any risk of breaking the design or the animations.&lt;/p&gt;

&lt;p&gt;For a non-technical client, this is worth more than any CMS: no panel to learn, no database to maintain, and the site stays static and fast.&lt;/p&gt;

&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%2F04uzo6dmczq130sw92c0.webp" 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%2F04uzo6dmczq130sw92c0.webp" alt="Content kept separate from the design" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Decision 3: launch in stages
&lt;/h2&gt;

&lt;p&gt;At the club's request, the first stage is just the landing page, meant to bring in interested people. In parallel, we're building the club's internal management system, which is the second part of the project.&lt;/p&gt;

&lt;p&gt;Launching the landing first lets them start receiving enquiries now, without waiting for the whole system.&lt;/p&gt;

&lt;h2&gt;
  
  
  Result
&lt;/h2&gt;

&lt;p&gt;Villurcann is live at &lt;a href="https://villurcann.com" rel="noopener noreferrer"&gt;villurcann.com&lt;/a&gt;, with a site that explains the legal framework, the requirements and the path to membership, and sends every enquiry straight to WhatsApp.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Full case study with videos: &lt;a href="https://francokaddour.com/projects/villurcann" rel="noopener noreferrer"&gt;francokaddour.com/projects/villurcann&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Stack: React, TypeScript, Vite, Tailwind, GSAP, Cloudflare.&lt;/p&gt;

&lt;p&gt;Thanks for reading. If you've worked on sites for regulated businesses, I'd like to hear what you learned.&lt;/p&gt;

</description>
      <category>react</category>
      <category>webdev</category>
      <category>gsap</category>
      <category>showdev</category>
    </item>
    <item>
      <title>My first project in production: a home decor store where the cart checks out on WhatsApp</title>
      <dc:creator>Franco kaddour</dc:creator>
      <pubDate>Tue, 17 Nov 2026 01:03:51 +0000</pubDate>
      <link>https://dev.to/francokaddour/my-first-project-in-production-a-home-decor-store-where-the-cart-checks-out-on-whatsapp-11io</link>
      <guid>https://dev.to/francokaddour/my-first-project-in-production-a-home-decor-store-where-the-cart-checks-out-on-whatsapp-11io</guid>
      <description>&lt;p&gt;&lt;strong&gt;Espacio Vina&lt;/strong&gt; was my first project in production, back in 2025, and it's still online today.&lt;/p&gt;

&lt;p&gt;It's a home &amp;amp; decor business that sold only through Facebook and Instagram, with no physical store. Every sale was closed by hand over chat: answering questions, sending photos, confirming prices. Juggling several networks at once ate up the owner's day and cost her sales.&lt;/p&gt;

&lt;h2&gt;
  
  
  What we built
&lt;/h2&gt;

&lt;p&gt;I built it in a pair with &lt;strong&gt;Nico Alvez&lt;/strong&gt;: I handled the frontend and the design decisions, and Nico the backend.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;A browsable product catalog with the brand's palette and typography.&lt;/li&gt;
&lt;li&gt;A cart that assembles the order and sends it, ready-made, over WhatsApp.&lt;/li&gt;
&lt;li&gt;An admin panel to upload products and manage orders.&lt;/li&gt;
&lt;li&gt;A PHP + MySQL backend built from scratch.&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/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2F7dmagw37ffayanns1qzu.webp" 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%2F7dmagw37ffayanns1qzu.webp" alt="The catalog" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Two decisions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Why cart → WhatsApp instead of a payment gateway?
&lt;/h3&gt;

&lt;p&gt;The owner already closed every sale over WhatsApp, and her buyers trust that channel. A gateway would have added fees and friction. So the cart builds the message with products and quantities and drops it into the chat. Less back and forth, and the same way of selling she already had.&lt;/p&gt;

&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%2Fzvx72867zmw1wm67ioti.webp" 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%2Fzvx72867zmw1wm67ioti.webp" alt="The WhatsApp cart" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Why a custom PHP + MySQL backend?
&lt;/h3&gt;

&lt;p&gt;The business needed a catalog it could manage without paying monthly fees to a third-party platform. Building it from scratch was more work, but it fit the budget and the operation.&lt;/p&gt;

&lt;h2&gt;
  
  
  What I learned
&lt;/h2&gt;

&lt;p&gt;Looking back, this project taught me to start from how the client &lt;strong&gt;already works&lt;/strong&gt; instead of how an online store "should" work. That idea has shown up in almost every project since.&lt;/p&gt;

&lt;p&gt;Today the site works as the business's central catalog: one place to point to from every social network, with sales still closing on WhatsApp.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Live: &lt;a href="https://espaciovina.com" rel="noopener noreferrer"&gt;espaciovina.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Full case study: &lt;a href="https://francokaddour.com/projects/espacio-vina" rel="noopener noreferrer"&gt;francokaddour.com/projects/espacio-vina&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Stack: HTML, CSS, JavaScript, PHP, MySQL.&lt;/p&gt;

&lt;p&gt;Do you remember your first project in production? I'd love to read about it in the comments.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>php</category>
      <category>ecommerce</category>
      <category>beginners</category>
    </item>
    <item>
      <title>Brand first, website second: building Miga Club for a pizza maker with no storefront</title>
      <dc:creator>Franco kaddour</dc:creator>
      <pubDate>Tue, 17 Nov 2026 01:03:06 +0000</pubDate>
      <link>https://dev.to/francokaddour/brand-first-website-second-building-miga-club-for-a-pizza-maker-with-no-storefront-5e14</link>
      <guid>https://dev.to/francokaddour/brand-first-website-second-building-miga-club-for-a-pizza-maker-with-no-storefront-5e14</guid>
      <description>&lt;p&gt;&lt;strong&gt;Miga Club&lt;/strong&gt; is run by a master pizza maker in Buenos Aires who started selling frozen pizzas, &lt;em&gt;sándwiches de miga&lt;/em&gt; (our classic thin sandwiches) and event bundles on his own. No storefront, no brand, no online presence: he only sold to people he knew, and there was nowhere to see the products, the prices or how to order.&lt;/p&gt;

&lt;p&gt;So this wasn't "make me a website". It was "make me a business people can find".&lt;/p&gt;

&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A full brand identity: logo, color palette and typography.&lt;/li&gt;
&lt;li&gt;Illustrations and graphics for the site and social media.&lt;/li&gt;
&lt;li&gt;A website with a product and promo catalog.&lt;/li&gt;
&lt;li&gt;A small admin dashboard for prices, promos and new products.&lt;/li&gt;
&lt;li&gt;A Google Business profile as the pickup point, with delivery across the city.&lt;/li&gt;
&lt;li&gt;Facebook and Instagram setup, plus menus and social pieces.&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/https%3A%2F%2Fdev-to-uploads.s3.us-east-2.amazonaws.com%2Fuploads%2Farticles%2Fvimjwsl35p1kz2fxfps4.webp" 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%2Fvimjwsl35p1kz2fxfps4.webp" alt="The Miga Club brand" width="800" height="500"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Three decisions
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Why the brand before the site?
&lt;/h3&gt;

&lt;p&gt;Without an identity, the website would have been just another price list. I defined the logo, palette and type first, and only then built the site on top of that. The same identity repeats on the web, on social media and on the printed menus, and that consistency is what makes a business without a storefront feel like a real brand.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Why plain HTML, CSS and JavaScript?
&lt;/h3&gt;

&lt;p&gt;A catalog with a simple dashboard didn't need a framework. Zero dependencies means zero dependency maintenance: the site loads fast, never breaks because of a third-party update, and every tweak goes straight into the code. Firebase covers the data side.&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Why a minimal dashboard?
&lt;/h3&gt;

&lt;p&gt;The client needs to change prices, set up promos and add products. Nothing else. A panel built for exactly that is easier for a non-technical person than a generic CMS with a hundred options he'll never touch.&lt;/p&gt;

&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%2Fnchhm9l4v2ga3p58iump.webp" 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%2Fnchhm9l4v2ga3p58iump.webp" alt="The admin dashboard" width="800" height="640"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  Result
&lt;/h2&gt;

&lt;p&gt;Miga Club went from selling only to acquaintances to a complete presence: brand, site, social media and a Google listing, taking orders with delivery across the city.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"I know pizza, not websites. Franco built everything from scratch — brand, logo and site — and suddenly I had something to show. Now people find me, see the products and order on their own." — Julio, owner&lt;/p&gt;
&lt;/blockquote&gt;

&lt;ul&gt;
&lt;li&gt;Live: &lt;a href="https://migaclub.com.ar" rel="noopener noreferrer"&gt;migaclub.com.ar&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Full case study: &lt;a href="https://francokaddour.com/projects/miga-club" rel="noopener noreferrer"&gt;francokaddour.com/projects/miga-club&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Stack: HTML, CSS, JavaScript, Firebase.&lt;/p&gt;

&lt;p&gt;If you've ever had to choose between "a framework" and "just HTML" for a small client, I'd love to hear how you decided.&lt;/p&gt;

</description>
      <category>webdev</category>
      <category>javascript</category>
      <category>design</category>
      <category>showdev</category>
    </item>
    <item>
      <title>How I built an e-commerce a neighborhood bakery runs by itself (Next.js, loyalty points and a lot of motion)</title>
      <dc:creator>Franco kaddour</dc:creator>
      <pubDate>Tue, 17 Nov 2026 01:02:09 +0000</pubDate>
      <link>https://dev.to/francokaddour/how-i-built-an-e-commerce-a-neighborhood-bakery-runs-by-itself-nextjs-loyalty-points-and-a-lot-4flo</link>
      <guid>https://dev.to/francokaddour/how-i-built-an-e-commerce-a-neighborhood-bakery-runs-by-itself-nextjs-loyalty-points-and-a-lot-4flo</guid>
      <description>&lt;p&gt;&lt;strong&gt;La Básica&lt;/strong&gt; is a small bakery in Saavedra, a neighborhood in Buenos Aires. It had a storefront, loyal customers and a full display case, but no digital channel at all: orders came in over WhatsApp or at the counter, there was no online catalog, no visible prices, and loyalty lived in a paper notebook.&lt;/p&gt;

&lt;p&gt;The owner wanted to sell online &lt;strong&gt;without depending on anyone to run it&lt;/strong&gt;. That sentence shaped every decision in the project.&lt;/p&gt;

&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%2F1evjnj7chmzn4xxlp0z7.webp" 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%2F1evjnj7chmzn4xxlp0z7.webp" alt="La Básica in production" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h2&gt;
  
  
  What I built
&lt;/h2&gt;

&lt;ul&gt;
&lt;li&gt;A full online store: storefront, catalog, cart and checkout with in-store pickup.&lt;/li&gt;
&lt;li&gt;A loyalty points system: every purchase adds up, and points are redeemable for products and discounts.&lt;/li&gt;
&lt;li&gt;An admin panel for products, orders, categories and email marketing.&lt;/li&gt;
&lt;li&gt;Motion design as part of the identity: a brand loader, marquees and micro-interactions in every section.&lt;/li&gt;
&lt;li&gt;16 local-SEO pages (per product and per area).&lt;/li&gt;
&lt;li&gt;Production-grade basics: CSP with nonces, rate limiting, transactional emails and CI/CD.&lt;/li&gt;
&lt;/ul&gt;

&lt;h2&gt;
  
  
  Four decisions worth explaining
&lt;/h2&gt;

&lt;h3&gt;
  
  
  1. Why so much motion on a bakery?
&lt;/h3&gt;

&lt;p&gt;Because personality is the one thing a neighborhood shop has that big apps can't copy. Every animation runs on the browser's compositor (only &lt;code&gt;transform&lt;/code&gt; and opacity), and I checked them on WebKit so the experience holds up on a mid-range iPhone, not just on my desktop.&lt;/p&gt;

&lt;h3&gt;
  
  
  2. Why in-store pickup and bank transfer, with no payment gateway?
&lt;/h3&gt;

&lt;p&gt;This was a business decision, not a technical one. Gateway fees eat the margin of a croissant. The checkout confirms the order and only then shows the payment details. Less friction, zero commission, and the owner validates each transfer from the panel.&lt;/p&gt;

&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%2Fkn56sovfxatwknxcosdo.webp" 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%2Fkn56sovfxatwknxcosdo.webp" alt="Checkout with in-store pickup" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  3. Why a custom points system?
&lt;/h3&gt;

&lt;p&gt;People come back to a bakery every week. A tailor-made system (points per purchase, rewards the business defines) turns that habit into an incentive. A generic coupon can't do that.&lt;/p&gt;

&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%2F71vn0su9h7e775c91cxz.webp" 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%2F71vn0su9h7e775c91cxz.webp" alt="Loyalty points" width="800" height="533"&gt;&lt;/a&gt;&lt;/p&gt;

&lt;h3&gt;
  
  
  4. Why serious security and SEO for a small business?
&lt;/h3&gt;

&lt;p&gt;Because the site handles customer data and money. Strict CSP, rate limiting and validation on every endpoint are what let the owner trust her operation to it. And the local pages with structured data are what make "bakery in Saavedra" mean La Básica.&lt;/p&gt;

&lt;h2&gt;
  
  
  Result
&lt;/h2&gt;

&lt;p&gt;La Básica went from the counter and WhatsApp to an online store run by the owner herself: a live catalog, orders with coordinated pickup, customers earning points.&lt;/p&gt;

&lt;blockquote&gt;
&lt;p&gt;"At last I have the digital presence I was missing — it's really polished, and I'm very happy with the design and performance of the site." — Flor, owner&lt;/p&gt;
&lt;/blockquote&gt;

&lt;p&gt;It's a small project, but it taught me that the most important feature is often the one the client can operate on her own.&lt;/p&gt;

&lt;ul&gt;
&lt;li&gt;Live: &lt;a href="https://labasicapasteleria.com" rel="noopener noreferrer"&gt;labasicapasteleria.com&lt;/a&gt;
&lt;/li&gt;
&lt;li&gt;Full case study with videos: &lt;a href="https://francokaddour.com/projects/la-basica" rel="noopener noreferrer"&gt;francokaddour.com/projects/la-basica&lt;/a&gt;
&lt;/li&gt;
&lt;/ul&gt;

&lt;p&gt;Stack: Next.js, React, TypeScript.&lt;/p&gt;

&lt;p&gt;Thanks for reading! Happy to answer questions about any of these decisions in the comments.&lt;/p&gt;

</description>
      <category>nextjs</category>
      <category>ecommerce</category>
      <category>webdev</category>
      <category>showdev</category>
    </item>
  </channel>
</rss>
