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

Job Listings with React, Framer Motion, and Material UI

framer-motion, react, material-ui
Julianna Messineo•290
@mathematiCode
A solution to the Job listings with filtering 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 of the animations that I have for when you select a job to see more details. (See if you can guess what prompt I gave chatGPT to come up with those job details 👀). I'm also proud of the overall look on desktop because the CSS was very challenging. I tried many things but wasn't ultimately able to get the jobs centered on mobile :(.

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

I'm still learning when it's appropriate or necessary to use an effect and state so that took some time to figure out. I think I may have used more effects than necessary but I'm not entirely sure. It was also a little confusing to figure out how to filter the jobs by traversing two different arrays and seeing if they have any matches to then display that job. I may have done that in a more expensive way than necessary but it works. The CSS was also very challenging with this one. One issue that I kept running into was when you filter for backend jobs, there's less stuff in that box than the rest so it would make my whole main div smaller. Almost like I had width: fit-content but I didn't. It was because I had some flexbox divs and I had to change them to display: inline so they wouldn't become smaller just because there was less space needed.

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

I would love feedback on my React architecture, like if I used effects and context only when needed and organized things well.
CSS feedback is also welcome!

Code
Loading...

Please log in to post a comment

Log in with GitHub

Community feedback

  • khaduj || خدوج•670
    @khaduj03
    Posted 7 months ago

    Wow, great job! You’ve done an amazing job with the project. Good luck, dear friend! 😊🌟

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.

Oops! 😬

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

Log in with GitHub