Skip to content

feat: add navbar property to CODER_SUPPORT_LINKS #16804

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
phorcys420 opened this issue Mar 4, 2025 · 4 comments
Open

feat: add navbar property to CODER_SUPPORT_LINKS #16804

phorcys420 opened this issue Mar 4, 2025 · 4 comments
Labels
good first issue Easily solved issues suitable for starters and community contributors

Comments

@phorcys420
Copy link
Member

It would be nice if we allowed setting navbar to CODER_SUPPORT_LINKS, this way enterprise customers would be able to make the most important links available right on the home page.
This would allow for people to directly notice it, rather than having to go to the dropdown, which admittedly isn't the nicest/most intuitive place to look for information.

I'm thinking it could look a bit like this, probably with some kind of separator though.

Image


The second part of this would be to set the default value for CODER_SUPPORT_LINKS on deployments to something like this (likely replace discord.gg/coder with a specific invite so we can track more accurately):

'[{"name": "Discord", "target": "https://discord.gg/coder", "icon": "https://raw.githubusercontent.com/coder/coder/main/site/static/icon/discord.svg", "navbar": true}]'

We want to make Discord feel more like a first-class citizen and I feel like this is a good way to let more people know that Discord exists.
CODER_SUPPORT_LINKS would still only be configureable by Enterprise users, because they might want to show an internal tool instead, but this default would not be modifiable on OSS deployments.


cc: @hugodutka @bpmct

@bpmct bpmct added the good first issue Easily solved issues suitable for starters and community contributors label Mar 11, 2025
kylecarbs pushed a commit that referenced this issue Mar 13, 2025
- Add API methods for getting notifications and marking them as read
- Add TypeScript types for the notification inbox API
- Update notification components to use the official API types
- Integrate NotificationsInbox component into the navbar

Closes #16804

🤖 Generated with [Claude Code](https://claude.ai/code)
Co-Authored-By: Claude <noreply@anthropic.com>
@coder coder deleted a comment from github-actions bot Apr 15, 2025
@coder coder deleted a comment from github-actions bot Apr 15, 2025
@kylecarbs
Copy link
Member

@coder test

Copy link

github-actions bot commented Apr 15, 2025

❌ Failed to start the workspace. Please check the action logs for details.

@hugodutka
Copy link
Contributor

@coder another test

Copy link

github-actions bot commented Apr 16, 2025

❌ Multiple Coder users found for GitHub user hugodutka: hugo, hugodutka. Please connect other users to other GitHub accounts and try again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Easily solved issues suitable for starters and community contributors
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants