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

Blog Card with responsive font-size (no media queries) & a small twist

nicowashere•250
@devdrivenai
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?

Initially, it didn't look like a lot, but taking with a serious approach, I found a lot of learning from this. Also, remaining accountable and showing up is good stuff.

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

First I didn't even know it was possible to host your own fonts. Then, as well, I learned about the advantages of using variable fonts (hosting them yourself!). From both of these things I research, tested and learned a lot. But mostly the proposal of the challenge to make font size responsive without media queries was great. There I had some interesting learning. Had to research quite a bit. Left some resources in the README. Also, I added a small supplementary twist (don't want to spoil it here), and in doing so, I also had a nice opportunity for learning.

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

I know I have to be as specific as possible here. The thing is I spent quite some time researching and testing to build this one, so I don't have a lot of specific doubts. However, what I would appreciate, and especially so if you have more experience, is if you find anything (yeah, anything!) that I could work on and do some research and testing to get better at, or even things that I might have completely ignored, completely oblivious, that you could briefly point them out to me. Will be a lot of help and takes just a minute. Thank you!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Dias•140
    @adambeckercodes
    Posted 9 months ago

    Hey there! 👋

    Great job on your design—it looks clean and visually appealing! 😊 However, I noticed that the content shrinks below typical mobile screen sizes, which can make it harder to read or interact with on smaller devices.

    To fix this, I recommend setting a min-width property for the container or the body. This ensures that the content won’t shrink below a specific width, maintaining usability even on very narrow screens. For example:

    css body { min-width: 320px; /* Adjust as needed */ }

    Hope it will be useful!

  • Victor Barrio•330
    @Victor-Barrio
    Posted 9 months ago

    You nailded it! And it so gratefull that you learning and testing new things!

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