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

Chris Cablish

@ChrisCablishSt. Louis, MO310 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

  • Tic-Tac-Toe Game (React.js, React Bootstrap, SaSS)


    Chris Cablish•310
    Submitted over 1 year ago

    0 comments
  • Dictionary Web App - My first react app (SaSS, Bootstrap)


    Chris Cablish•310
    Submitted almost 2 years ago

    0 comments
  • github-user-search (github REST API, SaSS, Bootstrap, Responsive CSS )


    Chris Cablish•310
    Submitted almost 2 years ago

    0 comments
  • pricing-component (SaSS, bootstrap, vanillaJS)


    Chris Cablish•310
    Submitted almost 2 years ago

    0 comments
  • bmi-calculator with SaSS, bootstrap, vanilla JS


    Chris Cablish•310
    Submitted about 2 years ago

    1 comment
  • Age Calculator (vanilla js, regEx, mobile first design)


    Chris Cablish•310
    Submitted about 2 years ago

    0 comments
View more solutions

Latest comments

  • DevMedic11•20
    @DevMedic11
    Submitted almost 2 years ago

    Responsive QR Code

    3
    Chris Cablish•310
    @ChrisCablish
    Posted almost 2 years ago

    Hey there,

    Most (if not all) of the challenges on this website provide multiple designs for the same challenge. Navigate to the provided mobile design and flesh that one out first. Once you have completed it, move on to the tablet (if applicable), and finally the desktop design. My understanding of the rationale is that it is fundamentally easier to expand a compact design than it is to shrink down a larger (desktop) design. Also, internet connections tend to be less stable on mobile, so having the compiler encounter the mobile design first helps with performance on mobile devices. Be sure to check into media queries for CSS responsive design if you haven't already done so. Hope this helps.

    -Chris

  • Dzhangir Bayandarov•40
    @Dzhango
    Submitted about 2 years ago

    Static Responsive Results Summary component

    3
    Chris Cablish•310
    @ChrisCablish
    Posted about 2 years ago

    I think the fact that the solution you provided includes breakpoints where the design changes after the screen reaches a certain width (from mobile to desktop) means that technically your design is responsive. If you wanted the width to change along with the width of the screen you could look into using width as a percentage. For instance, if you wanted your component to take up 80% of the width of the body of your desktop design at all times you could set that element to width: 80%. That way the component will always take up 80% of its container (probably <body>) no matter if the screen is 1000px wide or 1440px wide or anywhere in between. Not sure if this is what you are asking exactly but figured i would give it a go.

    Marked as helpful
  • Zain•90
    @ZainA11
    Submitted over 2 years ago

    Product Preview Card Component

    1
    Chris Cablish•310
    @ChrisCablish
    Posted over 2 years ago

    Hi Zain, I'm pretty new to front-end, but it looks to me like if you wanted to get the spacing between your elements closer to what is depicted in the desktop challenge design, you could use the following on your div.preview selector:

    display:flex; flex-direction: column; justify-content: space-between or space around.

    This should cause the elements to space out evenly, filling out the entirety of the available horizontal space.

Frontend Mentor logo

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