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

I used css style components to complete this task.

Poovarasan G•20
@Poovarasang123
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 coded this project in my own thinking and it helps me to understand the problem very clearly and I resolve many errors and bugs by myself. The most interesting part is to apply style to the project using css. Also I learnt how to create a live link for my website by creating github repository and make it live.

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

The challenges I encountered is to apply responsive design to overcome that I have watched youtube tutorial videos and studied websites like geeks for geeks take to resolve the problem.

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

I want to know where I need to use grid , flex boxes to effectively build websites. Also I need a road map to be a frontend developer.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Gurbala Laurent•110
    @laurentGurbala
    Posted 9 months ago

    Great job on your work!

    I noticed that you used an HTML table for the nutrition section. I would recommend trying CSS Grid instead. It will not only make it simpler to arrange the elements, but you’ll also have more control over the placement of the different cells. This way, you can achieve a better layout and make it more responsive and visually appealing.

    Regarding your question about when to use Flexbox or CSS Grid, here’s a little tip:

    If you have a layout that works on one dimension (either horizontally or vertically), Flexbox is usually the best choice. On the other hand, if you're working on a layout with two dimensions (both columns and rows), as you might have guessed, CSS Grid is the way to go!

    I hope these tips help, and once again, great job on what you've achieved so far!

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
Frontend Mentor logo

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