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

Blog preview card

shadazls•200
@shadazls
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?

Given my current skill level, I use these projects as simple entertainment and reminders for the basics, so I'm not particularly proud of anything. However, I think I would use Bootstrap for responsiveness next time.

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

I find it frustrating that not all color values are provided in projects. For instance, in this project, the border color of the card isn't specified. Additionally, I often struggle with whether to strictly adhere to provided specifications, such as font sizes, to accurately replicate the project. However, due to differences in screen resolutions, following exact measurements may not yield the same result. For example, instead of using fixed pixel values for elements like the card dimensions, I calculate the percentage value from Figma and implement it in my code, but this doesn't always produce the intended outcome.

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

I would appreciate assistance with responsive design and utilizing flexbox effectively.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sayeed Munees•130
    @sayeedmunees
    Posted over 1 year ago

    The dimensions of the card are so accurate, as well as the dimensions of the image. When screen size the contents are coming outside the card, you may can fix this by, not hard coding the height and width. Also, try using media queries to make the webpage responsive. Check out this MDN web docs link to know more - (https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_media_queries/Using_media_queries). You may learn more about it from YouTube too. Talking about color you may can use a color picker to make it similar to the given. Front-end Mentor provides a style guide, which contains the colors used.

    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
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