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

Recipe page solution

Seyed Ahmad•80
@seyedahmaddv
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 take particular pride in creating a clean semantic HTML structure that properly uses sectioning elements for accessibility, along with a fully responsive design that adapts beautifully across devices. The typography hierarchy combining Young Serif for headings and Outfit for body text creates strong visual appeal, while custom styling touches like the ::before pseudo-elements for list bullets add polish. For future iterations, I would focus on optimizing the CSS architecture - perhaps implementing BEM methodology to make the stylesheets more maintainable.

The nutrition table could be rebuilt using CSS Grid for more layout flexibility, and I'd refine the ordered list styling in the instructions section for better alignment.

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

Several interesting challenges emerged during development. Getting the custom list bullets to align perfectly with their text required careful absolute positioning and padding adjustments. Mobile responsiveness needed extra attention, particularly for padding values which I fine-tuned through targeted media queries.

I improved font loading performance by adding preconnect hints in the head section after noticing occasional render delays. Accessibility was another focus area - after an initial oversight, I made sure to add descriptive alt text for the omelette image and verified color contrast ratios.

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

I would greatly appreciate expert eyes on several aspects of this project. A CSS architecture review could help me adopt better organizational patterns like BEM or SMACSS. An accessibility audit would be invaluable to identify any WCAG compliance issues I might have missed, particularly around ARIA labels and interactive elements.

Performance optimization suggestions, especially regarding font loading strategies like font-display: swap, would be welcome. Finally, I'd love insights on cross-browser compatibility testing strategies to ensure consistent rendering across less common browsers.

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Seyed Ahmad's solution.

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
  • Use cases

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