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

Recipe Page - HTML, CSS And Flexbox

P
Jan•290
@Jan-Dev0
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?

The challenge was mostly basic stuff. The only thing to mention here is the customized lists styling and the use of CSS counters.

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

I’d just like some tips on best practices or things to avoid. Any advice on common mistakes and how to do things the right way would be awesome!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Steven Stroud•11,890
    @Stroudy
    Posted 11 months ago

    Hey Great job with this challenge, Nothing wrong but some things to consider,

    • Having better alt="" descriptions for accessibility is a must check this out Write helpful Alt Text to describe images,
    • Should take a look at BEM naming convention for class names, Its really useful and practical,
    • You have used <div> under instructions for your paragraphs, you should wrap them in <p> to make them semantically correct,
    • You should apply a full modern reset to make things easier as you build, check out this site for a Full modern reset
    • In your <atricle> you have set a width in px and your @media, Check out this article from a Frontend mentor dev about responsive-meaning.
    • Using max-width: 100% or min-width: 100% is way more responsive than just width:100%,
    • It would not be a bad idea to download the fonts in .woff2 format, Host it your self using a @font-face and add a font-display: swap; property, To leverage the font-display CSS feature to ensure that text is user-visible while web fonts are loading, Increasing performance.

    Happy coding, will be good to see some more from you.

    Marked as helpful
  • Teodor Jenkler•4,040
    @TedJenkler
    Posted 11 months ago

    Nice job, keep going!

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