<?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 Soraya Cantos on Medium]]></title>
        <description><![CDATA[Stories by Soraya Cantos on Medium]]></description>
        <link>https://medium.com/@sorayacantos?source=rss-56deaaa77031------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*tf-M0E_CPy8WEb5nZECTFQ.jpeg</url>
            <title>Stories by Soraya Cantos on Medium</title>
            <link>https://medium.com/@sorayacantos?source=rss-56deaaa77031------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Sun, 22 Nov 2026 16:50:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@sorayacantos/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[From an Idea to the First Version of my App with AI Code]]></title>
            <link>https://medium.com/@sorayacantos/from-an-idea-to-the-first-version-of-my-app-with-ai-code-3a74c6f37535?source=rss-56deaaa77031------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a74c6f37535</guid>
            <category><![CDATA[vibe-coding]]></category>
            <category><![CDATA[saas]]></category>
            <category><![CDATA[windsurf]]></category>
            <category><![CDATA[app-development]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Soraya Cantos]]></dc:creator>
            <pubDate>Fri, 16 May 2025 12:44:19 GMT</pubDate>
            <atom:updated>2025-05-16T12:44:19.044Z</atom:updated>
            <content:encoded><![CDATA[<h4>How I used Windsurf to launch the first version of Mocktopus in one sitting</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*XPZvCQFK9Fpu82fDPue9EQ.png" /></figure><h3><strong>Why I used Windsurf</strong></h3><p>It’s been a few months now that “vibe coding” has been popping up everywhere. As a web developer, I asked myself: is this really for me?</p><p>After a failed production launch of a SaaS I had spent months building, I didn’t want to go down that road again.</p><blockquote>I wanted to test a new idea — Mocktopus — without spending weeks or months developing it.</blockquote><p>I just wanted to create something simple. Something to test. No big SaaS, no big product.</p><p>That’s when I decided to <strong>try Windsurf</strong>, an AI-powered IDE I had only heard about a few days earlier. I wanted to keep it simple and go fast and Windsurf could help me achieve this.</p><h3><strong>The Idea Behind Mocktopus</strong></h3><p><strong><em>Mocktopus is a feedback platform that helps founders, makers, and developers validate their SaaS , app or product ideas before building or launching.</em></strong></p><p>It enables users to collect valuable insights from real and anonymous users early in the process — whether you’re exploring an idea, shaping a concept, or preparing to go to market.</p><p>Whether the goal is to gather honest feedback or test if there’s genuine interest in an idea, Mocktopus streamlines the journey from rough concept to a product people actually want.</p><h3><strong>The Windsurf Experience</strong></h3><p>What surprised me the most was the design.</p><blockquote>I didn’t ask for anything specific, but it came out minimalistic, clean, and honestly beautiful.</blockquote><p>It looked like something I could ship right away. I hadn’t to touch much of the design.</p><p>I used Next.js and Tailwind CSS for the frontend, which was perfect. But it didn’t follow the latest recommendations around server and client components — it felt more like a classic React project. I left some parts like that, but in the places where it really mattered, I could just point out what was wrong and ask it to fix it. That flexibility was impressive.</p><p>Later, I tried to add a database I’m not very familiar with. That became the most challenging part. It didn’t work exactly as expected at first, and I ran into a few errors and warnings. The hardest part was that I couldn’t clearly find what was wrong. I asked Windsurf to fix it, but eventually, I had to dive into the official documentation and browse forums to make sure everything was working properly and safely.</p><h3><strong>Rethinking What It Means to Start</strong></h3><p>Since Mocktopus isn’t ready yet, I added a simple waitlist CTA. I asked Windsurf to create a modal, and just like that, I had something that looked and felt smooth and native.</p><blockquote>Before this, I used to think that building meant hours of brute-force coding.</blockquote><p>But with the right AI tools, it feels more like shaping clay. You’re not hammering things into place — you’re sculpting and adjusting as you go.</p><p>Windsurf didn’t just help me build faster — it made me rethink what it means to start a project. It’s like we’re entering a time where ideas can come to life faster. And maybe fail faster too. That’s actually a good thing.</p><p><strong>Mocktopus is still in the works. But if you’re curious, you can check out the site </strong><a href="https://mocktopus.app/"><strong>here</strong></a><strong> or join the waitlist. And if you’ve been experimenting with AI tools to build something, I’d really love to hear your story too.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a74c6f37535" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[How I Keep My Motivation Flowing]]></title>
            <link>https://medium.com/@sorayacantos/how-i-keep-my-motivation-flowing-803f8e25690b?source=rss-56deaaa77031------2</link>
            <guid isPermaLink="false">https://medium.com/p/803f8e25690b</guid>
            <category><![CDATA[tricks-that-help]]></category>
            <category><![CDATA[productivity]]></category>
            <category><![CDATA[business]]></category>
            <category><![CDATA[motivation]]></category>
            <category><![CDATA[self-improvement]]></category>
            <dc:creator><![CDATA[Soraya Cantos]]></dc:creator>
            <pubDate>Thu, 03 Apr 2025 06:46:23 GMT</pubDate>
            <atom:updated>2025-04-03T06:46:23.987Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>My new productivity hack</strong></p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*HTcw8Ia5OoCOugrVLVEKgA.jpeg" /><figcaption>Photo by Christin Hume on Unsplash</figcaption></figure><p><strong>I have struggled all my life to find intrinsic motivation.</strong></p><p>I’ve always been too lazy and unmotivated to start a side hustle or quit my 9-to-5 job. I had nice colleagues, good working conditions — what more could I want?</p><blockquote>But deep down, I always knew that I wanted to work for myself and that I needed to find that intrinsic motivation.</blockquote><p>At the end of 2024, I finally decided to quit and embark on my solo journey! I made a few promises to myself:</p><ul><li>I will do everything I can to keep my <strong>motivation flowing</strong>.</li><li>I will do whatever it takes to maintain a <strong>high level of productivity.</strong></li><li>I <strong>don’t want to</strong> <strong>regret</strong> this precious time I’m giving myself.</li><li>I will allow myself to <strong>experiment and fail</strong>.</li><li>I will try to<strong> enjoy the process</strong> as much as possible, no matter how long it takes.</li></ul><p>After struggling to maintain my motivation, here’s what has been working for me so far — and what hasn’t:</p><h3><strong>What Didn’t Work</strong></h3><h4><strong>I Don’t Believe in the ‘Discipline Over Motivation’ Mindset</strong></h4><p>Some entrepreneurs, influencers, and even people around me have told me that motivation is temporary and that what truly keeps you going is discipline and hard work. They say:</p><ul><li>Once the euphoria of the first few days is going, staying motivated is impossible.</li><li>The key to success is to keep working, even if you don’t enjoy it.</li><li>Make work a habit.</li><li>Motivation will eventually return.</li></ul><p>I understand that this method works for many people and can be extremely rewarding when you succeed and look back at all the sacrifices and hard work.</p><blockquote>But where’s the joy in doing things this way? What if I can find a method that keeps me consistently motivated so that work doesn’t feel like a chore?</blockquote><p><strong>I want to fully enjoy the process of building my business and developing my personal brand.</strong></p><h3><strong>What Has Been Working for Me</strong></h3><p>I’ve read and followed several entrepreneurs and love hearing their perspectives on this topic.</p><p>After some reflection, here’s what has worked really well for me:</p><ul><li><strong>A Sense of Urgency:</strong> Because I’m not doing this as a side hustle but rather as a full-time commitment, I feel an intense need to succeed. The lack of a backup plan keeps me going.</li><li><strong>A Well-Defined Plan:</strong> I started with a rough idea of what I needed to do to grow my personal brand, but once I precisely defined my roadmap, everything fell into place.</li><li><strong>Daily Reflection and Learning:</strong> At the end of each day, I write, communicate on social media, read, watch inspirational videos, and take time to reflect on what I’ve learned.</li></ul><p>This last point has had the biggest impact on my motivation. Of course, I don’t do all of these things every single day. Instead, I choose what feels most necessary at any given moment.</p><blockquote>Constantly improving myself and my work — and reflecting on it — gives me a small dopamine boosts every day. This feeling helps me stay focused on my goals and fuels my motivation.</blockquote><p>This last point was inspired by Dan Koe video here after: <a href="https://www.youtube.com/watch?v=ZdO00Y-u1y0&amp;t=1s&amp;ab_channel=DanKoe">https://www.youtube.com/watch?v=ZdO00Y-u1y0&amp;t=1s&amp;ab_channel=DanKoe</a></p><h3><strong>Am I Delusional?</strong></h3><h4>I’m simply choosing to enjoy my journey as a freelancer and solopreneur.</h4><p>I believe the key is to trick your mind into finding what works best for you:</p><ul><li>If meditation doesn’t work for you, don’t do it.</li><li>If waking up at 5 AM doesn’t suit you, don’t force it.</li><li>Prioritize your sleep, your health, and your personal needs.</li></ul><blockquote><strong>Free yourself from rigid routines and guides.</strong> Work in a way that aligns with how you feel. When you do this, work becomes more productive, and you feel significantly happier.</blockquote><p>You have to experiment and analyze what works best for you.</p><p><strong>What are your thoughts on this?</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=803f8e25690b" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Handling Forms in Next.js with next/form, Server Actions, useActionState, and Zod Validation]]></title>
            <link>https://medium.com/@sorayacantos/handling-forms-in-next-js-with-next-form-server-actions-useactionstate-and-zod-validation-15f9932b0a9e?source=rss-56deaaa77031------2</link>
            <guid isPermaLink="false">https://medium.com/p/15f9932b0a9e</guid>
            <category><![CDATA[useactionstate]]></category>
            <category><![CDATA[server-action]]></category>
            <category><![CDATA[zod]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[nextjs]]></category>
            <dc:creator><![CDATA[Soraya Cantos]]></dc:creator>
            <pubDate>Wed, 02 Apr 2025 17:03:22 GMT</pubDate>
            <atom:updated>2025-04-02T17:03:22.333Z</atom:updated>
            <content:encoded><![CDATA[<h4>Examples of form setups</h4><h4>There are two ways to use next/form, depending on the action prop.</h4><p>The action prop can be either a string or a function. If it is a <strong>string</strong>, the form uses the GET method and navigates to a new URL.</p><p>If it is a <strong>function</strong>, the form uses the POST method and calls the associated server action.</p><p>I will detail here how to use the form with a Server Action.</p><h3>Example 1: Simple form with Server Action</h3><p>Here is my app/page.js file:</p><pre>import Form from &#39;next/form&#39;<br><br>export default function Home() {<br><br>  const formAction = async (formData) =&gt; {<br>    &#39;use server&#39;<br>    console.log(&#39;formData&#39;, formData)<br><br>    // if needed, you can access the inputValue like this:<br>    const inputValue = formData.get(&quot;inputValue&quot;)<br>    console.log(&#39;inputValue&#39;, inputValue)<br><br>    // Save in database, send emails or any backend task without exposing such logic on the client side.<br>  }<br><br>  return (<br>    &lt;Form action={formAction}&gt;<br>      &lt;input name=&quot;inputValue&quot; /&gt;<br>      &lt;button type=&quot;submit&quot;&gt;Submit&lt;/button&gt;<br>    &lt;/Form&gt;<br>  );<br>}</pre><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*LQwAb9kxlkh5QpnCbxc3gQ.png" /></figure><p>As its name suggests, server actions run on the server, so console.logs will only appear in the terminal, not in the browser console.</p><p><strong>By handling logic on the server, you keep sensitive operations away from the client.</strong></p><p>This way you won’t need a separate API, API route or route handler to set up.</p><h3>Example 2: Form with Server Action + Zod validation</h3><p>Now we want to:</p><ul><li>send request from form to our formAction</li><li>validate using zod</li><li>send back the error to the client</li></ul><p>To do this, you will need to convert your page.js or component into a client component by adding &#39;use client&#39; at the top.</p><p>Export your formAction function to another file, placing &#39;use server&#39; at the top to maintain its server action behavior.</p><p>Then, to easily catch validation errors, you can wrap the server action in a client-side function (handleSubmit).</p><p>Here is my app/page.js file:</p><pre>&#39;use client&#39;<br>import { useState } from &#39;react&#39;;<br>import Form from &#39;next/form&#39;;<br>import formAction from &#39;./actions/form-action&#39;;<br>export default function Home() {<br>  const [error, setError] = useState(null);<br><br>  // Wrap the server action call in a client-side function.<br>  const handleSubmit = async (formData) =&gt; {<br>    try {<br>      const result = await formAction(formData);<br>      // If no error, you can proceed with further UI changes (e.g., clear form, show success message)<br>    } catch (err) {<br>      setError(err.message);<br>      // or use a toast for example<br>    }<br>  };<br><br>  return (<br>    &lt;&gt;<br>      &lt;Form action={handleSubmit}&gt;<br>        &lt;input name=&quot;inputValue&quot; /&gt;<br>        &lt;button type=&quot;submit&quot;&gt;Submit&lt;/button&gt;<br>      &lt;/Form&gt;<br>      {error &amp;&amp; &lt;p style={{ color: &#39;red&#39; }}&gt;{error}&lt;/p&gt;}<br>    &lt;/&gt;<br>  );<br>}</pre><p>Here is my app/actions/form-action.js file:</p><pre>&#39;use server&#39;<br>import { z } from &#39;zod&#39;;<br><br>const schema = z.object({<br>    inputValue: z.string().min(1, &quot;Input is required&quot;),<br>  });<br><br>const formAction = async (formData) =&gt; {<br><br>    // use this method to get all entries at once:<br>    const dataToValidate = Object.fromEntries(formData.entries());<br>    const validation = schema.safeParse(dataToValidate);<br><br>    if (!validation.success) {<br>      throw new Error(validation.error.flatten().fieldErrors);<br>    }<br>    // Perform your server-side tasks<br>  };<br><br>  export default formAction</pre><p>Alternatively you can also use form libraries like <strong>React Hook Form</strong> along with server actions. These libraries make it easier to handle validation on the client side while still keeping important checks on the server.</p><h3>Example 3: Form with Server Action + useActionState + Zod validation</h3><p>This is the way presented in Next.js documentation. <a href="https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations"><em>https://nextjs.org/docs/app/building-your-application/data-fetching/server-actions-and-mutations</em></a></p><p>We will now introduce the useActionState() React hook to better handle the form. It is a very simple and clean way to create a form with Next.js and React.</p><p>Here is my app/page.js file.</p><pre>&#39;use client&#39;<br>import Form from &#39;next/form&#39;<br>import ourFormAction from &#39;./actions/form-action&#39;;<br>import { useActionState } from &#39;react&#39;;<br><br>const initialState = {<br>  message: null,<br>}<br><br>export default function Home() {<br>  const [state, formAction, pending] = useActionState(ourFormAction, initialState);<br><br>  return (<br>    &lt;Form action={formAction}&gt;<br>      &lt;input name=&quot;inputValue&quot; /&gt;<br>      &lt;p style={{ color: &#39;red&#39; }}&gt;{state?.message?.inputValue?.[0]}&lt;/p&gt;<br>      &lt;button type=&quot;submit&quot; disabled={pending}&gt;Submit&lt;/button&gt;<br>    &lt;/Form&gt;<br>  );<br>}</pre><p>With this hook, we have a state to handle error messages, success messages, or anything else we need from the form.</p><p>This hook uses formAction to call our server action function which I named ourFormAction.</p><p>We can also easily handle ‘pending’ state.</p><p>Here is my app/actions/form-action.js file:</p><pre>&#39;use server&#39;<br>import { z } from &#39;zod&#39;;<br><br>const schema = z.object({<br>    inputValue: z.string().min(1, &quot;Input is required&quot;),<br>  });<br><br>const formAction = async (prevState, formData) =&gt; {<br><br>    const dataToValidate = Object.fromEntries(formData.entries());<br>    const validation = schema.safeParse(dataToValidate);<br><br>    if (!validation.success) {<br>      return {message: validation.error.flatten().fieldErrors}<br>    }<br><br>    // Perform your server-side tasks here.<br>    // redirect if needed<br>  };<br><br>  export default formAction</pre><p>ourFormAction takes two arguments: previousState and formData.</p><p>After validation, we need to return our state, in this case with an updated message.</p><p>Now the code is concise and leverages Next.js’s and React’s built-in features.</p><p><strong>Let me know what you think and if you think something is missing !!</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=15f9932b0a9e" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Why you shouldn’t trust AI as a Web Developer!]]></title>
            <link>https://medium.com/@sorayacantos/why-you-shouldnt-trust-ai-as-a-web-developer-61a96b1fe936?source=rss-56deaaa77031------2</link>
            <guid isPermaLink="false">https://medium.com/p/61a96b1fe936</guid>
            <category><![CDATA[risks-and-benefits]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[chatgpt]]></category>
            <category><![CDATA[ai]]></category>
            <dc:creator><![CDATA[Soraya Cantos]]></dc:creator>
            <pubDate>Tue, 11 Mar 2025 14:21:58 GMT</pubDate>
            <atom:updated>2025-03-11T14:23:36.884Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*g-Ebvoa0j0tLMhvWw2ja9A.jpeg" /></figure><h3><strong>1. The Risks of AI-Generated Code</strong></h3><p><strong>The Illusion of Expertise</strong></p><p>The new generation of web developers doesn’t know how to code anymore, yet they are releasing highly technical code. It’s somewhat true. We tend to rely more and more on AI tools and automation rather than their own technical skills and critical thinking. At first glance, AI-generated code appears well-structured and functional, giving the illusion of progress. It feels like you’re learning, improving, and mastering both AI prompts and coding.</p><p>However, this approach to coding is extremely dangerous because it creates a paradox: you may be building highly technical applications without truly understanding the core principles behind them. As a web developer myself, I sometimes face this duality, especially when I want to implement complex tools or code quickly in technologies I don’t fully master.</p><p><strong>Losing control over your own code</strong></p><p>When working with a large amount of AI-generated code, you’ve probably had to iterate on it multiple times. This can cause the feeling that you don’t understand and you don’t own the code anymore.</p><p>This loss of ownership can be problematic when working in a team or maintaining a project long term. AI-generated code can sometimes be more complex than necessary, making it harder to manage, debug, and maintain over time.</p><p><strong>Security and Maintenance Risks</strong></p><p>Because AI tends to provide solutions based on the most common patterns it has seen, the code is not always the most efficient, innovative, or appropriate for a given context. Future developers (or even yourself) might struggle to modify or extend the code without rewriting it from scratch.</p><p>On top of that, AI-generated code isn’t always secure. Without proper review and testing, it might introduce vulnerabilities that hackers can exploit. You must be proactive in checking AI-generated code for potential security flaws.</p><h3><strong>2. How You Should Use AI Instead</strong></h3><p><strong>Think Before You Code: Question AI’s Suggestions</strong></p><p>Don’t just check if AI-generated code works — take a step back and ask yourself why it’s suggesting that solution in the first place. Is it really the best way to solve the problem? Could there be a simpler, more secure, or more efficient approach? Instead of blindly accepting what AI gives you, stay involved in the process. That way, you keep control over your own code and truly understand what you’re building.</p><p><strong>Important Steps You Must Follow</strong></p><p>Here are some ways to use AI effectively:</p><ul><li>Ask AI for the best approach to solving a problem rather than just requesting code.</li><li><strong>Don’t copy the code immediately</strong> — once you understand the idea, read the documentation or try writing it yourself.</li><li><strong>Break down AI-generated code into small parts and test it</strong> to ensure it works as expected.</li><li><strong>Ask AI to explain its solution</strong> and challenge its reasoning.</li><li><strong>LEARN throughout the process</strong> — don’t skip steps or rush. You should understand every line of code AI provides.</li><li><strong>Cross-check and validate AI-generated code</strong> with official documentation and trusted sources.</li></ul><h3><strong>3. Will AI Replace Web Developers ?</strong></h3><p>From my point of view, given the current state of AI, it should be used as an assistant, not a replacement for web development. We must generate and understand our own code while using AI to help with smaller parts. AI should be a companion, and some tools are following this path — like GitHub Copilot and other AI-powered coding assistants.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=61a96b1fe936" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Efficient Font Loading with Next.js and TailwindCSS (using variables)]]></title>
            <link>https://medium.com/@sorayacantos/efficient-font-loading-with-next-js-and-tailwindcss-3a8163f2d511?source=rss-56deaaa77031------2</link>
            <guid isPermaLink="false">https://medium.com/p/3a8163f2d511</guid>
            <category><![CDATA[code]]></category>
            <category><![CDATA[fonts]]></category>
            <category><![CDATA[ux]]></category>
            <category><![CDATA[seo]]></category>
            <category><![CDATA[nextjs]]></category>
            <dc:creator><![CDATA[Soraya Cantos]]></dc:creator>
            <pubDate>Mon, 10 Mar 2025 17:46:55 GMT</pubDate>
            <atom:updated>2025-03-21T11:09:11.433Z</atom:updated>
            <content:encoded><![CDATA[<p><strong>Why Font Loading Matters for UX, SEO, and Site Performance</strong></p><p>Fonts play an important role in web design, when fonts loaded dynamically there is first a default rendering, and then the desired font is applied. This can cause a shift in the UI rendering because the browser initially renders the page using a fallback font, which is the browser’s default font. This issue is particularly visible when the user has a very poor internet connection. By default, <strong>the browser will display its own default font until the intended font is fully loaded and can be rendered</strong>. Usually, important differences can be observed, making the rendering appear unpolished. When loaded, fonts can affect font size, layout display, and the positioning of elements.</p><p>This frustrating visual changes can be tracked by a metric called the <strong>cumulative layout shift (CLS)</strong>. The more stable the page is, the better will be the CLS score. Improving the CLS score, increases site performance and both UX and SEO will benefit from it.</p><p><strong>How to handle fonts efficiently with Next.js and TailwindCSS</strong></p><p>To mitigate these issues, Next.js optimizes fonts through the @next/font module. This approach:</p><ul><li>Downloads font files at <strong>build time</strong>.</li><li>Hosts fonts alongside <strong>static assets</strong>.</li><li>Eliminates extra <strong>network requests</strong>, improving performance.</li></ul><p>When starting a new Next.js application, fonts from next/font/google are provided by default in the RootLayout of our application as variable fonts.</p><pre>import { Geist, Geist_Mono } from &quot;next/font/google&quot;;<br>import &quot;./globals.css&quot;;<br><br>const geistSans = Geist({<br>  variable: &quot;--font-geist-sans&quot;,<br>  subsets: [&quot;latin&quot;],<br>});<br><br>const geistMono = Geist_Mono({<br>  variable: &quot;--font-geist-mono&quot;,<br>  subsets: [&quot;latin&quot;],<br>});<br><br>export const metadata = {<br>  title: &quot;Create Next App&quot;,<br>  description: &quot;Generated by create next app&quot;,<br>};<br><br>export default function RootLayout({ children }) {<br>  return (<br>    &lt;html lang=&quot;en&quot;&gt;<br>      &lt;body<br>        className={`${geistSans.variable} ${geistMono.variable} antialiased`}<br>      &gt;<br>        {children}<br>      &lt;/body&gt;<br>    &lt;/html&gt;<br>  );<br>}</pre><ul><li>variable: &#39;--font-geist-sans&#39; → Defines a CSS variable for Tailwind to use.</li><li>className={${geistSans.variable} ${geistMono.variable} antialiased} → Applies fonts to the body.</li></ul><p>If you check your default globals.css file you will have something like this:</p><pre>@import &quot;tailwindcss&quot;;<br><br>@theme inline {<br>  --color-background: var(--background);<br>  --color-foreground: var(--foreground);<br>  --font-sans: var(--font-geist-sans);<br>  --font-mono: var(--font-geist-mono);<br>}</pre><p>You can now just use font-sans and font-mono as your tailwind classNames.</p><p>You can also apply as many fonts as you want in your application by following this simple steps:</p><ul><li>Import the fonts from next/font/google</li><li>Add them to the bodytag</li><li>If you want to use shorter Tailwind classNames modify globals.css</li></ul><pre>import { Geist, Geist_Mono, Lora, Roboto, Montserrat } from &quot;next/font/google&quot;;<br>import &quot;./globals.css&quot;;<br><br>const geistSans = Geist({<br>  variable: &quot;--font-geist-sans&quot;,<br>  subsets: [&quot;latin&quot;],<br>});<br><br>const geistMono = Geist_Mono({<br>  variable: &quot;--font-geist-mono&quot;,<br>  subsets: [&quot;latin&quot;],<br>});<br><br>const lora = Lora({<br>  variable: &quot;--font-lora&quot;,<br>  subsets: [&quot;latin&quot;],<br>});<br><br>const roboto = Roboto({<br>  variable: &quot;--font-roboto&quot;,<br>  subsets: [&quot;latin&quot;],<br>});<br><br>const montserrat = Montserrat({<br>  variable: &quot;--font-montserrat&quot;,<br>  subsets: [&quot;latin&quot;],<br>});<br><br>export default function RootLayout({ children }) {<br>  return (<br>    &lt;html lang=&quot;en&quot;&gt;<br>      &lt;body<br>        className={`${geistSans.variable} ${geistMono.variable} ${lora.variable} ${roboto.variable} ${montserrat.variable} antialiased`}<br>      &gt;<br>        &lt;div className=&quot;space-y-4 m-72&quot;&gt;<br>        &lt;p className=&quot;font-sans&quot;&gt;This text uses GeistSans&lt;/p&gt;<br>        &lt;p className=&quot;font-[family-name:var(--font-geist-sans)]&quot;&gt;This text uses GeistSans&lt;/p&gt;<br>        &lt;p className=&quot;font-mono&quot;&gt;This text uses GeistMono&lt;/p&gt;<br>        &lt;p className=&quot;font-[family-name:var(--font-geist-mono)]&quot;&gt;This text uses GeistMono&lt;/p&gt;<br>        &lt;p className=&quot;font-lora&quot;&gt;This text uses Lora&lt;/p&gt;<br>        &lt;p className=&quot;font-[family-name:var(--font-lora)]&quot;&gt;This text uses Lora&lt;/p&gt;<br>        &lt;p className=&quot;font-roboto&quot;&gt;This text uses Roboto&lt;/p&gt;<br>        &lt;p className=&quot;font-[family-name:var(--font-roboto)]&quot;&gt;This text uses Roboto&lt;/p&gt;<br>        &lt;p className=&quot;font-montserrat&quot;&gt;This text uses Montserrat&lt;/p&gt;<br>        &lt;p className=&quot;font-[family-name:var(--font-montserrat)]&quot;&gt;This text uses Montserrat&lt;/p&gt;<br>        &lt;/div&gt;<br>        {children}<br>      &lt;/body&gt;<br>    &lt;/html&gt;<br>  );<br>}</pre><p>globals.css could look like this:</p><pre>@import &quot;tailwindcss&quot;;<br><br>@theme inline {<br>  --color-background: var(--background);<br>  --color-foreground: var(--foreground);<br>  --font-sans: var(--font-geist-sans);<br>  --font-mono: var(--font-geist-mono);<br>  --font-montserrat: var(--font-montserrat);<br>  --font-lora: var(--font-lora);<br>  --font-roboto: var(--font-roboto);<br>}</pre><p>As a result, this is what you’ll see in your browser:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*t_idkUOE1KnP6u-uSBSk4A.png" /></figure><p>If you want to have more control over the font styles or weights, you can configure the next/font module to load only the necessary weights and styles. For example:</p><pre>const lora = Lora({<br>  variable: &quot;--font-lora&quot;,<br>  subsets: [&quot;latin&quot;],<br>  weight: &quot;400&quot;, // Loads only the regular weight<br>});</pre><p>This ensures that you’re not overloading the page with unnecessary font files, making the page faster to load.</p><p><strong>Conclusion</strong></p><p>By using Next.js and TailwindCSS, you can optimize the way fonts are loaded on your site, minimizing layout shifts and enhancing page stability. Using the @next/font module, fonts are downloaded at build time, hosted alongside static assets, and applied via CSS variables. This approach reduces unnecessary network requests, improving both site performance and user experience.</p><p>For websites that require custom or local fonts, this method can be extended to include additional font sources using next/font/local module. Custom fonts can be managed similarly by importing them into your Next.js project and setting them as CSS variables.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3a8163f2d511" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Next.js App Router: Basic Project Structure Explained]]></title>
            <link>https://medium.com/@sorayacantos/next-js-app-router-basic-project-structure-explained-34d5342e3d98?source=rss-56deaaa77031------2</link>
            <guid isPermaLink="false">https://medium.com/p/34d5342e3d98</guid>
            <category><![CDATA[routing]]></category>
            <category><![CDATA[nextjs]]></category>
            <category><![CDATA[code]]></category>
            <category><![CDATA[react]]></category>
            <category><![CDATA[nextjs-app-router]]></category>
            <dc:creator><![CDATA[Soraya Cantos]]></dc:creator>
            <pubDate>Sat, 08 Mar 2025 14:01:33 GMT</pubDate>
            <atom:updated>2025-03-08T14:01:33.558Z</atom:updated>
            <content:encoded><![CDATA[<h3><strong>1/ Why use Next.js and Next App Router in the first place ?</strong></h3><p>If you are coding with React, it is no longer recommended to use React on its own. There are powerful existing frameworks that leverage React’s advantages. The official React documentation itself recommends using a framework when starting a new React application.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*O3Z6q4oaRLKW-0mzj0uapQ.png" /><figcaption><a href="https://react.dev/learn/creating-a-react-app">https://react.dev/learn/creating-a-react-app</a></figcaption></figure><p>On top of that, React developers state that Next.js, and especially Next App Router (v13+), has become the main and recommended framework for React applications. It is also well-maintained and supported by millions of users.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0nf1fg65EKi6Hgscbz1w1g.png" /><figcaption><a href="https://react.dev/learn/creating-a-react-app">https://react.dev/learn/creating-a-react-app</a></figcaption></figure><h3><strong>2/ Understanding Next App Router project structure</strong></h3><p>Next.js started as a simple framework for React applications, handling routing, SEO optimization, and server-side rendering. Among other advantages, Next App Router adds a modern and flexible architecture that requires developers to think differently and structure their code accordingly.</p><p>With Next App Router, you can create complex routing scenarios to optimize organization and rendering, all based on a simple file-and-folder-based routing system.</p><h4><strong>Basic structure</strong></h4><p>When creating a new Next.js App project, you will be asked if you want to place the app folder (router) inside a src folder. As the Next.js team explains, using the src folder instead of placing the app folder in the root of your project can help separate application code from project configuration files.<br> Once inside the app folder, you can start structuring your project.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*7lernf8QDA51INwzxEid6g.png" /></figure><h4>Layouts and pages</h4><p>In Next App Router, routes are defined by files and folders.<br> Two main files help create a route segment and display content: a layout and a page. These files must be named <strong>layout.js</strong> and <strong>page.js</strong>to be recognized by Next.js. You can choose the file extension based on the language you are using: either JavaScript (.js or .jsx) or TypeScript (.ts or .tsx).<br> Layouts and pages inside folders can be nested to create complex routing paths.</p><p>Everything starts with the <strong>RootLayout</strong>, which is the entry point of the app’s routing system. Only this layout is mandatory — other nested layouts are optional. You don’t necessarily need to display anything in RootLayout, but you must include at least a children prop for your pages and nested layouts to be displayed.</p><p>For example, your RootLayout can contain a <strong>header</strong> and a <strong>footer</strong>, elements that will be displayed across your entire application. A typical RootLayout might look like this:</p><pre>export default function RootLayout({ children }) {<br>  return (<br>    &lt;html lang=&quot;en&quot;&gt;<br>     &lt;head&gt;<br>      Head content<br>     &lt;/head&gt;<br>     &lt;body&gt;<br>      &lt;header&gt;<br>       &lt;nav&gt;<br>        Nav content<br>       &lt;/nav&gt;<br>      &lt;/header&gt;<br>      &lt;main&gt;<br>      {children}<br>      &lt;/main&gt;<br>      &lt;footer&gt;<br>       Footer content<br>      &lt;/footer&gt;<br>     &lt;/body&gt;<br>    &lt;/html&gt;<br>  );<br>}</pre><p>The entry point of each route is the <strong>layout.js</strong> file, and, as its name suggests, it is meant to display general UI. To create a layout, <strong>default export</strong> a React component inside <strong>layout.js</strong>.<br>Layouts accept a children prop, which is passed to the component to display nested pages and layouts, creating <strong>nested routes</strong>.<br>Layouts remain interactive while preserving state and avoiding unnecessary re-renders. Each parent layout will be displayed along with its nested route segments.</p><p>Example of an application with nested routes, and what is displayed in my-app/shop/bikes:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*G_FLP5fqgsytKaUVnrJZIQ.png" /><figcaption>my-app/shop/bikes</figcaption></figure><p>For a route segment to exist, the folder must contain at least a <strong>page.js</strong> file. To display page UI content, <strong>default export</strong> a React component inside page.js.</p><p>In the following app configuration:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bJraDh_P03Tak_UhPRfGJA.png" /></figure><ul><li>my-app/shop is <strong>not</strong> a valid URL path</li><li>my-app/shop/bikes <strong>will</strong> display the corresponding page content</li></ul><h4>Grouping routes</h4><p>In large applications, you may want to organize your routes based on business or code logic <strong>without</strong> creating a route segment in the URL. You can do this by <strong>grouping routes</strong> using <strong>parentheses</strong> in the folder name:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2JllXnJCwUb62nKhfGAnJQ.png" /></figure><p>The folder enclosed in parentheses is excluded from the URL path system.<br> From the previous image, only the paths my-app/bikes and my-app/planes exist.<br> Grouping both routes under the (shop) folder helps keep the code organized and improves routing clarity.</p><h4>Dynamic routing</h4><p>Dynamic routing is another basic yet powerful feature of the Next.js routing system. It was already available before the introduction of App Router.<br> It is useful when you don’t know the exact path in advance and need a <strong>dynamic path system</strong>.</p><p>For example, if you are developing an <strong>online bike store</strong> and need to create a page and route for each bike model, you can implement a <strong>dynamic segment</strong> by wrapping a folder name in square brackets:</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*GTLoKiluxWEFUZah0ndZrg.png" /></figure><p>Here, [model] will take any value, allowing URLs like:</p><ul><li>my-app/shop/bikes/thunderbolt</li><li>my-app/shop/bikes/phantom</li></ul><h4>Combining key routing concepts</h4><p>Imagine an app where you post <strong>blog articles</strong> for the public while also tracking reading statistics privately. The <strong>statistics routes</strong> are protected. You could separate <strong>public</strong> and <strong>protected</strong> routes while keeping authentication logic separate from protected routes.</p><p>In the following example, only these URLs exist:</p><ul><li>my-app/</li><li>my-app/blog/first-article (or any custom slug under /blog)</li><li>my-app/login</li><li>my-app/signup</li><li>my-app/stats</li></ul><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*0pHtGM1MQLSjL-I3TOmdzA.png" /></figure><p>Find here what will be displayed :</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*TB95L7RZg0i6B3DUmgKJug.png" /><figcaption>my-app/</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*eNidiMwUrLJSmiksrKCZdg.png" /><figcaption>my-app/blog/first-article (or any custom slug under /blog)</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ofaQyAfS1JqJoS2-46ywBA.png" /><figcaption>my-app/login</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*YxSTO050OHI18r45_Z6NNg.png" /><figcaption>my-app/signup</figcaption></figure><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*SqovOuYo-klc0TJCsqHpIQ.png" /><figcaption>my-app/stats</figcaption></figure><h4><strong>More In-Depth Articles Coming Soon</strong></h4><p>A series of articles about Next.js and Next App router are coming, especially one more detailed and exhaustive about Next App router routing system. All routing possibilities will be explained, with use cases provided to identify the best approaches for better performance and greater code clarity. So don’t forget to follow my account !</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=34d5342e3d98" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Is Confidence just a skill you can build ?]]></title>
            <link>https://medium.com/@sorayacantos/is-confidence-just-a-skill-you-can-build-f86b91cc5a4d?source=rss-56deaaa77031------2</link>
            <guid isPermaLink="false">https://medium.com/p/f86b91cc5a4d</guid>
            <category><![CDATA[growth-hacking]]></category>
            <category><![CDATA[growth-mindset]]></category>
            <category><![CDATA[confidence]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[growth]]></category>
            <dc:creator><![CDATA[Soraya Cantos]]></dc:creator>
            <pubDate>Fri, 29 Nov 2024 10:22:12 GMT</pubDate>
            <atom:updated>2024-11-29T10:22:12.086Z</atom:updated>
            <content:encoded><![CDATA[<h3>Is <strong>Confidence</strong> just a skill you can build ?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*dpulYAYSAWnjXmq0wlBHqg.jpeg" /></figure><p><strong>Two years ago, I took an online personality test, and the result blew my mind: 95% introvert versus 5% extrovert.</strong> It made me question every moment of my childhood and adolescence. How could this be true?</p><p>This revelation probably explains why I’ve always admired people who excel at public speaking. It’s the trait I envy the most because it feels like the hardest one for me to master. I have no problem speaking one-on-one, but if there are more than three people in a group or an audience, my inner fears start to surface.</p><p>I clearly remember a time in high school when I actually thought giving presentations was fun.<br> So, what changed? Five years later, I found myself feeling incredibly anxious whenever I had to speak in public, and I couldn’t pinpoint what triggered that transformation.</p><p>When I started working in corporate organizations, I had no choice but to lead or participate in large meetings and present to clients. Over time, I began to feel comfortable with the process again. While I didn’t enjoy it as much as I once did, I wasn’t reluctant anymore. I had no option but to push myself through it.</p><p>Repetition helped me adjust. For work, I often had to pretend I was confident, even when I wasn’t. I truly embodied the saying, “Fake it till you make it.” By the end, I felt confident again when leading meetings and speaking in public.</p><p>Looking back, I’m proud of what I accomplished, but at the time, I didn’t enjoy the process. It was stressful, and it was the part of the work I liked the least.</p><p>Later, two things happened that changed my situation. First, I shifted my career path to one where public speaking wasn’t as frequent. Second, the COVID-19 pandemic cut off most social interactions. After a few years, I can now say I’m not as confident as I once was, but my mindset has completely changed. If needed, I know I can push myself to do it again. I know the confidence will return.</p><p>This time, however, the motivation is different. Now, I want this change for myself — because it comes from within me, not from an external obligation.</p><p><strong>Conclusion</strong><br> Pushing yourself into challenging situations can be valuable — that’s when real growth happens. But I believe it should be a conscious decision, not something imposed on you for vague or unclear reasons. “Because it’s my job” isn’t enough of an explanation.</p><p>That stress shouldn’t be constant, though, because it risks leading to burnout. Striking a balance is easier said than done, but it’s essential.</p><p>Even if it feels overwhelming, don’t shy away from trying new things. Growth often comes from stepping out of your comfort zone. And this time, do it because deep down, <em>you</em> truly want to.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f86b91cc5a4d" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[The Day I Created an AI Coloring Book and made… $0. Best Decision of My Life!]]></title>
            <link>https://medium.com/@sorayacantos/the-day-i-created-an-ai-coloring-book-put-it-up-for-sale-on-amazon-kdp-and-made-0-d87b998d9989?source=rss-56deaaa77031------2</link>
            <guid isPermaLink="false">https://medium.com/p/d87b998d9989</guid>
            <category><![CDATA[freelancing]]></category>
            <category><![CDATA[self-improvement]]></category>
            <category><![CDATA[side-hustle]]></category>
            <category><![CDATA[small-business]]></category>
            <category><![CDATA[life-lessons]]></category>
            <dc:creator><![CDATA[Soraya Cantos]]></dc:creator>
            <pubDate>Fri, 11 Oct 2024 12:51:25 GMT</pubDate>
            <atom:updated>2025-03-19T18:09:43.991Z</atom:updated>
            <content:encoded><![CDATA[<h4>This failure has taught me a lot</h4><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Yr1lSK2LEz8z86ZWV-Cmxg.png" /></figure><h3>How Everything started</h3><p>In early August, I started my journey as a freelancer and solo entrepreneur. I decided to try out one of the supposedly “easiest” ways to earn money online:</p><ul><li>Creating a children’s coloring book using AI and publishing it on Amazon KDP.</li></ul><h3>From Zero To Published</h3><p>I’ll be honest:</p><ul><li>I didn’t have a marketing strategy</li><li>I didn’t have a communication plan</li><li>I didn’t have any basic design skills</li><li>I wasn’t expecting much from a random online video I just found.</li></ul><p>I simply followed a YouTube tutorial that walked me through the process, step by step.</p><p><strong>But none of that really mattered.</strong></p><p><strong>The surprising part was just how easy it was to start.</strong></p><p>In about 10 hours, I went from idea to finished product, creating the illustrations, formatting the pages, and publishing it for the world to see.</p><h3>I Didn’t Make a Single Sale, But I Gained So Much More</h3><p>I didn’t make a single sale, but it didn’t bother me.</p><p>Instead, I realized that <strong>the barrier</strong> to trying something new — especially in today’s digital world — <strong>is almost nonexistent.</strong></p><p>I had jumped into this project with no background in design and no promotional plan, yet I managed to launch a product online.</p><p><strong>The experience taught me that making that first move is often the hardest step, and once you take it, everything else falls into place.</strong></p><p><em>For those interested in the book : </em><a href="https://www.amazon.fr/dp/B0DF38WXZL"><em>https://www.amazon.fr/dp/B0DF38WXZL</em></a></p><p><em>And the tutorial I followed : </em><a href="https://www.youtube.com/watch?v=1N-dI6IuVq0&amp;t=1s"><em>https://www.youtube.com/watch?v=1N-dI6IuVq0&amp;t=1s</em></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d87b998d9989" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>