Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Oct 28, 2025

On small screens, the "Get involved" button in the navbar was cut off and inaccessible. The button is now responsive using Bootstrap display utility classes to maintain visibility on large screens while preventing cutoff issues on smaller screens.

Changes

  • Added responsive display classes to the button in layouts/partials/navbar.html (line 120)
<!-- Before -->
<li class="nav-item">
  <a href="/about/get-involved/" class="nav-link btn btn-primary nav-btn">🚀&nbsp;Get&nbsp;involved!</a>
</li>

<!-- After -->
<li class="nav-item d-none d-xl-block">
  <a href="/about/get-involved/" class="nav-link btn btn-primary nav-btn">🚀&nbsp;Get&nbsp;involved!</a>
</li>

Responsive Behavior

Responsive Behavior Diagram

  • XL screens (≥1200px): ✅ Button visible as prominent call-to-action in navbar
  • Large screens (992-1199px): ⚠️ Button hidden to prevent cutoff issues
  • Medium/Small screens (<992px): 📱 Menu collapses - accessible via "About FORRT → Get Involved"

This solution keeps the visual, prominent button on larger displays while preventing the cutoff issue on medium screens. "Get involved" remains accessible on all screen sizes either through the prominent button (XL screens) or the "About FORRT" dropdown menu (smaller screens).

Fixes #195

Original prompt

This section details on the original issue you should resolve

<issue_title>Website does not adapt to screen width</issue_title>
<issue_description>When I am on the FORRT website, the window only shows half of the "get involved" button and completely cuts off the github button on the right because the width of the window/website is not adapted to my small laptop screen. It would be great if it was at least possible to scroll to the side (which is maybe not the most user friendly solution) or in the best case that the window is adapted to the screen width.
</issue_description>

<agent_instructions>Fix this display issue, likely by including the button into the menu</agent_instructions>

Comments on the Issue (you are @copilot in this section)

@richarddushime @LeonieDudda Thank you for bringing this to our attention!

I’ve been testing the website on various screen sizes, and it seems to display correctly on most devices. However, your feedback is valuable, as it highlights an area we can improve.

Could you please share the specific device and screen size you’re using? This information will help us optimize the website to ensure it works seamlessly for devices like yours.

Thank you!</comment_new>
<comment_new>@flavioazevedo
Keep open. Just tagging @LukasWallrich here too :)</comment_new>
<comment_new>@LukasWallrich
This appears to be because "Get involved" is not part of the menu. @richarddushime the menu collapsed when publications is touched - but get involved can be cut off. Could you have another look - maybe that can be added to the menu? [Even though it would be nice to keep the image.]</comment_new>
<comment_new>@flavioazevedo
Open</comment_new>
<comment_new>@flavioazevedo
@richarddushime can you check what @LukasWallrich writes above, please?</comment_new>


💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

… About FORRT menu

Co-authored-by: LukasWallrich <60155545+LukasWallrich@users.noreply.github.com>
@LukasWallrich
Copy link
Contributor

@copilot can the button disappear when it leaves the viewport? In general it would be good to have a very visual get involved

Copilot AI changed the title [WIP] Fix website display issue for small screens Remove hardcoded "Get involved" button from navbar to fix small screen responsiveness Oct 28, 2025
Copilot AI requested a review from LukasWallrich October 28, 2025 22:11
Copilot finished work on behalf of LukasWallrich October 28, 2025 22:11
…n smaller to prevent cutoff

Co-authored-by: LukasWallrich <60155545+LukasWallrich@users.noreply.github.com>
Copy link
Contributor Author

Copilot AI commented Oct 28, 2025

@copilot can the button disappear when it leaves the viewport? In general it would be good to have a very visual get involved

The button now uses responsive display classes (d-none d-xl-block) so it:

  • ✅ Stays visible on extra-large screens (≥1200px) for maximum visibility
  • ⚠️ Hides on large/medium screens (992-1199px) to prevent cutoff
  • 📱 Accessible via "About FORRT → Get Involved" on all smaller screens

This keeps the visual, prominent button on larger displays while preventing the cutoff issue.

Responsive behavior diagram

Commit: a6ca311

Copilot AI changed the title Remove hardcoded "Get involved" button from navbar to fix small screen responsiveness Make "Get involved" button responsive to fix small screen cutoff issues Oct 28, 2025
Copilot finished work on behalf of LukasWallrich October 28, 2025 22:18
@LukasWallrich LukasWallrich marked this pull request as ready for review October 28, 2025 22:29
@LukasWallrich LukasWallrich requested a review from a team as a code owner October 28, 2025 22:29
@github-actions
Copy link
Contributor

👍 All image files/references (if any) are in webp format, in line with our policy.

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

1 similar comment
@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

Copy link
Contributor

@LukasWallrich LukasWallrich left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works in my testing - a clean solution.

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

3 similar comments
@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@richarddushime
Copy link
Contributor

Works in my testing - a clean solution.

the btn is instead getting hidden on small devices
inspect in the browser tools and check

@richarddushime
Copy link
Contributor

I think instead of hidding the btn completely we can try to adjust on styles so that it all fits as expected
Also most of the devices fits and displays well
only NestHub

see the screenshot
Screenshot 2025-10-29 at 22 43 32

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

17 similar comments
@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

I don't understand what this is showing? You are right that the button gets hidden like this - not ideal, but imho more professional than it getting cut off. If you have a better fix, go for it ... my only thinking would be a dynamic menu element that gets unhidden as the button gets hidden?

I think instead of hidding the btn completely we can try to adjust on styles so that it all fits as expected Also most of the devices fits and displays well only NestHub

see the screenshot Screenshot 2025-10-29 at 22 43 32

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

10 similar comments
@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

@LukasWallrich
Copy link
Contributor

✅ This PR has been deployed to staging as part of an aggregated deployment. View at: https://staging.forrt.org

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Website does not adapt to screen width

3 participants