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

Responsive recipe page built with html and css

Gift Amachree•870
@jen67
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Hi everyone,

I just finished this coding challenge, and I'm excited to hear your thoughts and suggestions! 🚀

Thanks in advance for your input!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Awais Ahmad•20
    @awaisahmad64
    Posted over 1 year ago

    you completed an awesome pixel-perfect design.

  • Ibrahim Mohammed•640
    @MohammedOnGit
    Posted 9 months ago

    Hello Gift Amachree!

    Congratulations on completing the challenge. You did awesome! However, looking at your "Design Comparison" solution, I presume you completed the project using your best judgment.

    I recommend Pixel Perfect Pro for you. It is a Chrome extension that allows you to upload the Frontend Mentor's design pictures directly onto your browser. This will aid you in comparing your design with the project design specifications while you code. With this tool, you are likely to create a nearly perfect solution, if not pixel-perfect, in the future.

    You can search for the tool or use the link below to download it.

    Happy coding!

    NB: I am not sponsored by the developers of the tool in any way.

  • Sivaprasath•2,500
    @sivaprasath2004
    Posted about 1 year ago

    Hello i`ll wishing for your completion project solution.

    • Nice solution. It`s proper HTML structure format .

    • If I want to recommend the <article> Ex: <div class="Instructions"></div> to use the <article></article>

    • The <article> tag in HTML, introduced with HTML5, serves a vital role in structuring web content. It delineates a self-contained and cohesive piece of content within a webpage, such as blog posts, news articles, forum posts, or even comments. Its purpose is to encapsulate content that could be distributed or reused independently.

    • By employing <article>, developers can semantically differentiate the primary content from peripheral elements on the page, aiding both search engines and assistive technologies in comprehending the significance of the encapsulated content. Typically, an <article> element includes a heading, usually marked up with <h1> to <h6>, providing a clear title or headline for the contained content.

    • This tag's usage aligns with the broader efforts in HTML5 towards improving the semantic structure of web documents, fostering accessibility, search engine optimization (SEO), and overall maintainability of websites.

  • FabFalch•130
    @FabFalch
    Posted about 1 year ago

    Just submitted mine so looking at others! Looks great! I've just checked out your README for this project also, I'm looking to see how I can improve my future README's for upcoming projects.

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 1st-party linked stylesheets, and styles within <style> tags.

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.

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

Oops! 😬

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

Log in with GitHub