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

html, css, table, lists

P
Paul Wonka•260
@pdoubleu30
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 proud that I'm continuing to grow, and able to overcome obstacles faster with each project. Next time, I would try to problem solve a bit more by experimenting before researching solutions online.

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

I had a challenge setting my table up with the borders and getting the borders to position correctly.

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

I am open to any suggestions. I would like my code to be simpler and more efficient. Thank you.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Glen•140
    @grgallosa
    Posted 4 months ago

    it look like as reference but maybe too small and not reponsive for smaller screen and also Remove duplicate Google Fonts links to avoid unnecessary HTTP requests. but overall it looks great.

    Marked as helpful
  • Devesh Soni•100
    @DeveshSoni973
    Posted 4 months ago

    the code broke in mobile view, if you don't know, put the max and min dimensions and maybe use more percentages. But I really love how the ui is all perfect to the last colors :))

    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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub