nextcloud / nextcloud/server

Make smart picker symbol more visible and consistent

Open
#60,155 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage design enhancement
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

[!TIP]

Help move this idea forward
  • Use the 👍 reaction to show support for this feature.
  • Avoid commenting unless you have relevant information to add; unnecessary comments create noise for subscribers.
  • Subscribe to receive notifications about status changes and new comments.

Is your feature request related to a problem? Please describe.
The smart picker is great to connect resources from different apps in Nextcloud. However, finding it besides the / command is sometimes a little bit difficult, because it is hidden behind menus.

Describe the solution you'd like

  1. Make the / the uniform icon for the smart picker. So far, this is just the case for Office. Since this icon would be more connected to the command itself, it would be easier to understand.
  2. Move the smart picker at the top level in the menu in the text editor. This would make using the smart picker way friendlier for people using UI elements.

Describe alternatives you've considered
Just use the command which is fine for tech-savvy people, but people only working with the UI have no quick access to the smart picker.

Additional context

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the smart picker controls in the text editor and comparing them with the Office interface. Check how the picker icon and menu placement are defined; done means the slash icon is used consistently and the picker is available at the text editor's top-level menu.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
design, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
55/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.