Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
10
Comments
10

Samuel Gomez

@samuelgomez05130 points

I’m a mysterious individual who has yet to fill out my bio. One thing’s for certain: I love writing front-end code!

Latest solutions

  • Time tracking dashboard with React and Tailwind god

    #react#tailwind-css

    Samuel Gomez•130
    Submitted 20 days ago

    1 comment
  • Newsletter sign up with Astro and tailwind god

    #astro#tailwind-css

    Samuel Gomez•130
    Submitted 5 months ago

    1 comment
  • Article preview component using Astro with tailwind

    #astro#tailwind-css

    Samuel Gomez•130
    Submitted 5 months ago

    1 comment
  • Testimonials grid section using react and tailwind

    #react#tailwind-css

    Samuel Gomez•130
    Submitted 6 months ago

    1 comment
  • Four card feature section with react and tailwind css

    #react#tailwind-css

    Samuel Gomez•130
    Submitted 6 months ago

    1 comment
  • Product preview card component practicing react with styled components

    #react#styled-components

    Samuel Gomez•130
    Submitted 6 months ago

    1 comment
View more solutions

Latest comments

  • P
    Mhd Rizki Candra•270
    @rizkicaandra
    Submitted 21 days ago
    What challenges did you encounter, and how did you overcome them?

    design size is not common.. this really made me struggle to adjust the size..

    simple time tracking dashboard

    #svelte#tailwind-css
    1
    Samuel Gomez•130
    @samuelgomez05
    Posted 20 days ago

    Good job 👍

  • NameLessS•190
    @NameLesSs00
    Submitted 5 months ago
    What are you most proud of, and what would you do differently next time?

    done

    What challenges did you encounter, and how did you overcome them?

    .

    What specific areas of your project would you like help with?

    .

    sign-up-form-with-success-message with nextjs and tailwind

    #tailwind-css#next
    1
    Samuel Gomez•130
    @samuelgomez05
    Posted 5 months ago

    It's ok 👍

  • Rounak Kumar Singh•110
    @rounakkumarsingh
    Submitted 5 months ago
    What specific areas of your project would you like help with?

    Implementing the share action section.

    Article Preview Component

    #tailwind-css
    1
    Samuel Gomez•130
    @samuelgomez05
    Posted 5 months ago

    Good job, but remember to use html semantics h1, p, article

  • P
    Anonymous Coder•200
    @AnonymousCoder323
    Submitted 6 months ago

    Testimonials Grid using Astro and Tailwind

    #astro#tailwind-css
    1
    Samuel Gomez•130
    @samuelgomez05
    Posted 6 months ago

    Is very similar to the design, good job 👍

  • P
    Anonymous Coder•200
    @AnonymousCoder323
    Submitted 6 months ago

    Four Card Feature Section w/ Tailwind and Astro

    #tailwind-css#astro
    1
    Samuel Gomez•130
    @samuelgomez05
    Posted 6 months ago

    Good job! 🎉

  • P
    Mars - Martiniano Leguizamon•275
    @martinianol
    Submitted 6 months ago
    What are you most proud of, and what would you do differently next time?

    Solution Retrospective – Product Preview Card

    👎 What I Didn’t Enjoy

    While this project helped reinforce responsive UI principles, I found it frustrating that there was no consistent gap across all elements. • The design inconsistencies forced me to create a custom Flex component just to handle spacing properly. • Instead of relying on natural layout flow, I had to manually pass gapMob and gapDesktop props everywhere. • This felt unnecessarily repetitive and made the code less clean than I would have liked.

    💡 What I Learned & Would Do Differently • A better design system with global spacing variables (--spacing-sm, --spacing-md, --spacing-lg) would have helped. • Instead of per-component custom gap values, a consistent spacing scale across all components would prevent layout frustration. • If possible, using CSS Grid for better gap management might have worked better than flex.

    ✅ Key Takeaways • Flexbox is powerful but can be painful when spacing isn’t uniform. • Consistency in design is crucial—without it, we waste time fixing layout gaps. • Custom components should simplify work, not make it more tedious.

    While the final product looks great, the process was not enjoyable due to constant layout tweaking. 🚀 If I were to redo this, I’d prioritize a spacing system for a smoother workflow!

    What specific areas of your project would you like help with?

    🚀 3. Cleaner Code & Readability

    If the codebase feels messy or repetitive: ✅ Optimize the Flex component to be more efficient. ✅ Reduce overuse of props and instead use default values where possible. ✅ Improve file structure so components are modular and easier to maintain.

    Responsive Product Card

    #react#vite#styled-components
    1
    Samuel Gomez•130
    @samuelgomez05
    Posted 6 months ago

    It's very similar to the design, good job 🎉, maybe you could use the picture element for the responsive of the images

View more comments

Stay up to datewith new challenges, featured solutions, selected articles, and our latest news

Frontend Mentor

  • Unlock Pro
  • Contact us
  • FAQs
  • Become a partner

Explore

  • Learning paths
  • Challenges
  • Solutions
  • Articles

Community

  • Discord
  • Guidelines

For companies

  • Hire developers
  • Train developers
© Frontend Mentor 2019 - 2025
  • Terms
  • Cookie Policy
  • Privacy Policy
  • License

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub