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

Recipe Page built with nextjs and tailwindcss

react, tailwind-css, next
Nate Poli•60
@njpoli
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?

Fairly simple project. Only thing I would do differently next time is hopefully complete the challenge faster. It took me longer than expected to complete.

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

The only trouble I had for this project was dealing with getting the text to go to the right of the makers. It works on the first line but once it goes to the next line the text is directly under the marker rather than going under the first word of the text. If anyone could point out to me how to do it that would be great.

Adding left margin inside of a span nested inside of the list item only worked for the first line. I also tried wrapping the text content in a div and made the div a block-level element, but that put the entire block of text on the next line with the marker above it.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Rafael Ibarra•120
    @rafbar2000rr
    Posted 9 months ago

    In my project I did the following in <ol>, I didn't use list-inside-space neither marker:text-primary-nutmeg:

    <ol class=" pl-5 ml-[10px] list-decimal "> and for each <li> I only added a padding left class pl-2, this way: <li class="pl-2"> So each text will be at the right of its marker and it worked.

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.

Oops! 😬

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

Log in with GitHub