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

Blog Preview Card

Manny Verma•240
@mverma45
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 proud that I got the design really close to the actual design.

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

The challenges I encountered in this project were trying to get correct width for the pictures used. I just had to play around with the code to get the width's correct.

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

I want to know how I can create a container for my code that matches the example on frontendmentor.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • R A H U L•360
    @owlbunt
    Posted over 1 year ago

    why you want to switch images? it's the same image for all screen bro just take a look at my solution and see what i have done if you still don't understand any part of this feel free to ask I'm here for u - https://owlbunt.github.io/frontEndMentor/blogCard/

    and here is source code : https://github.com/owlbunt/frontEndMentor/tree/main/blogCard

    Marked as helpful
  • Marcos Travaglini•6,230
    @Blackpachamame
    Posted over 1 year ago

    The live site url should be https://mverma45.github.io/Frontend_Mentor/blog-preview-card-main/

    Well, here we have some topics:

    • The idea is not that your site is an image, you should do the same thing that appears in the design image, but with HTML and CSS. That is, you should create a card equal to the one in the design.
    • You have the images (illustration and avatar) in the assets/images folder

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