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

RECIPE PAGE

echo-script0•180
@echo-script0
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 clean and visually appealing the final design turned out, even though I worked with just HTML and CSS. I focused on layout, spacing, and design details like background styling and fixed positioning, which really brought the project to life. Next time, I’d spend more time refining the responsive design for smaller screens and improving the structure of my CSS for better scalability. I’d also consider organizing my content more intentionally from the start and planning the sections better before diving into code.

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

One challenge I faced was managing the push and pull conflicts with GitHub, especially when the remote repository had updates I didn’t have locally. I overcame this by learning to properly use git pull to sync changes before pushing my own updates. Another challenge was making the background image fixed without cutting off page content. At first, using background-attachment: fixed made the page content get hidden or stuck. I had to experiment with CSS properties like overflow and adjusting layout styles to make sure the whole page was visible while keeping the background fixed. Lastly, figuring out how to deploy my project via GitHub Pages and set the correct source folder (root vs docs) took a bit of trial and error, but reading through the GitHub Pages settings and documentation helped me fix it.

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

I’d like support with better scaling and responsiveness, especially implementing font styles and sizes that adapt smoothly across different screen sizes and devices. Right now, my fonts can look too big or too small depending on the viewport, so guidance on using relative units, media queries, or modern CSS techniques like clamp would be really helpful. Additionally, tips on choosing accessible and visually appealing font pairings would improve the overall design and readability of my project.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on echo-script0'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

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.