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

Blog preview card

Arekpok29•50
@Arekpok29
A solution to the Blog preview card challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Aakash Verma•9,500
    @skyv26
    Posted 5 months ago

    Hi @Arekpok29,

    Here are some suggestions for your code to improve it:

    1. Remove commented code: There’s some commented-out code in your repo (lines 19-32 in index.html) that should be removed for cleaner and more maintainable code. You can check it here: GitHub link. ✅

    2. Use place-content instead of place-items: place-content will help you position the card in the center. Both properties have different use cases, so using place-content in this case is more appropriate for centering. 🎯

      Example:

      body {
          font-family: "Figtree", serif;
          background-color: hsl(47, 88%, 63%);
          height: 100svh;
          display: grid;
          place-content: center;
      }
      
    3. Use max-width instead of width for responsiveness: When defining the card's size, max-width ensures that it adapts to different screen sizes, while width would keep it fixed. 📱

      Example:

      .card {
          background-color: white;
          border-radius: 1rem;
          max-width: 22rem;  /* Instead of width */
          box-shadow: 0.5rem 0.5rem 0 black;
          border: 1px solid black;
      }
      
    4. Make image width 100%: To ensure the image adapts properly to the card's size, simply set its width to 100%. 🎨

      Example:

      .card .top-image {
          display: flex;
          justify-self: center;
          max-width: 100%;
          margin: 1rem;
          border-radius: 1rem;
      }
      
    5. Consolidate margins and paddings: Instead of adding margin to the text inside the card, just add padding to the card itself. This keeps your layout clean and consistent. 💡

      Example:

      .card {
          padding: 1rem;  /* Add padding here */
      }
      
      .card .card-content {
          display: flex;
          flex-direction: column;
          align-items: flex-start;
          gap: 0.5rem;
      }
      

    These small adjustments will improve the readability, maintainability, and responsiveness of your code. Keep up the good work! 👍

    Let me know if you have any questions. 😊

    Marked as helpful
  • coyoteshkw•150
    @coyoteshkw
    Posted 5 months ago

    no responsive on 375px, and not so pixel perfect.

    published time is not that bold

    I usually use some div wrapper on img or tag, maybe use them can control element better.

    Actually it feels good, bro

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub