Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 2 years ago

Four card feature section using React

react
nikoProg•120
@nikoProg
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 am trying to learn react. I also had a lot of difficulties setting the styles properly. Here are the problems.

  1. the colored top part of cards, is it a border or not? Mine does not look the same.
  2. the layout of the 4 cards, I had to add extra divs and then tries to somehow arrange them to look like on the picture, but it was extremely difficult. I tried using grid and flex, but I was not sure how to set up the empty space in the 1st and 3rd column.
  3. I could not put an <img> tag with a path to the given SVGs, but instead, I had to copy the entire SVG code inline. The problem was a path error "could not find the file specified". I was not sure how.
  4. The positioning of the SVGs is not good. I tried using absolute positioning, but every time I would use "top" or "bottom", all 4 SVGs would arrange on top of each other for some reason.
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • J.D. Browne•890
    @PeshwariNaan
    Posted over 2 years ago

    Hello nikoProg - Nice work on completing the challenge, it looks good.

    Here's a few things you could do that might help.

    • For the layout, I think it would be easier to use a grid for the cards. You could have something like.
    .card_container {
    display: grid;
    width: 80vw;
    height: 70vh;
    grid-template-columns: repeat(3, 1fr);
    grid-template-rows: repeat(3, 1fr);
    

    These values are just a quick guess, you would have to figure the height and width of the container as per your design. But now you can assign each card to right where you want them in the styling for your individual cards

    .card_1{
     grid-column: 1 / 2;
    grid-row: 2 /4;
    

    Then do that for the other 3 cards but changing where in the grid you want them buy changing the grid-column and row values. See here for more info on GRIDS . When you get more comfortable you could assign the positions via props but that is beyond the scope of this project.

    • To use an svg as an image src just import the svg into your component file like: import sun from '../../assets/icon-sun.svg'. Then just use <img src={sun} onClick={toggleThemeHandler} alt='sun icon' /> . When you import like this, the name doesn't matter, just make sure the path is correct. For example I could have used import apple from '../../assets/icon-sun.svg' and as long as I use src={apple} it will still work.

    • Get into the habit of building individual components to get the benefits of react. That is what react is for. Putting everything into your app.js and not dividing up your code will lead to trouble.

    I hope this helps. Happy coding

    Marked as helpful

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

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