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

Responsive Recipe Page using CSS media queries

resegoreey•30
@resegoreey
A solution to the Recipe page 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 proud of how I was able to know which tags and elements to use on my HTML file and the styles I could implement on my own in my CSS stylesheet.

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

I had troubles with getting the image to fit into the container and also making it adjust to the small screen sizes. I also troubles with making the oage responsive using media queries. I overcame this by watching short clips and using w3schools website to look for similar examples.

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

Fonts. I don't know how to use the fonts given in the starter pack. Even though I tried looking for many examples, I couldn't use the fonts.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Andrey•4,400
    @dar-ju
    Posted about 2 months ago

    Hello!

    The most correct way is to use woff and woff2 font formats. The first one is for old browsers, the second one is for modern ones. It is better not to use ttf in the project, there is a lot of unnecessary information, which is why it weighs more than woff2.

    Download ttf from google fonts, convert it. Use any font converter, for example this one Put the woff and woff2 files in the fonts folder.

    Connect them at the very top of the css file (specify the correct path):

    @font-face {
      font-family: "BeVietnamPro";
      src: local("BeVietnamPro"),
      url("../assets/fonts/Outfit-Regular.woff2") format("woff2"),
      url("../assets/fonts/Outfit-Regular.woff") format("woff");
      font-weight: 400;
      font-style: normal;
      font-display: swap;
    }
    

    (use a separate @font-face for each font-weight)

    And assign the font to the project in the body tag - font-family: "BeVietnamPro", sans-serif;

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