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

CSS Grid,CSS Flex

foundation
arcueid-x•50
@arcueid-x
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?

This is my first time trying rem instead of px, and I think it's a step forward for me. It's more beneficial for responsive layouts. Also, I used to really like the Grid layout, but this time I didn't use it entirely. Instead, I combined Flexbox and Grid layouts, and I'm happy to try more things. Additionally, I used global variables for all the colors with :root, and I found that really convenient.

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

I am not very proficient with media queries, and this time I encountered some issues while using them, which I managed to resolve. I will organize my notes and upload them to GitHub. Additionally, I don't use Flex very often, and this time I ran into a problem when applying a Flex layout to a ul element. Even though I used flex-wrap, the items still didn't wrap to the next line. This made me realize the importance of flex-direction, and I am glad to continue learning through practice.

Another thing is about modifying the marker before li elements. Previously, I avoided using li because I didn't know how to change the marker. This time, I tried using li and learned that I can use li::marker to alter the properties of the marker.

Also, regarding the <main> and <section> tags, this was my first time using them, and I gained a deeper understanding of their meanings.

Lastly, the letter-spacing property is something I rarely used before and had almost forgotten about. This time, I revisited letter-spacing and learned a lot from this exercise. Overall, I gained a lot from this practice session.

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

I'm not sure how well I'm using media queries. I also realize that I used to rely heavily on div and span elements, which probably isn't the best practice, right?

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 arcueid-x'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 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.