-
-
Notifications
You must be signed in to change notification settings - Fork 10.3k
[doc] Add Slack and Forum to the top navigation #20208
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
[doc] Add Slack and Forum to the top navigation #20208
Conversation
👋 Hi! Thank you for contributing to the vLLM project. 💬 Join our developer Slack at https://slack.vllm.ai to discuss your PR in #pr-reviews, coordinate on features in #feat- channels, or join special interest groups in #sig- channels. Just a reminder: PRs would not trigger full CI run by default. Instead, it would only run Once the PR is approved and ready to go, your PR reviewer(s) can run CI to test the changes comprehensively before merging. To run CI, PR reviewers can either: Add 🚀 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @reidliu41, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!
This pull request introduces a user experience improvement to the documentation website by integrating a prominent Slack button into the top navigation. The primary goal is to facilitate easier access for users to join the project's Slack community, thereby enhancing engagement and support channels.
Highlights
- Documentation Enhancement: A new Slack button has been added to the top navigation bar of the documentation website, providing users with a direct link to join the project's Slack workspace.
- Frontend Implementation: The Slack button is implemented using a new JavaScript file (
slack.js
) that dynamically creates and inserts the button into the header, and new CSS rules (extra.css
) to style its appearance and hover effects. - Build Configuration Update: The
mkdocs.yaml
configuration file has been updated to include the newslack.js
JavaScript file, ensuring it is loaded and executed as part of the documentation site.
Using Gemini Code Assist
The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.
Invoking Gemini
You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command>
or @gemini-code-assist <command>
. Below is a summary of the supported commands.
Feature | Command | Description |
---|---|---|
Code Review | /gemini review |
Performs a code review for the current pull request in its current state. |
Pull Request Summary | /gemini summary |
Provides a summary of the current pull request in its current state. |
Comment | @gemini-code-assist | Responds in comments when explicitly tagged, both in issue comments and review comments. |
Help | /gemini help |
Displays a list of available commands. |
Customization
To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/
folder in the base of the repository. Detailed instructions can be found here.
Limitations & Feedback
Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.
You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.
Footnotes
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code Review
This PR adds a Slack button to the header. The review suggests using a semantically correct HTML element (<a>
instead of <button>
) and centralizing all styling in the CSS file. These changes will improve maintainability and accessibility.
docs/mkdocs/javascript/slack.js
Outdated
const slackButton = document.createElement('button'); | ||
slackButton.className = 'slack-button'; | ||
slackButton.title = 'Join us on Slack'; | ||
slackButton.style.border = 'none'; | ||
slackButton.style.background = 'transparent'; | ||
slackButton.style.cursor = 'pointer'; | ||
|
||
slackButton.innerHTML = ` | ||
<img src="https://a.slack-edge.com/80588/marketing/img/icons/icon_slack_hash_colored.png" | ||
style="height: 1.4rem;" | ||
alt="Slack"> | ||
`; | ||
|
||
slackButton.addEventListener('click', () => { | ||
window.open('https://slack.vllm.ai', '_blank', 'noopener'); | ||
}); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider using an anchor (<a>
) tag instead of a <button>
element for navigation. This is more semantically correct and improves accessibility. Also, it's better to avoid inline styles and move them to the CSS file for better maintainability.
const slackButton = document.createElement('button'); | |
slackButton.className = 'slack-button'; | |
slackButton.title = 'Join us on Slack'; | |
slackButton.style.border = 'none'; | |
slackButton.style.background = 'transparent'; | |
slackButton.style.cursor = 'pointer'; | |
slackButton.innerHTML = ` | |
<img src="https://a.slack-edge.com/80588/marketing/img/icons/icon_slack_hash_colored.png" | |
style="height: 1.4rem;" | |
alt="Slack"> | |
`; | |
slackButton.addEventListener('click', () => { | |
window.open('https://slack.vllm.ai', '_blank', 'noopener'); | |
}); | |
const slackLink = document.createElement('a'); | |
slackLink.className = 'slack-button'; | |
slackLink.title = 'Join us on Slack'; | |
slackLink.href = 'https://slack.vllm.ai'; | |
slackLink.target = '_blank'; | |
slackLink.rel = 'noopener noreferrer'; | |
slackLink.innerHTML = ` | |
<img src="https://a.slack-edge.com/80588/marketing/img/icons/icon_slack_hash_colored.png" | |
alt="Slack"> | |
`; | |
cc @simon-mo are you ok with this? |
Personally I think the icon is a bit too big, it should have a similar size as the Git icon. |
Forum might be better for top level. Potentially both. |
Signed-off-by: reidliu41 <[email protected]>
c5caf00
to
926af7f
Compare
@DarkLight1337 updated, could you please take a look if you have time? thanks |
The Forum button looks a bit offset |
Signed-off-by: reidliu41 <[email protected]>
updated |
Can you move the icon downwards a bit? It doesn't look centered |
Signed-off-by: reidliu41 <[email protected]>
Moved it |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM now, thanks for adjusting the style!
Signed-off-by: reidliu41 <[email protected]>
Signed-off-by: reidliu41 <[email protected]> Signed-off-by: avigny <[email protected]>
Signed-off-by: reidliu41 <[email protected]>
Essential Elements of an Effective PR Description Checklist
supported_models.md
andexamples
for a new model.Purpose
Test Plan
Test Result
(Optional) Documentation Update