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

My Recipe Page Solution

P
Jocelyne Teles•180
@JocelyneTeles98
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 could manage to create a responsive page only using CSS. Also, I learned how to style unordered and ordered list (this is the first time I'm doing it). Next time, I hope to practice more about these aspects of styling a website, specially with responsiveness, which I learned that I should go first with mobile screen sizes, and then tablet and desktop sizes.

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

The challenges I encountered:

  1. List styles: First time I change the colour of the bullets and numbers of the lists, and also changing the padding to fit with the titles and subtitles. I found out some solutions by searching them through W3Schools, MDN, and ChatGPT.
  2. Responsive: I learn to manage correctly this aspect because I was doing it wrong all the time 😅. I learned that the correct way to approach this is starting with the mobile size, then tablet size, and finally desktop size. Fun fact: With this project, I needed to "delete" (comment, erase, move lines of code) and write the code again to fix this. I overcome this with searching all about responsiveness through internet.
What specific areas of your project would you like help with?

I think I managed well but if you have more information about styling lists and responsiveness, I will be eternally grateful 😊.

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 Jocelyne Teles'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
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 1st-party linked stylesheets, and styles within <style> tags.

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.