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

Blog Preview Card using HTML/CSS

timdogan0•30
@timdogan0
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?

I am most proud of the fact that I was able to solve problems using online resources.

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

I had trouble centering certain stuff, however, I managed to fix them.

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

Feedback on accessibility, and best practices.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dylan de Bruijn•3,220
    @DylandeBruijn
    Posted about 1 year ago

    Hiya @timdogan0,

    Great job on a good looking solution to this project! Happy to hear that you were able to solve your problems using online resources. Being good at problem solving and finding the information you are looking for is a good skill to have in your arsenal.

    A bit of friendly constructive feedback:

    • I suggest changing the height: 100vh; on your body tag to min-height: 100vh. The reason why is when your content grows vertically in the body you'll run into overflow issues when the height is more than 100vh. By setting a min-height the body is still able to grow beyond 100vh but 100vh at a minimum. You can check this by giving your card text a lot of characters.

    • Try adding some padding to your body this makes sure your card has some space between the viewport edges and itself on smaller viewports.

    • You could try using CSS variables to make your code more reusable.

    • You have a double declaration for the max-width of the image. One is coming from the reset and one from the image class. You can remove the one set on the image itself. You also don't need flex on the image. So your new styling would be:

    .card-image {
        /* display: flex; */
        /* justify-content: center; */
        border-radius: 10px;
        /* max-width: 100%; */
        margin-bottom: 1.5rem;
    }
    

    The commented out lines are the ones you can remove.

    I hope you find my feedback helpful and I would appreciate it if you could mark it as helpful if it did!

    Happy coding!

    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