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

Mobile first page recipe page using HTML,CSS

praveen Agandla•60
@Praveen3009
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)
Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • https429•70
    @https429
    Posted about 1 year ago

    Hey there, Boss!

    Your code is already pretty solid, but there are always ways to improve or tweak things. Here are a few suggestions:

    1. Alt Text for Images: You've got an image tag with an empty alt attribute. It's a good practice to provide descriptive alt text for images. This helps with accessibility and SEO. For example, you could use alt="Omelette".

    2. Semantic HTML: Consider using more semantic HTML tags. For example, you could use <section> tags to group related content together, like the ingredients and instructions. This can improve accessibility and SEO.

    3. CSS Variables: You're using some colors multiple times in your CSS. You could define these as CSS variables at the top of your file. This makes it easier to maintain and change your color scheme.

    4. Font Loading: You're loading two different fonts using @font-face. Consider using a service like Google Fonts or Adobe Fonts. They can handle the font loading for you and can help improve performance.

    5. Responsive Design: You've got a media query for screens larger than 768px, which is great! You might want to consider adding more breakpoints for different screen sizes to make your design even more responsive.

    6. CSS Organization: Consider organizing your CSS in a more structured way. You could group styles by component or follow a methodology like BEM or SMACSS.

    Remember, these are just suggestions. Your code is already pretty good! Keep up the good work, mate! 🚀

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