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

Blog Preview Card

Colt•100
@Xerver8694
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?

Fiddling with the CSS is both rewarding and frustrating. I'm still struggling with it, but looking at how other people have managed to style the project has helped me gain more of a grasp of the fundamentals of styling HTML elements.

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

I am still struggling with the styling aspects of web page design. CSS Flexbox is a bit finicky, and I am having trouble grasping the concepts of centering and spacing things with Grid or Flexbox.

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

I need the most help with the styling aspects of this project. The CSS Flexbox model is still something that I have difficulty working with.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Natali 👻 Grimm•1,190
    @Grimm-N
    Posted 10 months ago

    Awesome work—you’re really putting in the effort, and it shows! 🌟 Keep going; you’re doing great!

    Here are a few tips to polish your code even further:

    1. Only use one <main> element per page. Having more than one <main> can confuse screen readers and make it harder for assistive technologies to understand the main content of your page.

    2. Add classes to all elements—it keeps your code flexible and easy to style later on. Giving each element a unique class name helps you target and style each part of your layout precisely, especially as your project grows.

    3. Try using rem, em, %, or vh units instead of pixels. These units adjust to different screen sizes, which makes your design more responsive and user-friendly.

    4. To center your card within the body, try using flexbox:

      body {
        display: flex;
        justify-content: center; /* centers horizontally */
        align-items: center; /* centers vertically */
        height: 100vh;
        width: 100vw;
      }
      

      This centers the card both vertically and horizontally within the body container.

    5. To prevent the card from sticking to the edges on smaller screens, try setting the card width to 90vw or 90%:

      .card {
        width: 90vw; /* or 90% */
      }
      

      This gives the card a little breathing room from the edges, making it look balanced at all screen sizes.

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

    Hey there! You're doing a great job- keep coding! I'm new as well, but I have one small pointer. I found using display: inline-block;

    for the learning tag keeps it from spreading the full length of my card.

    Good luck and hope to swap code answers soon!

    Marked as helpful
  • Abdulsalm Taiwo•120
    @Symplyteeziy
    Posted 10 months ago

    I think you should improve drastically in using width and border. The padding on both side is not that okay.

    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

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

Oops! 😬

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

Log in with GitHub