feat: Implement a command palette with Ctrl-K shortcut

[juliusknorr]

Signed-off-by: Julius Knorr jus@bitgrid.net

📝 Summary

This is a common feature in IDEs and also other tools like Notion, for Nextcloud this has only been discussed in nextcloud/notes#1200

This is a first attempt out of personal need to implement this in collectives.

Also pulling in @marcoambrosini for some design feedback and to check if something like this was discussed in other places in the design team as well.

Currently implemented

Navigation

• Search and jump to any page or collective
• Cross-collective page search

Commands:

• Create new page/collective
• Switch edit/view mode
• Toggle outline and full-width view
• Favorite/unfavorite pages
• Share, set emoji, manage tags
• Move/copy/download/delete pages

🖼️ Screenshots

Kapture.2025-12-31.at.13.39.41.webm

🏁 Checklist

• Code is properly formatted (npm run lint / npm run stylelint / composer run cs:check)
• Sign-off message is added to all commits
• Tests (unit, integration and/or end-to-end) passing and the changes are covered with tests
• Documentation (README or documentation) has been updated or is not required

[Aveyron-RetD]

Sorry for the noise.
That is so cool 👀 but.... should this palette interact with the other apps instead of the collectives app.

Like a smartpicker, but the action is not inserted in the actual page but in the target=> Add a reminder, create a deck card, message a friend add something on your calendar.

Like be in mail summon this palette => Create a deck card which has a link to the mail
Like be in deck => Create a meeting which has a link to the deck card
Be in collectives => Send to chat the page is linked to a chat

Productivity 🚀 🚀

[marcoambrosini]

Amazing stuff @juliusknorr <3

A couple of comments from my side:

• We don't need a dialog for this title, the input label is enough
• In the screencast, the height of the dialog varies depending on the search results list. Would it be possible to make the dialog's height fixed? Or maybe even better we could have the height change depending on the results, but only "cut the container from the bottom" and have the search field itself fixed in place on the page.

Edit: sorry for the ping different Julius

[juliusknorr]

Different julius pinged but, I'll look into those.

@marcoambrosini Regarding the comment from @Aveyron-RetD I think this is an interesting idea worth to discuss with the other designers or in planning calls if we think this is interesting for all apps, but we could start with collectives to try this out in daily use and then learn from it for a more global implementation in a next round.

[juliusknorr]

@marcoambrosini Adjusted

Also set to ready for review for some code feedback from the others ;)

[marcoambrosini]

@juliusknorr writing to you from design team meeting. Everyone likes it a lot :)

A couple of things that came up, both non blocking:

• The sub-lines of the commands are a bit redundant. What do you think about removing those?
• It would be nice if there was a hint about this somewhere in the UI, maybe the main landing page after first run? Or there could be a shortcut section in the settings like in talk

@Aveyron-RetD regarding connecting this with other apps commands and resources, we agree that that could be really good eventually, but we prefer to start small and test this out in collectives first. This would already be very useful in its current form.

also ping @jancborchardt for when you're back from vacation :)