Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 11 months ago

Four-card-web

Jackson-zablon15•330
@Jackson-zablon15
A solution to the Four card feature section challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


What are you most proud of, and what would you do differently next time?

I'm proud of using grid to make the layout

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

I encountered the challenge of styling space between paragraphs and component as their appear in the design. How to know the current space between paragraphs so i can know the amount to add up for example i could set margin of paragraphs to zero but still there was some space between them making it difficult to know the space to add so as they could look like in the design. I used developer tool.

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

I would like help on best ways how to style and calculate space between paragraphs. Is good to use margin, gap or other ways?

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    MikDra1•7,450
    @MikDra1
    Posted 11 months ago

    Nice one 😀

    If you are curious how you can do this straight lines on the top of each card here is my tip:

    Create another element in each of the cards. Then position this element absolute. Card should be positioned relative. At the end you need to give this element a height of 3px width of 100% and top 0 and left 0. You can also use ::after or ::before pseudo elements to create these.

    Hope you found this comment helpful 💗

    Good job and keep going 😁😊😉

  • Rastislav Hepner•180
    @raswonders
    Posted 11 months ago

    Hi @Jackson-zablon15,

    you've created nice solution. The way you handled the top stripes on those feature cards inspired me 🕵️‍♀️ and I reimplemented mine too .

    Regarding the spacing inside feature cards I'd handle it slightly different. It's better when header of feature is sticking to the start of the flex container and icon to the the end of it. You already using flexbox so its as easy as removing those margins and setting items-justify: between on your flex container.

    Regarding layout shift, i'd propose to use larger width when shift happens. Currently it shifts prematurely and horizontal scrollbars appear between 750px...1150px

    Hope this note will help you in some way.

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