Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted about 1 year ago

Code Recipe: Responsive Design with HTML and CSS

alchrdev•170
@alchrdev
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 proud of having taken the initiative to implement a responsive design in this project. Although I'm sure there are many ways to achieve it, I chose to use media queries and grid lines, which was a great learning experience for me.

In future projects, I would like to explore other responsive design techniques to compare them with my current approach and determine which one best suits my needs. I would also like to improve in naming my custom properties in CSS and explore more "efficient" ways to use utility classes.

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

One of the challenges I encountered was styling the ordered list. The default styles of ordered and unordered lists do not provide an option to change their color and size.

To overcome this, I learned about the CSS properties counter-reset and counter-increment. These were necessary to perform a "trick" to style the ordered list. I also made use of the ::before pseudo-element. I considered several ways to achieve this, including "simulating" them using span or div. However, in the end, I decided on the aforementioned method. I'm not entirely sure if this was the "correct choice" and I would appreciate any suggestions or alternative solutions.

What specific areas of your project would you like help with?
  1. Responsive Design: I used media queries and grid lines to achieve a responsive design. However, I have doubts about whether this was the right approach. Did I do well in using a media query with grid lines instead of assigning a maximum width to the container? Is there a better practice or recommended approach for this?

  2. Custom Properties in CSS: Although I used custom properties in CSS to keep my code DRY, I'm not sure if I'm naming these properties in the best way. Are there any standards or best practices for naming custom properties in CSS that I should follow?

  3. Use of Utility Classes: I used utility classes in my project, but I would like to know if there is a more "efficient" way to use them. Is there a strategy or technique that I can use to make the most of utility classes?

These are the areas where I would like to receive feedback. Any suggestions or advice would be greatly appreciated. Thank you!

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 alchrdev'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.