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

Exact copy of the design using HTML/CSS

tomblack9452•60
@tomblack9452
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?

This is my version of the "Blog Preview Card" challenge by Frontend Mentor. I feel that I recreated this exactly and used very efficient and accurate HTML/CSS.

I'm proud of finding the solution to an easy drop shadow behind the card using the filter: drop-shadow option in the css file.

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

Lining up the profile icon with the name, still not sure how I managed to do it properly and it still isn't exactly centred.

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

Help with the best way to line-up the profile icon with the name.

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Boris•4,110
    @makogeboris
    Posted 10 months ago

    You can align the icon with name using flexbox like so

    html

    <div class="profile-icon">
        <img src="images/image-avatar.webp" alt="Greg Hooper Profile Icon" style="width: 32px; height: 32px;">
        <span class="profile-text">Greg Hooper</span>
    </div>
    

    css

    .profile-icon{
        display: flex;
        align-items: center;
        gap: 0.75rem;
    }
    
    Marked as helpful
  • Teodor Jenkler•4,040
    @TedJenkler
    Posted 10 months ago

    Hi @tomblack9452,

    Nice project! Here are a couple of suggestions for improvement:

    ARIA Labels and Semantic HTML: Consider adding aria-label attributes to <div> elements to enhance accessibility for screen readers. This practice will help with both accessibility and SEO. Alternatively, when appropriate, use semantic HTML elements like <section>, <article>, or <header> to provide more meaningful structure to your content.

    CSS Resets and Box-Sizing: To ensure consistent styling across different projects, it's a good idea to reset margins on the <html> and <body> elements. Additionally, using * { box-sizing: border-box; } will help maintain consistent box-sizing across your site, making layout and styling more predictable.

    Hope these suggestions help!

    Best, Teodor

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