Skip to content
  • Unlock Pro
  • Log in with GitHub
Profile
OverviewSolutions
6
Comments
4
P

Adam Winzenburger

@adamwinzdesignColumbia, Missouri, United States230 points

Currently located in Columbia, Missouri, USA. I'm working on random projects here and there, but I would love to get a full-time position as a front-end or full-stack developer working remotely! My favorite technologies are React, Redux, styled-components, TailwindCSS, framer-motion, and NodeJS.

I’m currently learning...

I'm currently learning TailwindCSS, but soon I will take the plunge into TypeScript and NextJS.

Latest solutions

  • Space tourism website using React, TailwindCSS, and framer-motion

    #react#react-router#tailwind-css#motion

    P
    Adam Winzenburger•230
    Submitted almost 3 years ago

    1 comment
  • Single-page design portfolio solution using React and TailwindCSS

    #react#tailwind-css

    P
    Adam Winzenburger•230
    Submitted about 3 years ago

    0 comments
  • Expenses chart component using React, TailwindCSS, and Chartjs.

    #react#tailwind-css#chart-js

    P
    Adam Winzenburger•230
    Submitted about 3 years ago

    1 comment
  • Responsive product card using React and Tailwind CSS

    #react#tailwind-css

    P
    Adam Winzenburger•230
    Submitted about 3 years ago

    0 comments
  • 3-column preview card using react and styled-components

    #react#styled-components

    P
    Adam Winzenburger•230
    Submitted about 3 years ago

    0 comments
  • Order summary card using react and styled-components

    #react#styled-components

    P
    Adam Winzenburger•230
    Submitted about 3 years ago

    0 comments

Latest comments

  • Kodjo Frimpong•10
    @cyrilkodjo
    Submitted about 3 years ago

    Product preview card component challenge

    1
    P
    Adam Winzenburger•230
    @adamwinzdesign
    Posted about 3 years ago

    There are a couple of ways of fixing the display issue between the main/wrapper element and the footer/attribution element. One way would be to wrap both elements into a common parent and then style that parent so that it displays both the main element and the footer element in a single column at all screen widths. For example, using flexbox, you could use a flex-column parent div to make sure that the main element and footer element are displayed in a single column at all screen widths, then you could still style the main element to be responsive without changing where the footer is displayed. In other words, the browser needs to know how to place the main element and footer elements in relation to each other, not just how they each look independently.

    Marked as helpful
  • kefiiiiR•70
    @kefiiiiR
    Submitted about 3 years ago

    Order Summary, HTML/CSS

    1
    P
    Adam Winzenburger•230
    @adamwinzdesign
    Posted about 3 years ago

    It's perfectly ok to set display:flex on a parent and a child, and many layouts require it. It also helps to have both a parent and child use display:flex when using a responsive design because you can change one or the other or both to flex-direction:column whenever you need to, depending on the screen width or whatever the use case requires.

  • Jordan•140
    @joanFaseDev
    Submitted about 3 years ago

    Product Preview Card solution using plain old HTML and CSS Grid

    3
    P
    Adam Winzenburger•230
    @adamwinzdesign
    Posted about 3 years ago

    I don't know if one format would be considered to be preferred over the other technically, but for the larger projects that I've seen here, when you get the figma design files, they typically include a color system guide that includes the color values in hex, rgb, and hsl, so you should be able to use whichever format you prefer without even having to convert the values yourself.

  • Lajoc•40
    @f-lajoc
    Submitted about 3 years ago

    QR Code Component Challenge using Media Query for Responsiveness

    #accessibility
    1
    P
    Adam Winzenburger•230
    @adamwinzdesign
    Posted about 3 years ago

    Looking at the challenge, it says that the card isn't meant to be responsive. Your deployed site looks fine to me at wider widths, nothing breaks or moves to a location that it isn't supposed to be. What is it about the component that you would like to change at desktop widths?

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