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

Blog Preview Card Using HTML & CSS

Nasrul Khakim•30
@illuminasrul
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


This is a Blog Preview Card, created using HTML and CSS. This project requires some basic knowledge of HTML and CSS, also little bit of understanding design principle would be so helpful.

This is perfect for beginner in web development to get the hands dirty by solving real world problem.

The challenge is to build and get it look as close as possible. I can use any tools I like to help me complete the challenge.

Users should be able to :

  • See hover states for interactive elements

feel free to give me some feedback, that’d be really helpful for me

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rebecca Padgett•2,100
    @bccpadge
    Posted over 1 year ago

    Hello @illuminasrul. Congratulations on completing this challenge!!!🎉

    I have a few suggestions you might be interested in to improve your solution.

    HTML 📃:

    • Wrap all your content using the <main> tag
    • Images that are decorative you can leave the alt text blank and add aria-hidden: true; so it can be ignored by screen readers
    • Add alt text to the avatar image: `alt="headshot of Greg Hooper">
    • For the published date you can wrap the date using the <time> tag Example
    <p class="metadata">
       Publish <time datetime="2023-12-21">21 Dec 2023</time> 
    </p>
    
    • Your div.container has unnecessary CSS styles
    .container{
      max-width: 1440px; */
      /* height: 100vh; */
      /* margin: 0 auto; */
      display: grid;
      place-content: center;
      min-height: 100vh;
    }
    

    CSS 🎨:

    • Adding a CSS Reset is good practice to remove all default styles in the browser

    • You don't need to add font-size:16px; on the <body> because that is the default font size

    • When you add min-height:100vh; your component be placed in the center of the website.

    • Be sure to use rem on other CSS properties like margin and padding because it better for accessibility.

    Here is my solution to this challenge Blog preview card

    Hope you find it useful and don't hesitate to reach out to me if you have questions

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