Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 5 years ago

Desktop first using sass and flexbox

Tyshawn Anthony•115
@tyshawn-anthony
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


I wasn't sure if I needed to use absolute/relative positioning. I couldn't think of any other way to get the cards in the exact positions that they needed to be in. If anyone has another way, I'd love to be enlightened! Still very new to coding so thanks in advance!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Shashi Lo•1,345
    @shashilo
    Posted about 5 years ago

    Trying is apart of development. You keep trying and learning until you get better. I really like your hover animation. Super clean!

    You are right, there is a better way to implement this. Try to avoid exactly positioning main sections when developing. It's very difficult to maintain and it doesn't work well on multiple screen sizes. For me, I usually only use position: relative; with left/right/top/bottom on elements that needs to move just a little bit. In this case, these cards should be completed a different way. You could either look at making this with Flexbox or CSS Grid. The best way to get ideas is to look at how others from the community are implementing their solutions. Everyone does things differently and it will provide some guidance you're looking for.

  • Thomas Malice•135
    @thm01
    Posted about 5 years ago

    Cool hover effect, thanks for the idea :)

  • Pranshu Dobhal•295
    @pranshudobhal
    Posted about 5 years ago

    Hey Itchito, I loved the hover effect on cards. The way that I have positioned cards is using flexbox. I used bootstrap 4 which now uses flexbox for positioning. So, maybe you can give it a try.

Join our Discord community

Join thousands of Frontend Mentor community members taking the challenges, sharing resources, helping each other, and chatting about all things front-end!

Join our Discord
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

How does the accessibility report work?

When a solution is submitted, we use axe-core to run an automated audit of your code.

This picks out common accessibility issues like not using semantic HTML and not having proper heading hierarchies, among others.

This automated audit is fairly surface level, so we encourage to you review the project and code in more detail with accessibility best practices in mind.

How does the CSS report work?

When a solution is submitted, we use stylelint to run an automated check on the CSS code.

We've added some of our own linting rules based on recommended best practices. These rules are prefixed with frontend-mentor/ which you'll see at the top of each issue in the report.

The report will audit all CSS, SCSS and Less files in your repository.

How does the HTML validation report work?

When a solution is submitted, we use html-validate to run an automated check on the HTML code.

The report picks out common HTML issues such as not using headings within section elements and incorrect nesting of elements, among others.

Note that the report can pick up “invalid” attributes, which some frameworks automatically add to the HTML. These attributes are crucial for how the frameworks function, although they’re technically not valid HTML. As such, some projects can show up with many HTML validation errors, which are benign and are a necessary part of the framework.

How does the JavaScript validation report work?

When a solution is submitted, we use eslint to run an automated check on the JavaScript code.

The report picks out common JavaScript issues such as not using semicolons and using var instead of let or const, among others.

The report will audit all JS and JSX files in your repository. We currently do not support Typescript or other frontend frameworks.

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