Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 25 days ago

Blog Preview Card Challenge 02 | CSS + HTML

TheTCGProject•40
@TheTCGProject
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 think this is a near replication of the images shown for the challenge. I'm happy to receive an application that is close to the request, learn more about CSS and HTML production, and have a hovering element included as well.

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

Getting the main div centralised, which is a similar challenge I had with the 1st challenge. But finally, after some experimentation and browsing the forums, I've managed to get it sussed.

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

Some advice on the inner elements of the div to get them working together more smoothly, it took a lot of padding and margin experimenting to get something that replicated the challenge, which I feel may have complicated this more than anything.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Elmar Chavez•540
    @CodingWithJiro
    Posted 25 days ago

    Hi TheTCGProject!

    • You nailed the visual side of this challenge! However, if you would like to upgrade your project more, use PerfectPixel. This helped me a ton in getting my solution to as close as possible to the intended design. I'm sure this will help you too!

    • I opened your live site and it seems like your card is squished at 320px device width. A simple <div> container with padding-inline can solve this.

    • You mentioned that you heavily rely on trial-and-error for margins and paddings. I've been there and my suggestion is for you to use display: flex for internal elements not only limited to the main container. This way, you will not be relying on floats anymore. Personally, I RARELY use float property in my current projects.

    • Regarding your HTML, there is an extra equal sign for the </div=> that you may want to edit out:

    <div class="img-container"><img class="img-article" src="/assets/images/illustration-article.svg"></div=>
    

    All in all, good job. I hope this feedback 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