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

Recipe Page – Built with HTML, CSS, and Responsive Design Techniques

Arham Ali•10
@Arham5503
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 successfully implementing a responsive recipe page with a clean and structured layout using only HTML and CSS. The use of custom fonts, CSS variables, and semantic HTML ensures both readability and maintainability. Additionally, I ensured that the design remains visually appealing across different screen sizes with media queries.

What would you do differently next time? Next time, I would:

Improve interactivity by adding JavaScript features like a dark mode toggle or a checklist for ingredients.

Enhance accessibility by using ARIA attributes and improving keyboard navigation.

Optimize for performance by lazy-loading images and minimizing CSS.

Explore animations for a smoother user experience, like hover effects on list items.

What challenges did you encounter, and how did you overcome them?
  1. Responsive Design Adjustments Challenge: Ensuring the layout remained consistent across different screen sizes, especially on mobile devices. Solution: I used CSS media queries to adjust the layout for smaller screens, ensuring images and text resized properly. I also made the main container fluid (80% width on larger screens and full width on mobile) for better responsiveness.

  2. Custom Fonts Not Loading Properly Challenge: Initially, the custom fonts (YoungSerif and Outfit) didn’t display correctly. Solution: I checked the file paths and ensured the @font-face declaration was correctly linked to the font files. I also provided fallback fonts in case the custom ones failed to load.

  3. List and Table Styling Issues Challenge: The bullet points and table layout didn’t look visually appealing at first. Solution: I used ::marker to style list items and nth-child selectors to customize table rows, improving readability and structure.

  4. Maintaining Clean & Reusable CSS Challenge: Managing colors and typography without duplicating styles. Solution: I implemented CSS variables (:root) for colors and font sizes, making the styles easier to manage and update in the future.

What specific areas of your project would you like help with?
  1. Code Optimization & Best Practices Are there any redundant CSS styles that could be simplified or improved for better maintainability?

Any suggestions for optimizing the HTML structure to make it more semantic and accessible?

  1. Enhancing User Experience (UX) & Interactivity What JavaScript features could enhance usability, such as an ingredient checklist or a dark mode toggle?

Would adding smooth transitions or animations improve engagement, and if so, where should they be implemented?

  1. Performance Optimization Are there performance improvements I can make, such as lazy-loading images or reducing CSS file size?

Would using CSS Grid instead of Flexbox for layout be a better approach in this case?

  1. Accessibility Improvements How can I improve keyboard navigation and screen reader support for a more inclusive experience?
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Le-Joker•80
    @Le-Joker
    Posted 2 months ago

    TRES INSTRUCTIF

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