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

Blog card using HTML & CSS

Justina-R•20
@Justina-R
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’m most proud of my progress and how I’ve effectively utilized resources. Next time, I’ll focus on continuous improvement to keep growing even more.

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

I wanted to try different methods for adding fonts and creating a more responsive design without relying heavily on media queries. It was challenging since I didn’t have much knowledge in that area, but with some research, I was able to solve it.

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

As I mentioned in other challenges, my biggest concern is with responsive design and whether I’m applying it correctly. I’d appreciate help in that area.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Illia Liashko•70
    @Illia-L
    Posted 10 months ago

    Well done!

    Seems, like everything is ok with fonts and colors.

    The ways to improve:

    • check component behavior in different screen sizes, I noticed some issues;
    • consider using meaningfull html tags for headers and paragraphs instead of <div>, remember, some people use assistive technologies to read web sites.
    Marked as helpful
  • Derik Boghozian•230
    @psychederik
    Posted 10 months ago

    The design looks great but there are a few issues on the live site. First, the size is changing for every stretch of the window size and second, there are no hover effects. I like your code, it is well structured and easy to read. I think it will be best for you to learn how to make the size remain consistent with window size and also add the hover effects (check Figma files and hit the play button on top right to view the functional prototype).

    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