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

Recipe page

tailwind-css
P
jeffgrahamcodes•260
@jeffgrahamcodes
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 how well the structure and design align with the mockup provided. The use of semantic HTML, such as <article>, <section>, and <figure>, ensures the content is accessible and meaningful. The CSS refactor introduced reusable design tokens for colors, typography, and spacing, which improved maintainability and made the code easier to scale. Additionally, the layout adapts seamlessly across different screen sizes, preserving the design’s visual hierarchy and user experience.

If I were to approach this project again, I’d dedicate more time to enhancing accessibility by adding descriptive alt text to images and considering screen reader optimizations like aria-labels for interactive elements. I would also explore adding subtle animations or transitions to improve interactivity and make the user experience more engaging. Finally, further testing for edge cases, such as very narrow viewports or long text strings, could help identify areas for fine-tuning.

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

One of the main challenges was ensuring the text content remained visually balanced and aligned across different screen sizes. Initially, text wrapping issues and inconsistent spacing caused the layout to deviate slightly from the design mockup. This was resolved by refining the typography styles, adjusting line heights, and using consistent padding and margins defined by CSS variables. Another challenge was managing the list styles, particularly ensuring markers and text alignment matched the mockup’s aesthetic. By using ::marker styling and centralizing spacing rules, I achieved a clean and organized list layout.

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

I’d appreciate feedback on the responsive design, particularly how well it performs on smaller screens. Additionally, guidance on optimizing accessibility for screen readers and ensuring a smooth experience for keyboard navigation would be valuable. If there are any opportunities to further reduce CSS redundancy or improve the semantic structure of the HTML, I’d love to hear suggestions. Finally, any ideas for enhancing interactivity, such as subtle animations or hover effects, would be helpful to make the design more dynamic and engaging.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Belamana-Harshitha•150
    @Belamana-Harshitha
    Posted 6 months ago

    Thanks this was my first challenge learnt a lot

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