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

HTML,CSS,and text editor VSCODE

Rafi Rachmawan•210
@rafirachmawan
A solution to the Product preview card component 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?

learn more about responsive and improve my knowledge in the frontend field

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

the challenges I face are a little more difficult on the layout of text images and responsiveness

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

in terms of distance and layout because I didn't get the figma design

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Karen Robertson•190
    @indigorose
    Posted 10 months ago

    This is a really nice solution to this challenge.

    The HTML is easy to read, however for the next challenge try to extend your use of semantics, such <main> or <section> rather than <div>.

    It helps us to see the flow of the page better and improve accessibility.

    Most use the cheat sheet from the Mozilla MDN site MDN Web Docs Cheat Sheet.

    For the text responsiveness, the clamp() css function has been helpful with sizing responsive text MDN description.

    There is also letter-spacing and line-height in css that will also help with the text design requirements.

    Even without the Figma files, the site is still impressive and meets the responsive requirements.

    Hope to see your other solutions soon.

    Marked as helpful
  • P
    Jose•160
    @josenegrete123
    Posted 10 months ago

    Great work! For your @media section of the CSS, you don't need to change the font-size around because per the figma documents, they are all the same font-size, from mobile-version to desktop. Also the h1 and the first span should be in a different font. But that was given in the style-guide. The line-height in the h1 could also be change to 0.

    Marked as helpful

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