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

Blog Preview Card simple solution

ShadowCoder040•70
@ShadowCoder040
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 happy that I got more comfortable with CSS and finding the correct solutions to position each element correctly, almost on the first try.

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

As usual the media queries are still a bit of mystery to me, but the more I practice the better I understand.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Sven Notermans•220
    @Sven-27
    Posted 7 months ago

    Hi,

    First of all it looks good wath you did. Couple suggestions i have.

    IN your html you use mainly div. Try to use semantic elements as much as possible. Div is used when no other element is suited. Like <div class="footer"> You can do <footer> instead.So it is a good thing to learn more about them. Otherwise it looks good.

    CSS: I see that you have imported the fonts directly. Since they are already in de asset folder it proberly was the meaning to use them instead of importing.Look at 'font face' to use local fonts in your project. The use of variables is perfect.

    You didn't make the fonts responsive. Try to google how to make the fonts responsive without media query. That was part of the assignment. Try to structure your CSS the same as your html. I will give you my github link so you can see what i mean.

    Take a look at your hover on the h2. It does not turn yellow.

    Hope you can use this feedback and if you have questions you can always ask me either here or on discord.

    My github is https://github.com/Sven-27/blog-preview-card

    Regards Sven

    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 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