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

Blog preview card HTML CSS

drelu•150
@dreelu
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 to build the site with a good acuracy, but ill probabily learn and use flexbox in the next time. Every solution to my problems that i find in other peoples code is using flexbox, so of course this will take me to another coding level.

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

Centralize the card on the center. I have a lot of difficult doing this and all the solutions that i found is using flexbox, that i dont know use. I overcome using margin auto and adding a margin on top to give a free space, like on the solution.

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

Make a responsive site.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Mdhenderson14•100
    @Mdhenderson14
    Posted 6 months ago

    Hi there, nice preview card you've created!

    I would like to mention, without comparing yours to the original, that the spacing between the words of your description isn't ideal from a user perspective. Because your text takes up about 80% of the card container, I assume the text is also in a container, which may not be necessary.

    For my own description I used the following: font-size: 1 rem; text-align: left; color: var(--color2);

    Without a container, all other styling for my publish date, title, and description came from the styling of the parent card container.

    I hope this is 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