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

blog-preview

Abdulelah || عبدالإله•50
@Abd-ulelah
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Tharun Raj•1,330
    @Code-Beaker
    Posted 10 months ago

    Hi there, congratulations on completing this challenge... You've done a great work with this one! 🎉

    I have checked your live site preview as well as your source code and I would like to forward some of my suggestions regarding your solution that might help you improve it.

    • Your site isn't fully responsive, meaning it currently sticks to the left side of the screen on the desktop. I think you've prioritized mobile screens here. But, make sure your site is responsive for all screens since it is an important part of building websites. Give this article a read and get an idea about making a website responsive.
    • NEVER use the id attribute for styling elements. It is more oriented towards scripting with JavaScript. Instead, use the class attribute to select your elements using the class. Here's an article that explains the purpose of the ID attribute.
    • Write your CSS inside an external CSS file to keep your HTML file smaller.
    • This is subjective and optional. This is important when you're sharing your code with other developers and collaborating on a project. But, try to improve the class names you give.
    • Instead of px units, use relative units like rem. Read this article about it.

    I hope you find these points helpful in improving your solution. 😄

    Marked as helpful
  • INDavid04•70
    @INDavid04
    Posted 10 months ago

    Hi! Nice work! Instead of using .Desktop class you could add background-color to the body and also display: flex; align-items: center; justify-content: center; to center the card vertically and horizontally. You could add border-radius to the image too. Also you could center the user name using display: flex; align-items: center; on the div parent of the image and text for example. Succes!

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 1st-party linked stylesheets, and styles within <style> tags.

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.