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

Simple main with the use of font-variant-numeric for the

sass/scss
P
Claudia•300
@cla91
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'm most proud of successfully tackling the styling of the ordered list numbers to perfectly match the design. It was a small but impactful detail that required some specific research into CSS properties like font-variant-numeric: normal;, and getting it just right felt very rewarding. It's often these seemingly minor details that make a design truly shine.

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

My main challenge, as mentioned, was getting the ordered list item numbers to display correctly. Initially, they weren't rendering with the exact style or weight depicted in the design preview.

I overcame this by systematically debugging and researching CSS font properties. I experimented with font-weight, font-size, and then delved into more specific typographic controls. This led me to discover font-variant-numeric: normal;, which ultimately resolved the issue by resetting any default browser or inherited styles that were subtly altering the number's appearance. It was a good reminder to sometimes look beyond the most obvious properties.

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

Currently, I'm quite satisfied with the project's outcome given the scope of the challenge. However, if I were to seek help or feedback, it would be around optimizing the SASS structure for larger projects. I'd be interested in best practices for organizing partials and variable files in a way that scales efficiently for more complex UIs, as well as strategies for managing global styles versus component-specific styles.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Abdul Subhan•1,580
    @Esabdul
    Posted about 1 month ago

    Hi Claudia,

    Just a few small things I noticed that could make your code even better.

    First, the inline styles you’ve added in the <head> for the .attribution class could be moved into your external CSS file. Keeping all your styles in one place helps with long-term maintenance and makes the HTML cleaner.

    I also noticed the <table> tag in the nutrition section is missing its closing tag, and the same goes for the closing </section> tag around it.

    While the browser might still render things correctly, it is good practice to make sure everything is properly closed to avoid unexpected behavior.

    Another small thing, the img tag uses width="100%" and height="auto" directly in the HTML.

    That works, but shifting those to your stylesheet would keep the structure and styling separated, which is more maintainable.

    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