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

Basic Blog Preview Card using simple HTML5 and CSS.

BozJR•260
@BozJR
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?

Most proud that I didn't need much help with this one (maybe cause its similar to the first project) but feel like I am slowly starting to get the hang of CSS and HTML. Just need to practise practise and more practise.

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

My only real challange was trying to get the profile picture and the profile picture name at the bottom of the card to sit side by side.

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

Just need some hints and tips on how to get two different elements to sit side by side.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sarah•580
    @AutumnsCode
    Posted 11 months ago

    Hello,

    well done for completing this challenge.

    I am happy to provide to give you some feedback:

    • the h1 element should be the first heading in your page. I would suggest to use a paragraph element with a class instead to style the element.
    • the next paragrapgh should have a class since its the text below your h1-element is actually the main text of the challenge.
    • I really enjoy that you include a hover effect on your h1-element. To made it even better, it would be great if you could wrap inside a anchor-element.
    • The profile image is too large. Inside your css, you could add a width to reduce it.
    • Almost every html-element has default styling. It can be really difficult to deal with them while styling like img. If I see an image in one of my project, I am always add reset to take away the default one. Here is the one for image, picture
    img, picture {
     max-width: 100%;
    display: block
    }
    

    I hope those tips and tricks will be helpful Best regards Sarah

    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
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 1st-party linked stylesheets, and styles within <style> tags.

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.

Oops! 😬

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

Log in with GitHub