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

HTML, CSS, and responsive design Web Page

lighthouse
Yasser Esam•120
@YasserEsam
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 most proud of achieving a clean and visually appealing design that closely matches the provided specifications

Next time, I would focus on improving the accessibility features of the project. This would include adding more semantic HTML elements and ensuring that all interactive elements are accessible with keyboard navigation. I would also consider implementing a more modular CSS architecture to further streamline the styling process.

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

One of the main challenges I encountered was aligning the design precisely with the provided mockups, particularly in terms of spacing and responsive behavior. To overcome this, I used browser developer tools to fine-tune the CSS and adjust the layout to match the design as closely as possible. I also used media queries extensively to ensure that the page looked good on both mobile and desktop screens.

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

I would appreciate feedback on the following areas:

  1. Responsiveness: Are there any improvements I can make to ensure the layout is even more fluid across different devices and screen sizes?
  2. Accessibility: Are there any specific accessibility improvements that could be made to enhance the usability of the page for all users?
  3. CSS Organization: Does the CSS code follow best practices in terms of organization and modularity? Are there any recommendations for refactoring or improving the stylesheet?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Pedro Eustáquio•220
    @PedroEustaq
    Posted 11 months ago

    Responsiveness: Yes there is a type of Grid called Flexbox, it is very helpful to make containers flexible and to move things inside them! Accessibility: I don't think so, normally people read recipes by scrolling down, which is present on your website. CSS Organization: its simple has that! Nice Semantic!

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