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

Recipe Page Responsive Design

Aria Rouzegar•150
@Ariarzg
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 think I coded cleanly and learned so much in the process.

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

I tried so much to vertically center the bullets relative to the li elements when the text is more than 1 line; but I couldn't.

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

I am open to any feedbacks. but if anyone knows how to vertically center a bullet relative to the li element, please comment the solution.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • P
    Øystein Håberg•13,260
    @Islandstone89
    Posted 3 months ago

    HTML:

    • <main> holds all of the main content on a page. As a card would likely not be the only component on a page, I would wrap the card content in a <div class="card"> inside the <main> element. It's also possible to use an <article class="card">.

    • You should not include words like "image" or "photo" in the alt text, as screen readers announce images with "image", followed by the alt text.

    • Beware that the <section> element by default doesn't have any semantic meaning. It has a role of generic, which is the same as a <div>. To give it a role="region" in the Accessibility Tree, you need to give the section heading an id, which is then referenced by the section using aria-labelledby:

    <section class="ingredients" aria-labelledby="ingredients-title">
      <h2 class="section-title" id="ingredients-title">Ingredients</h2>
    

    CSS:

    • It's not recommended to use % for properties like margin, padding, width, height or border-radius.

    • I'll refer to the demo showing how to vertically center custom list bullets. You need to remove the default bullets (you have list-style: none in your CSS Reset, but it only applies to lists with a role="list"). Create a ::before pseudo-element with the same width and height and border-radius: 50% and aspect-ratio: 1 / 1. It also needs a background-color, content="" and display: block.

    Marked as helpful
  • Barnabas001•180
    @Barnabas001
    Posted 3 months ago

    Excellent webpage, site is responsive and look good on all screen size, good job overall

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

Oops! 😬

You need to be logged in before you can do that.

Log in with GitHub