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

Webpage about a perfume made by HTML and CSS

deezjason•20
@deezjason
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?

I am very proud that I was able to do this and get almost everything correctly(except for the font)

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

My work got deleted unfortunately🥲 but I was able to bounce back and redesign it to be better than before

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

Mostly on how to change the font into the fonts that you get from Google fonts, its the only thing that I struggled with

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Jenna•230
    @NandiniCooppen
    Posted about 1 year ago

    Hi there,

    Congratulations on completing this challenge. 👏

    Regarding the Google fonts, to use them, first of all, you need to look up and select both from the Google Fonts site

    There is an icon at the top right, indicating, how many fonts you have got, select all fonts you need before clicking the embed code button.

    You will have something similar to

    "@import url('https://fonts.googleapis.com/css2?family=Fraunces:ital,opsz,wght@0,9..144,100..900;1,9..144,100..900&family=Montserrat:ital,wght@0,100..900;1,100..900&display=swap');"
    

    Copy it into your CSS file, at the start.

    You will be able to use the fonts where needed.

    Example:

    body {
      font-family: "Montserrat", sans-serif;
    }
    
    h2 {
      font-family: "Fraunces", serif;
    }
    
    

    If I may suggest some improvements :

    1. Semantic structure

    Use the semantic HTML5 in your structure. To improve the document structure and in return improve its accessibility, consider using <header>, <main>, <article>, and <footer> elements where applicable.

    Read more about semantics here

    Read more about accessibility here

    Read more about headings here

    2. Centring elements using CSS grid or Flexbox

    To centre the design both horizontally and vertically, you can use CSS flexbox as follows on the body.

    body {
    display: flex;
    justify-content: center;
    align-items: center;
    min-height: 100vh;
    }
    

    or grid

    display: grid;
    place-items: center;
    min-height: 100vh;
    

    3. Always do a reset for your CSS

    * {
      margin: 0;
      padding: 0;
      box-sizing: border-box;
    }
    

    4. Using CSS variables

    Try using CSS variables on your next challenge.

    Read more about CSS custom properties here

    For reference, you may check my submission here

    Do not hesitate, if you have any questions.

    I hope these will be helpful to you 😉

    Good luck onwards and happy coding 🙂

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