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

Responsive Blog Preview Card using Flexbox

Linda Jensen•80
@lindajensen
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?

My second Frontend Mentor Challenge and I'm really proud of the fact that I found a solution to the whole cursor:hover dilemma. I'm not sure using an image was the correct way to go, but it did solve the problem.

If I could do it all over again I would probably try a mobile-first approach. I really need to practice that and a lot of people says that's the way to go. I'm just really new to this whole coding thing and I'm not really sure how to go about it. Like do I just make my screen smaller and start from there?

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

One challenge I encountered was how to make the pointer change when I hovered over the link. I Googled forever and couldn't find a way to change the color of the pointer. So after quite some time I decided to use an image as a pointer. I hadn't done that before but it wasn't all that difficult.

Another challenge I encountered was the font-sizes. In the description it said "The font sizes in this project a slightly smaller in the mobile layout. Find a way to reduce font size for smaller screens without using media queries." I decided to use rem, but I'm not sure that's a solution to the problem. I tried using the calc() function, but I couldn't get it right.

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

Questions

  1. Is using an image as a pointer the "correct" solution to the problem? Are there other ways of solving it? Like is it possible to change the color of the pointer?
  2. Is using rems or ems one way to make the font-size smaller on smaller screens? Is that how they work? Or is there another solution?
  3. How do you design for mobile-first? Like practically? Do you just make your screen the size of a mobile screen and start coding or is there another, better way of going about it?
Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Linda Jensen's solution.

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.