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

Preview Card with hover

P
Catalina Sabogal•30
@csabogalortiz
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?

This project is a fast-win development prototype designed to explore Figma's Dev Mode and understand the transition from design to development.

It serves as a learning experience for front-end developers and designers who want to improve their workflow using Figma's Dev Mode.

This component serves as the base structure for a reusable card element in the project. It is designed to be flexible and customizable while maintaining consistency across the U

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Yacoub AlDweik•3,590
    @YacoubDweik
    Posted 6 months ago

    Wow!

    You don't know how much difference this makes when you change the design and add your own creativity, this makes you different!

    Everything is fine, except the overflow of your design in mobiles, this is because 3 things:

    First point, in the section try always to add max-width instead of width, think about small screens like mobiles, setting the width to be always 385px makes the design overflows on >385px screens, max-width will solve that!

    Second point, in the section flex-shrink: 0 makes the design take the max-content width, no flexibility, you do not need that!

    Third point, always give max-width: 100% to any img, when you put the img in your design it keeps its dimensions, the 1000px stays 1000px, so you need a way to force it to grow and shrink according to its parent div, max-width: 100% solves that!

    Keep it up!

  • Patrick Segarel•140
    @psegarel
    Posted 6 months ago

    Everything seems fine except that the Solution/Design screenshots belong to different projects. Not sure why that is, so I can't really comment further.

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