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

Responsive Mobile-first - static-job-listings-master

Barbara Ward•1,160
@bward67
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?

This is by far the best challenge I have completed on FEM...but it was also the HARDEST! I was able to do the HTML and CSS comfortably but I did get stuck for a long time on the JS - especially the filtering part. So I re-watched John Smilga's - Menu video: https://www.youtube.com/watch?v=3PHXvlpOkf4&t=8185s Thanks John - I have learned so much from you. I love the reduce method to get the unique categories.

However, I still couldn't complete this challenge completely so I watched this video from WebDevYT: https://www.youtube.com/watch?v=hGM8lMUqZLY&t=318s It just had music in the background so no explanations but after watching it twice and then studying the code in minute detail (for a loooong time!), I was finally able to understand the code and tweak mine to make it work. Thank you WebDevYT - your animation is class!

I chose to do a .forEach instead of the - for (let .. of) loops WebDevYT did just because I am more familiar with them but it was nice to see a different way of doing the same thing. For the filter part, I had to get an array of the items in the card and another array of the items in the filter. Then by using a boolean combined with a .forEach and an if statement, I checked if the filtered btns were not included in the card array. And if they were not included I removed that card. If they were included I brought that card back in.

If I am being honest, I am still a bit shaky on some of it - as in - if you put a gun to my head and forced me to do it without allowing me to review my notes from time to time, I am not sure I could complete it totally. But I will go over it many times now - starting with a blank JS page each time until it starts to come naturally.

Overall, this challenge was probably a bit too advanced for my current knowledge but I LOVED it and it encourages me to learn MORE because someday I want to be able to do all of this with my eyes - almost - closed!

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

No feedback yet. Be the first to give feedback on Barbara Ward's solution.

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.