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

Recipe Page using HTML and CSS

ILLORYS•10
@ILLORYS
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 could complete this challange as a newbie. I would do nothing differently. I searched and found everything i needed(except one thing). I would be more patient with myself :)

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

I realized that sometimes eventhough i write the right code the website doesnt show it and it confused me a lot of times. I had to wait or write it again and refresh. I also searched for communities and joined them. Unfortunately they werent a big a help because they are either too big to notice me or just a dead community or ignoring me i dont know :D I genuinely wanted to ask for help but i could solve it at the end with a little bit more time invested.

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

I have a problem with responsive web design. The challange asked me to do 375px for mobile and 1440px to desktop. I found a code which could work but it doesnt seem right when i checked it through google with the f12 device tool. Since it was my only problem i let it be but it still bothers me what did i wrong or how should i check correctly the size of the website.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • ILLORYS•10
    @ILLORYS
    Posted 8 months ago

    Update #2

    Now i only have 2 problems.

    Error:

    I only got 1 error message after i uploaded my correction related to the previous things:

    Bad value "recipe-page-main\assets\images\image-omelette.jpeg" for attribute "src" on element "img": Backslash ("") used as path segment delimiter.

    <img src="recipe-page-main\assets\images\image-omelette.jpeg" alt="Picture of an omlette" style="width: 100%">

    Still dont know what is this im trying to figure out.

    Responsiveness:

    And the other one is still about responsiveness. I guess i have to use next time vh and other measurements instead of pixel. Maybe the problem starts here but this is only a guess. The website still collapses on mobile and looking "okay" on everything else. I really want to solve this because its bothers me sooooo much :"D

  • ILLORYS•10
    @ILLORYS
    Posted 8 months ago

    Im giving an update to my solution: After i got the warnings and errors from the websites report system i learned new things such as:

    Headings:

    • headings should always come in order one after another. I did a mistake and wrote after h1 a h3 heading and you should do h1, h2, h3 in order!! i give a link to confirm that 'Headings are important' section gives the correct answer: https://www.w3schools.com/html/html_headings.asp

    Lists:

    • unfortunately i put my hr tag IN the lists code and it should be outside of it because lists should only contain list contain elements. Source: https://dequeuniversity.com/rules/axe/4.6/list?application=axeAPI

    Page landmarks:

    • it was very new for me that i should structure my website like this - pay attention to the header,nav, main, footer section in the code -: https://dequeuniversity.com/rules/axe/4.6/region?application=axeAPI

    About other landmarks: i dont understand this error but it says: Document should have one main landmark

    <html lang="en">-------- i have this in my code so what does it mean? :D

    Comments:

    • i was a bit too excited to use them and i got an error:

    The document is not mappable to XML 1.0 due to two consecutive hyphens in a comment.

    E--> <!-------------------

    Aaaand the last one:

    Bad value "recipe-page-main\assets\images\image-omelette.jpeg" for attribute "src" on element "img": Backslash ("") used as path segment delimiter. G"> <img src="recipe-page-main\assets\images\image-omelette.jpeg" alt="Picture of an omlette" style="width: 100%">

    I dont know what to do with this one. The image is working and everything. Maybe somebody can help me to figure out what should i do differently because i have no idea.

    Thank you if you read this all through!

    I wish everybody happy coding and dont give up if something doesnt work out the way you wanted. If you are stuck on a problem for too long just move on you probably spent too much time on it and it wont help if you whip yourself to madness. :D

    Give yourself time to process the problems!

    Take care!

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