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

I used HTML for structuring the website and after that used CSS

accessibility
Zeeshan-Haider0•10
@Zeeshan-Haider0
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?

This was my third day into the web development and I tried my best and put the knowledge to use as far as I could. Hopefully I will learn more and master my skills and get better. I tried my skills just to practise the knowledge that i have about html and css so far This was a pretty good experience But im not proud of what I made :(

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

As a complete beginner it was tough and I did everything on my own

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

As new to webdevelopment I didnt new how to customize that preperation time box and the nutrition table so i would definetely hope someone could help me there

Code
Couldn’t fetch repository

Please log in to post a comment

Log in with GitHub

Community feedback

  • Junier Bolívar 🕷•710
    @Junbol
    Posted about 1 year ago

    ok first do that first. You can if you want create a totally new repository in GitHub and call it: recipe-page-main

    then add that remote to your local repository: git remote add origin <url of your GitHub remote repository which it will have the name: recipe-page-main> To do all this read the README.md file:

    Building your project

    Feel free to use any workflow that you feel comfortable with. Below is a suggested process, but do not feel like you need to follow these steps:

    1. Initialize your project as a public repository on GitHub. Creating a repo will make it easier to share your code with the community if you need help. If you're not sure how to do this, have a read-through of this Try Git resource.
    2. Configure your repository to publish your code to a web address. This will also be useful if you need some help during a challenge as you can share the URL for your project with your repo URL. There are a number of ways to do this, and we provide some recommendations below.
    3. Look through the designs to start planning out how you'll tackle the project. This step is crucial to help you think ahead for CSS classes to create reusable styles.
    4. Before adding any styles, structure your content with HTML. Writing your HTML first can help focus your attention on creating well-structured content.
    5. Write out the base styles for your project, including general content styles, such as font-family and font-size.
    6. Start adding styles to the top of the page and work down. Only move on to the next section once you're happy you've completed the area you're working on.
    Marked as helpful
  • Ranti ogunrinde•210
    @Ranty09
    Posted about 1 year ago

    Hello Zeeshan. Kudos for taking a bold step. In addition, I want to advise you to always ensure that the file path in your code matches the actual file path in your repository to make your image visible. I also want to encourage you to use table element and table row in the "Nutrition" segment.

    Marked as helpful
  • Junier Bolívar 🕷•710
    @Junbol
    Posted about 1 year ago

    Hi Zeeshan, I think I might guess what is going on. My tip for you for now is to delete the repository you have now and create a new one but this time make recipe-page-main the repository and not nested inside another parent repository like it is now.

    Cheers

    Junier

    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
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

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