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

Blog Card Preview

P
Jacob Stone•130
@jacob-stone9554
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 am the most proud of how naturally the solution came together as I was developing it. I feel like I made it through this challenge more efficiently than the first one. If I were to do it differently, I would probably put the attribution into a footer tag rather than in main with the rest of the content.

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

One challenge I encountered was getting the margins around the title and the rest of the flex containers to align properly. I overcame this by adjusting the height of the title container to suit the spacing of the card.

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

I definitely need to work on making the responsiveness better. I have media queries, but I feel like it can still behave a little wonky when the viewport shrinks and grows.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Alex•3,130
    @Alex-Archer-I
    Posted about 1 year ago

    Hi there!

    You really have not to wrapping every element into the flex wrapper. In the big projects with a lot of content such approach could be very complicated =)

    You can style them directly and create spaces via margin or padding.

    <h1 class="title">Title</h1>
    <p class="text">First paragraph</p>
    <p class="text">Second paragraph</p>
    
    .title {
        margin-top: 1rem;
    }
    
    .text {
        margin-bottom: 0.5rem;
    }
    

    Or, since your container already has flex, you can use gap property to create gaps between it's inner tags.

    Of course, if you just want to train your flex skills or it's some new interesting technique, just ignore all that above =)

    Also I recommend you to use rem for the font-size properties. It can help users if they want to change their font size settings. To help you calculate value - by default 1rem = 16px.

    Anyway, quite a neat and accurate work (especially comments in code) and cool shadow-hover effect! Well done, keep going =)

  • JV2018•80
    @JV2018
    Posted about 1 year ago

    Nice work!

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