Skip to content
  • Unlock Pro
  • Log in with GitHub
Solution
Submitted 24 days ago

react,vite,MaterialUi,Css,google-Fonts,vercel,git+github

material-ui, pure-css, react, vite, web-components
Zirwa Abid•10
@Zirwaabid
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 most proud of completing my first Frontend Mentor challenge from scratch using React and deploying it successfully with Vercel. I faced several errors during deployment, especially with image paths and Vite configuration, but I didn't give up and learned how to solve them on my own.

Next time, I’d focus more on planning a fully responsive layout from the beginning and possibly use styled-components or Tailwind CSS for better modular styling. I'd also organize my components and assets more cleanly and maybe add light interactivity (like theme toggling or animations).

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

I faced multiple challenges while working on this project. The biggest ones were:

Deployment errors on Vercel: I initially got "vite": "command not found" and missing package.json errors. I fixed these by installing Vite as a dev dependency, correctly setting the root directory, and updating the build settings in Vercel.

Image not showing after deployment: I had placed the image inside the src/assets folder, which caused a Vite build error on Vercel. I overcame this by moving the image to the public/ folder and referencing it using a direct path (/img1.jpeg), as Vite recommends for static assets.

Responsiveness issues: Initially, the layout didn’t look good on smaller screens. I adjusted my CSS using media queries and flexible layout techniques to make sure it works on both mobile and desktop, as per the design guide.

Despite these challenges, I kept trying different solutions, researched documentation, and stayed patient — and Alhamdulillah, I got it working!

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

I'd love feedback on the following areas:

Responsiveness: Does the layout look good across different screen sizes? Any improvements in spacing or text alignment? Component structure: I used Material UI's Card and CardMedia inside a single component. Is this a good practice for small projects, or should I break it into smaller components? Styling choices: I used a mix of MUI components and custom CSS. Would it be better to use a single styling method (like styled-components or Tailwind)? Performance: Are there any optimizations I could apply, especially for images or layout structure? General best practices: Any suggestions to improve my React + Vite workflow or folder structure?

I'm open to any kind of constructive feedback — thank you!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • Harsh Kumar•5,180
    @thisisharsh7
    Posted 24 days ago

    Great job on completing the challenge! Some suggestion:

    Responsiveness: The layout works well. Use relative units (rem, vw, %) over fixed heights (height: 250) and Test on various devices.

    Component Structure: Using MUI’s Card is fine for small projects.

    MUI: Mixing MUI and custom CSS works, but a single approach (e.g., Tailwind or styled-components) would streamline maintenance. Tailwind’s utility classes could simplify responsiveness.

    Images: Optimize images by using modern formats (WebP) and lazy-loading (loading="lazy" on CardMedia).

    Best Practices: Organize assets in public clearly (e.g., public/images). Use constants for static data (e.g., ingredients list).

    Overall, a strong start! Keep learning—happy coding!

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