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

Recipe page built using neovim

pure-css, vanilla-extract
Sam•170
@wotanut
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 extremely proud that I was able to style the lists. This took some time but in the end I had to go back and insert a lot of span's just so I could colour the bullets but not the text and then bold part of the paragraph but not all of it. I used neovim's amazing macro keys and figured out how they worked.

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

This one had a lot of challenges, not least that for some reason my git repo reset itself midway through and I lost half my work, meaning I had to spend a further few hours fixing it.

Other challenges were getting the content to be centred, deciding on a font, spacing and the table at the bottom.

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

I would like help with the units that I used (percentages vh,vw etc) to make sure that i'm using the right units, I would also like to know why I struggled to center the content originally and how to get better at spacing the elements.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Adelabu Mobolaji•440
    @Bolazcoding
    Posted 10 months ago

    Firstly you did great. Your font styles are not applied. Instead you can go to google font and import the font style into your code. It is not bad that you used for vh and vw for the width and height. It is a good practice that you use percentage for width and height and pixels or rem for margins.

    Marked as helpful

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