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

Blog page using flexbox and a media query.

Lyle Patterson•60
@Squing0
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?

The overall responsiveness at smaller sizes.

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

Again, mainly making the container respond to smaller sizes here. Getting the container to work in a desktop view didn't take long.

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

The challenge said it was possible to make text smaller without using media queries but I was unable to do this. I also had a lot of trouble scaling the image down and I'm not sure if the way I've done it is good practice. I also noticed that in the mobile design that the challenge gave that the image appears to be zoomed in but I was unable to achieve this effect. I also only used hover and not focus as the challenge listed as it was unclear where to use this.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Bernardo Poggioni•6,990
    @R3ygoski
    Posted about 1 year ago

    Hello again Lyle. First of all, I'd like to say congratulations! Your project looks almost similar to the proposed design, which is great.

    Let me start by addressing your question. To create a small text without using @media, you can use clamp(). This way, you can define a minimum, base, and maximum size for your text.

    The method you used to resize the image doesn't seem wrong, but instead of using max-width, you could use width: 100%. This is because if the user happens to be using a larger font size, it may cause the image to appear small. To test this, try increasing your browser's font size, and then change max-width to width: 100%.

    Regarding the ::hover, you used it correctly; it was meant to be used on the card and the title. And a tip, the title should have a cursor: pointer; because it's clickable.

    About the image zoom, you can add an overflow: hidden to your figure, and on your image, add transform: scale(105%), then just add the border-radius to the figure.

    Once again, congratulations! If you have any questions or if any doubts arise, please ask below, and I'll try to help.

  • Kerwin•80
    @KerwinAngeles
    Posted about 1 year ago

    You need add more padding inside the card, after that look great

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