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

Responsive Recipe Page utilizing both `px` and `rem units

P
finkusuma-dev•130
@finkusuma-dev
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 implements both px and rem unit. px is used for horizontal margin and padding and other properties that don't need to scale with the default font size.

rem is used for font-size, vertical margin and padding and also horizontal spacing that has direct relation with text, such as spacing between bullet and list item text, horizontal spacing in the th and td.

When I tested it by increasing the default font-size to more than 40px, it showed the increased size of certain element properties as expected.

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

I faced some number of challenges:

  • How to stretch the marker to the list item height. To solve this I create a custom bullet by using ::before pseudo-element and centering it vertically using flexbox.
  • How to set the horizontal spacing of the marker. To handle this, first I align the marker with any text above the list. Then set the spacing according to Figma.
  • There are four divs in the page and three of those have the same class. The challenge: even if they have the same class, each of them has different border sides in the vertical direction. I resolved this by utilizing :nth-of-type() pseudo-class.
What specific areas of your project would you like help with?

I got feedback from Grace Snow for not using sections for this challenge as they don't add benefit. Each of block already has headings that can be used as accessibility navigation. But I still don't understand in which cases the sections are necessary. So if anyone already has clear understanding about this please let me know!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Ruan Costa Oliveira•60
    @umenorin
    Posted 7 months ago

    the only thing that would change is the color you forgot to change in the titles, other than that it's perfect, good job

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