✔️ Deploy Preview for docsearch ready!

🔨 Explore the source changes: 23475f9

🔍 Inspect the deploy log: https://app.netlify.com/sites/docsearch/deploys/61a4ebf4e9ff330008631128

😎 Browse the preview: https://deploy-preview-1196--docsearch.netlify.app

This pull request is automatically built and testable in CodeSandbox.

To see build info of the built libraries, click here or the icon next to each commit SHA.

Latest deployment of this branch, based on commit 23475f9:

This is the kind of features that we want to be opinionated about, and not create disparities in the DocSearch ecosystem.

It's clearly the reason why I wasn't sure about adding it to the options, but it's requested quite frequently so it's better to have a public discussion.

On the other hand, I still think it's good to provide a bit of customization without having to re-implement the component.

We don't necessarily want to please everybody in all situations. The ⌘K pattern was fully studied and introduced with a clear plan in mind: democratize a mental pattern for developers when using docs. We don't want to send blurry signals and have developers wonder if hitting ⌘K would start searching or not. Our take is that it should. We shouldn't make it an option just because we can – options are the main path to confusion.

DX is also about constraints. If we don't recommend customizing the keyboard shortcut, we shouldn't make it easy to do so.

I did not had strong opinions on this, but I'll share what's top on my mind.

• If this has been requested, can we gather why it has been requested?
• k might already been assigned, if you have Docsearch on top of VSCode for example.
• k might not fit all lang (I don't know about asian languages but I guess there might be an issue here)
• Docsearch is a tool not a standard imo, having a good DX by default should not disallow customisation, and I'm sure it will be okay for 99% of the implems.
• "Command palette" pattern is more and more prevalent in SaaS, it might be a blocker to integrate Docsearch, but in that case they might want to remove have their own search anyway.

My 2 cents on this.

Agree with Francois, low level customization should be enough in that case.

options are the main path to confusion.

I agree and this is why I wanted to have this open to a possible debate.

DX is also about constraints.

This is exactly why I first doubted when opening this PR, but we have developers with different background using our tool. While providing the best DX (by default in that case) is obviously our concern, we should also ease their journey when they want to move out of our constraints.

low level customization should be enough in that case.

I'd also add that almost half of our users are using website generators and only see DocSearch components through their website config file, providing an option at this level is also a great DX improvement.

If we all have different opinions we need facts:

why it has been requested?