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

recipe page using html and css

Nicolette Reneilwe Mashaba•140
@Reney17
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 am most proud of how the layout and styling of the recipe page came together. The use of semantic HTML for accessibility and the use of custom properties (CSS variables) for colors really helped maintain consistency across the design. Additionally, the responsive design works well across different screen sizes, ensuring a good user experience on both mobile and desktop.

Next time, I would optimize the code for accessibility even more, such as adding aria-labels and alt texts to images. I would also look into further improving the SEO by adding meta tags for social media sharing and making sure the page is mobile-first to enhance the loading performance.

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

One of the challenges I encountered was ensuring that the layout remained consistent across different screen sizes. Some of the sections, particularly the table and the image, were not aligning correctly on smaller devices. To overcome this, I used CSS media queries to adjust the layout for various screen sizes, which allowed the design to remain responsive.

Another challenge was ensuring the styling of the list items within the ingredients and instructions sections. Initially, the default browser styling made it difficult to keep the design clean and readable. I solved this by using custom list markers, adjusting the padding, and styling the list items with specific colors and fonts to improve readability.

Lastly, I encountered a challenge with the font sizes for headings on mobile screens. To make sure the text was still readable without being too large, I adjusted the font sizes for smaller screens using media queries and tested on multiple devices to ensure the design remained user-friendly.

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

Accessibility Improvements: I would appreciate feedback on how to improve the accessibility of my page, especially regarding image alt attributes, aria-labels, and any other suggestions to make the page more user-friendly for those with disabilities.

CSS Optimization: Although the layout works well, I am interested in getting feedback on whether there are any CSS performance improvements or best practices I could adopt to make the styles more efficient, especially regarding the use of media queries and CSS variables.

SEO Enhancements: I'd like advice on SEO improvements. What are the best practices for adding meta tags for social media sharing (e.g., Open Graph, Twitter Card tags)? Also, are there any other suggestions to improve the search engine ranking of the page?

Responsive Table Design: While the table layout works, I am curious if there are more effective ways to handle responsive tables. For example, I noticed that the table’s content might not look great on very small screens, and I’d like to know if there are more elegant solutions for making tables mobile-friendly.

Any advice or suggestions in thes

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Awoyinka Opeyemi•50
    @hoppYo
    Posted 5 months ago

    awesome

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