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

Job listing with filtering

react
Gaurav chauhan•50
@ravenbirdb1b
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 challenges did you encounter, and how did you overcome them?

** Filtering Filtering Logic part is a bit tricky. gave some time to it to figure the solution out.

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

Need some help with the css, as to how can i improve it, please point out any mistakes if possible and also what can i do to improve the feature.

Code
Select a file

Please log in to post a comment

Log in with GitHub

Community feedback

  • Sara Dunlop•450
    @Risclover
    Posted 10 months ago

    Hi! Nice job! I just wanted to point something out. When you click on tags, there are inconsistencies with how they're staying highlighted. I'll try to provide a very specific example so you can see what I'm talking about.

    Steps to reproduce:

    1. Click on the Frontend tag in the 1st listing (Photosnap Senior Frontend Developer)
    2. Click on the Junior tag in the 2nd listing (Account Junior Frontend Developer)
    3. Click on the CSS tag in the 2nd listing (MyHome Junior Frontend Developer).
    4. Click 'Clear' to clear the tags.

    You'll notice that the CSS tag is still highlighted.

    1. Click Frontend in the 1st listing again.

    CSS is still highlighted, so it's not an issue of it merely being the "last tag clicked" or anything.

    1. Close the Frontend tag by clicking the X close button.

    Frontend and CSS are still both highlighted.

    Just as an example. It seems that that's some logic that you need to hammer out. :) Just thought I'd make you aware! <3

    Marked as helpful
  • Teodor Jenkler•4,040
    @TedJenkler
    Posted 10 months ago

    Hi @ravenbirdb1b,

    Nice project—it looks really good! However, it seems you might have overlooked responsiveness.

    Are you using Chrome DevTools? If not, I recommend starting to use it. After you finish each project, check it across various common screen widths to ensure it doesn’t break.

    I’d also suggest looking into a mobile-first approach and avoiding fixed widths and heights. Instead, use properties like min-width or max-width to prevent overflow issues. Currently, your site breaks between 375px and 500px wide, making it difficult to use on phones and small tablets.

    For improving your CSS skills, I recommend watching Kevin Powell on YouTube. His best practices can help you become a CSS master.

    I hope this feedback is helpful!

    Best, Teodor

    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 1st-party linked stylesheets, and styles within <style> tags.

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.

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