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

Recipe page using HTML tags and containers

WajahatAli130•90
@WajahatAli130
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 got the site looking pretty similar to the example, even though there are some small details missing.

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

At first I was feeling so lazy and unmotivated to start because of all the code that I would have to write for this. So many tags and containers! At one point I got really frustrated with the code because it looked so confusing but then I created a new HTML file and build everything from scratch and that helped me complete this challenge.

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

How do I add lines between the rows of the table? And how do I get rid of the white border around the beige background?

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • m1st1nh0•70
    @m1st1nh0
    Posted 9 months ago

    hey there, i just finished my omelette too, to add the bottom borderlines for your table u have to : table{ border-collapse: collapse; (command to make the borders of the table unique, so they have no breaks at the crosses) }

    than:

    td, th{ border-bottom{ 1px solid (and the color u want) } this command define the width, the type of filling and the color.

    sorry for the bad english typing, hope i could help

    Marked as helpful
  • Ayorinde Maryam Oluwatoyin•380
    @MARYAMTEE
    Posted 9 months ago

    Ensure the design is viewed at 100% for accurate sizing! It's a crucial step for precision. Just double-check your screen resolution and zoom settings to avoid any scaling issues. Keep it up!

    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