Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted over 1 year ago

Blog Preview Card Challenge Solution

6xg0d•210
@6xg0d
A solution to the Blog preview card 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 that i spend most of my time with the CSS instead of HTML, i was way more comfortable to think the structure just by looking at the example.

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

One of the main problems that i had was positionating elements exactly where i want. Especially the space between the footer and the resume paragraph. I did think in a way to put the footer 24px away from the bottom using the row-gap property. Even when the space isn't exactly the same that the one in the design, i'm still pretty happy with the results, and looking forward to improve the code in the future.

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

I want to know more about in which cases use margin or padding (even knowing the definitions in the practice in some cases i'm a little indecisive about which one should i use). Also, would like to know how to improve the CSS code and reduce the amount of lines or selectors to create the same results with the minimum amount of code possible

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • perterHUAN•250
    @perterHUAN
    Posted over 1 year ago
    • Using flex combined with row-gap (actually, just using gap would suffice since there's no wrapping occurring here) on the article element to create spacing between child elements is a good method; elsewhere in the code, you could apply this approach instead of repeatedly using margin.
    • By setting a padding on the article, it eliminates the need to set margin-left and margin-right over and over again on the child elements.
    • I think it might be less appropriate to use header and footer here as they typically refer to headers or footers for the entire page rather than within the context used.
    • The hover animation seems to be missing; when the mouse hovers over the card, the box-shadow should shift downwards.
    • It's worth considering using CSS variables to standardize the spacing values throughout your stylesheet, making maintenance and modification more convenient.
    • This is my suggested solution; please note that I am not an expert, and I welcome your feedback and suggestions for discussion and mutual learning.
    Marked as helpful
  • Jason Delgado•40
    @delgado-jason
    Posted over 1 year ago

    Great job! I really like your semantic code layout. It makes sense. I was struggling to figure out which tags were appropriate.

    When to use margin vs padding can be subjective at times. It took me a while to figure that out. Generally though, imagine you have a box with text in it. The box has a border. Everything on the "outside" of the box is affected with margin. Padding affects everything around your text inside the box.

    Hope this helps.

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub