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

i use HTML, CSS, And Text editor Vs Code

Rafi Rachmawan•210
@rafirachmawan
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 that I probably spelled this out more by heart than asking chatgpt because I've worked on the project before.

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

Maybe the challenge I faced in terms of design was difficult because I didn't use the plus so I didn't get a figma design so I just worked with sample photos.

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

in terms of padding margin due to not getting the figma design

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • gabrilov•80
    @gabrilov
    Posted 8 months ago

    Hello!

    I'll tell you what I've seen: I see some problem with the colors: the background color and the header color does not correspond to the original template.

    On the other hand, in this exercise the semantics in html are important, and I see that you have not implemented it. Tags like "main" or "section" don't appear, and I only see "div," which is fine for structural needs, but not for giving meaning to those structures.

    I hope it has been useful to you.

    Best regards! :)

    Marked as helpful
  • Outstandinggirl13•70
    @Outstandinggirl13
    Posted 8 months ago

    Hello! If you'd like, I can recommend preconnecting fonts to enhance styling. You can find the font names in style-guide.md and add them to the <head> tag (through the <link> tag) in your HTML. Alternatively, since the starter files already include the fonts in the assets folder, you can add them directly to your CSS using @font-face. I hope you find this advice helpful. Wishing you all the best with your projects!

  • Rafi Rachmawan•210
    @rafirachmawan
    Posted 8 months ago

    okay thank you i will change and revise it as soon as possible thank you sir

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, SASS, 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

Oops! 😬

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

Log in with GitHub