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

Responsive Menu Card

react, typescript, tailwind-css
German Pinto•320
@germanp007
A solution to the Recipe page challenge
View live sitePreview (opens in new tab)View codeCode (opens in new tab)

Solution retrospective


Card Menu

Plz Need Feedback,in this solution i tried to made a semantic structure and clean code 🐱‍🏍 (❁´◡❁)(❁´◡❁)(❁´◡`❁)

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Petrit Nuredini•2,860
    @petritnuredini
    Posted over 1 year ago

    Congratulations on completing your project! It's impressive to see your dedication and attention to detail in building a visually appealing and structured application. Here are some short recommendations for further enhancement:

    1. Component Structure:

      • Reusability: Ensure your components like SectionOne, SectionTwo, etc., are reusable and can adapt to different content or layouts.
    2. CSS Best Practices:

      • Consistent Naming: Keep CSS class names consistent and descriptive for easy understanding and maintenance.
      • Responsive Design: Ensure your application is responsive across different devices. Consider using flexible units like rem for font sizes and margins.
    3. Accessibility:

      • Semantic HTML: Utilize more semantic HTML elements for better accessibility and SEO.
      • Alt Text: Ensure all images have descriptive alt text for screen readers.
    4. Code Organization:

      • Modularity: Break down large components into smaller, manageable pieces for better readability and maintainability.
    5. Performance:

      • Optimize Assets: Ensure images and SVGs are optimized for web use to improve load times.
    6. References for Learning:

      • CSS Techniques: CSS Tricks
      • React Best Practices: React Documentation

    Keep up the great work and continue to challenge yourself with new projects! Each project is an opportunity to learn and grow. Your progress is impressive, and I'm excited to see what you'll create next!

    Marked as helpful
  • Kevin•740
    @kevinfreitasv80
    Posted over 1 year ago

    Much Good, I liked that change in design

    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

Oops! 😬

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

Log in with GitHub