Skip to content

[Doc] cmd+k #19957

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

Closed
wants to merge 7 commits into from
Closed

[Doc] cmd+k #19957

wants to merge 7 commits into from

Conversation

aarnphm
Copy link
Collaborator

@aarnphm aarnphm commented Jun 22, 2025

This PR add supports for focusing search with [cmd|ctrl]+k

Signed-off-by: Aaron Pham [email protected]

Signed-off-by: Aaron Pham <[email protected]>
@aarnphm aarnphm requested a review from hmellor as a code owner June 22, 2025 21:51
Copy link

👋 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 fastcheck CI which starts running only a small and essential subset of CI tests to quickly catch errors. You can run other CI tests on top of those by going to your fastcheck build on Buildkite UI (linked in the PR checks section) and unblock them. If you do not have permission to unblock, ping simon-mo or khluu to add you in our Buildkite org.

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 ready label to the PR or enable auto-merge.

🚀

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a 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 @aarnphm, 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 new keyboard shortcut (cmd+k / ctrl+k) to quickly focus the search input field within the documentation, enhancing user experience and navigation efficiency. It also adds a visual indicator to make this new feature discoverable.

Highlights

  • New Keyboard Shortcut: I've added support for focusing the search bar in the documentation using the cmd+k (on macOS) or ctrl+k (on Windows/Linux) keyboard shortcut. This improves accessibility and speed for users navigating the documentation.
  • Visual Hint for Search: To inform users about the new shortcut, I've implemented a visual cue that displays 'cmd+k' next to the search input field when it's not active. This makes the shortcut discoverable.
  • MkDocs Configuration Update: The new JavaScript file containing the shortcut logic has been integrated into the MkDocs configuration (mkdocs.yaml) to ensure it's loaded and active on 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

  1. 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.

@mergify mergify bot added the documentation Improvements or additions to documentation label Jun 22, 2025
Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds support for focusing the search bar using the Cmd/Ctrl+K keyboard shortcut. To improve the user experience, consider dynamically displaying the correct keyboard shortcut (cmd+k for macOS, ctrl+k for Windows/Linux) in the UI by using a CSS variable and JavaScript to detect the user's OS.

font-size: .8rem;
border: .05rem solid var(--md-default-bg-color--lighter);
border-radius: .1rem;
content: "cmd+k";
Copy link
Contributor

Choose a reason for hiding this comment

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

medium

Consider using a CSS variable for the content property to dynamically display the correct keyboard shortcut based on the user's OS. This avoids hardcoding cmd+k which is specific to macOS. The JavaScript can then set the appropriate value for the variable based on the user's platform.

Suggested change
content: "cmd+k";
content: var(--md-search-shortcut);

@DarkLight1337
Copy link
Member

The shortcut doesn't seem to work as Ctrl+K focuses on the browser's search bar instead.

@aarnphm
Copy link
Collaborator Author

aarnphm commented Jun 23, 2025

yeah i realized.

@aarnphm aarnphm requested a review from DarkLight1337 June 23, 2025 20:55
Copy link
Member

@DarkLight1337 DarkLight1337 left a comment

Choose a reason for hiding this comment

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

Ctrl+K still doesn't work on my end (I'm on Windows). I also tried Alt+K and it doesn't work either

if (event.key === '/') {
// we actually don't want to bind this key on docs given that it uses builtin mkdocs search.
event.preventDefault();
} elif ((event.altKey || event.metaKey) && event.key === 'k') {
Copy link
Contributor

Choose a reason for hiding this comment

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

seems use alt + k, @DarkLight1337

@aarnphm
Copy link
Collaborator Author

aarnphm commented Jun 24, 2025

Can u try force refresh all cache?

@DarkLight1337
Copy link
Member

Yeah, I tried that already

Signed-off-by: Aaron Pham <[email protected]>
@aarnphm
Copy link
Collaborator Author

aarnphm commented Jun 24, 2025

Ok, I think it might be because of the css haha

@DarkLight1337
Copy link
Member

Still doesn't work. Btw, I think the keyboard shortcut might be a bit redundant because simply typing anything on the page opens the search bar...

Signed-off-by: Aaron Pham <[email protected]>
@aarnphm
Copy link
Collaborator Author

aarnphm commented Jun 24, 2025

I don't have a strong opinion on this.

@DarkLight1337
Copy link
Member

Alt+K still doesn't work

@aarnphm
Copy link
Collaborator Author

aarnphm commented Jun 25, 2025

ah I'm just going to close this PR for now.

@aarnphm aarnphm closed this Jun 25, 2025
@aarnphm aarnphm deleted the chore/cmd-k branch June 25, 2025 04:38
@@ -0,0 +1,13 @@
document.addEventListener('keydown', function (event) {
if (event.key.lower() === '/') {
Copy link
Contributor

Choose a reason for hiding this comment

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

should be toLowerCase()

if (event.key.lower() === '/') {
// we actually don't want to bind this key on docs given that it uses builtin mkdocs search.
event.preventDefault();
} else if ((event.altKey || event.metaKey) && event.key.lower() === 'k') {
Copy link
Contributor

Choose a reason for hiding this comment

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

should be toLowerCase()
@DarkLight1337 i test work in mac and or win

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants