Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 5 months ago

Blog Card Preview using HTML and CSS

FrontendDev•60
@Ali-Learner
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?

Proud of making the design as similar as possible

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

CSS optimization is the main challenge I encounter and I am not able to solve it

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

CSS optimization is the main challenge I encounter

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Simon Cassan•260
    @SimonCassan
    Posted 5 months ago

    Hello, You’ve done a great job overall! I do have a few suggestions for improvement:

    HTML Enhance your semantic markup by adding <main> and <footer> elements where appropriate. Always include an <h1> element and ensure you don’t skip heading levels. Avoid using HTML elements like <strong> purely for styling; instead, use CSS for visual presentation.

    CSS Consider using rem for padding and margin values—it’s generally a better practice for scalability. Adding a fixed width or max-width to your <img> elements would improve the layout on very large screens. You might want to add align-items: center; to your .profile class for better alignment. The layout is not fully responsive for mobile. Replace width: 25% on the card with a max-width to improve its adaptability on smaller screens.

    Keep up the great work! 😊

    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