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

responsive job listing website with add job feature

material-ui, react, react-router, materialize-css
Gift Richard•520
@fibonacci001
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?

Yo, what's up my coding superstars! 🔥 I'm stoked to share the deets on my latest React project tackling that job listing site challenge. Talk about a glow up for my frontend skills! 💪

Ensuring accessibility across devices was a top priority, and let me tell ya, it wasn't a walk in the park. But with some savvy moves, we crushed it like coding rockstars! 🤘

First up, responsive design was the name of the game. We leveraged those slick Material UI components and CSS media queries to serve up a layout that adapts like a chameleon to any screen size. Desktops, tablets, mobiles - you name it, we nailed it! 📺💻📱

But accessibility isn't just about looking good, it's about making sure everyone can enjoy the experience, right? 🌈 That's why we went the extra mile with keyboard navigation, proper focus management, and aria roles to keep things inclusive for our assistive tech fam.

Speaking of inclusivity, alt text for images was a no-brainer. Because let's be real, screen readers deserve to bask in the glory of our pixel-perfect designs too! 📷🔊

Now, let's talk code organization because that's where the real magic happens. 🧙‍♀️ We broke things down into reusable components, scoped styles for each one, and kept our file structure on point. Goodbye spaghetti code, hello maintainable masterpiece! 🍝👋

But you know what they say, there's always room for improvement! 🏔️ I ran into a hiccup with the app router when deploying to GitHub Pages. Couldn't get the page to display, and refreshing brought on that dreaded "no website assigned" error. 😩

I had to ditch the conditional rendering in the route handler and add the displayed jobs differently to the App component. Not gonna lie, it was a bit of a head-scratcher. 🤔

So if any of you React wizards out there have tips on how to tackle this routing issue more elegantly, I'm all ears! 👂 Hit me up with your wisdom, fam. Together we can conquer these challenges and build websites that are accessible, organized, and just plain awesome! 🚀

Let's keep pushing boundaries, breaking barriers, and making the web a better place for all users. Who's with me? 🙌👏✨

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

when I tried deploying this bad boy to GitHub Pages, things got a little wonky with the React Router setup. I had implemented conditional rendering in the route handler to display different components based on the URL path. But alas, once deployed, the pages wouldn't load correctly, and refreshing would hit me with that dreaded "no website assigned" error. 😩

I had to ditch the conditional rendering and add the job listing and posting components directly to the App component as a workaround. But let's be real, that's not a sustainable solution, fam. It's like putting a band-aid on a broken leg. 🩹

I need to figure out how to properly configure React Router for deployment on GitHub Pages (or any static hosting service, really). Is there some special server-side rendering magic I'm missing? Maybe I need to tweak the routing configuration or add some fancy redirect rules? 🧐

I'm all ears for any tips, tricks, or tried-and-true methods you React routing masters have up your sleeves. Hit me with your best shot! I'm determined to get this routing situation squared away once and for all. 💪

Routing is a crucial part of any web app, and I want to make sure I'm doing it right. No more workarounds or half-baked solutions – I'm aiming for a clean, robust implementation that plays nicely with static hosting services like GitHub Pages.

So, please, my coding compadres, share your wisdom! Let's tackle this routing conundrum head-on and make sure this project is truly deployment-ready. With your guidance, I'm confident we can slay this beast and emerge victorious! 🐉🗡️

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 Gift Richard'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.