UI Improvement: Better handling of no results when filters are applied.

[NehalSurti]

UI Improvement: Better handling of no results when filters are applied

Description:

When applying filters that result in no available repositories, the current UI does not effectively communicate this to the user. The page appears empty without any indication that no results match the applied filters.

Additionally, when no results are found:

• The page numbering, typically located at the bottom of the page, is also repositioned.
• The "Privacy and cookie settings" element, typically located at the bottom of the page, is also repositioned.

Steps to Reproduce:

1. Go to the Good First Issues website.
2. Apply a combination of filters that result in no repositories being found.
3. Observe the UI when no results are available, noting the position of the page numbering arrows and the "Privacy and cookie settings" element.

Suggested Expected Behavior:

• A message should be displayed indicating that no repositories match the applied filters.
• The page numbering arrows should remain in their original position.
• The "Privacy and cookie settings" element should stay at the bottom of the page.

Actual Behavior:

• The page is empty with no clear indication that the filters have resulted in no available repositories.
• The page numbering arrows are displaced from its original position at the bottom of the page.
• The "Privacy and cookie settings" element is displaced from its original position at the bottom of the page.

Screenshots:

[Khushboo2724]

i will like to contribute to this

[vishalpatil1899]

/assign

[gnaneshreddyy]

Hello @NehalSurti,

I have reviewed the bug and am very eager to resolve it. Could you please assign it to me? I am confident I can fix it within two days and ensure the website runs smoothly.

Additionally, I am currently unable to see the "Privacy and Cookie Settings" element, which, as you mentioned, should reposition when no search results apply.

Please find the below attachment.

Thank you!

[SuperAKWA]

Hi guys!

I noticed that the issue screenshot comes from the version available online, but when running the project locally from the repository, the design and features seem more advanced. Could you clarify if this issue is still relevant to the current production version (likely on gh-pages) or if it applies to the development version from the repository?

In the version running locally, the message "Oops! No issues found matching your filters" already displays correctly when no issues are available. However, I made a few small improvements on my fork to refine the user experience, such as slightly improving the error message display and ensuring it integrates seamlessly with the modern design.

Let me know if you'd like me to adjust my changes for the production branch (e.g., gh-pages) or if there’s another way I can help address this issue more effectively.

Thanks in advance for your guidance!