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

Blog Preview Card

sass/scss, vite, bem
Dylan de Bruijn•3,220
@DylandeBruijn
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?

Everything went pretty well. I would appreciate feedback on general code structure and accessibility. Also I tried to make the font-size responsive without media-queries using clamp(). However the title scales down sooner than the rest of the elements. Is there another way to achieve this? I tried container queries and cqw units but that didn't work. Would be much appreciated if someone could point me in the right direction!

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

Making the font-size responsive without the use of media queries.

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

General code structure, semantics, accessibility and making the font-size responsive without the use of media queries.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • trskldnt•80
    @trskldnt
    Posted about 1 year ago

    I reviewed your work, and I really liked what you’ve done! The code structure is clean, and you’ve clearly put a lot of effort into making your project accessible and well-organized. Unfortunately, I don't have a solution for the issue with making the font-size responsive without the use of media queries. I understand how challenging it can be to achieve the desired responsiveness, and I hope you find a good solution soon. Keep up the great work!

    Marked as helpful
  • P
    MikDra1•7,450
    @MikDra1
    Posted 11 months ago

    If you want to make your font-size responsive without using media queries I encourage you to learn about the clamp() method

    Hope you found this comment helpful 💗💗💗

    Good job and keep going 😁😊😉

  • AReactDeveloper•340
    @AReactDeveloper
    Posted about 1 year ago

    very clean I'm impressed what did you use to get the design in such pixel perfect accuracy ?

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

Oops! 😬

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

Log in with GitHub