Discoverability of features/commands #1555
Description
Discussed in https://github.com/orgs/albertlauncher/discussions/1420
Originally posted by rsyring August 13, 2024
Is there a way to make discoverability of plugin features easier?
My current case in point is the snippets plugin. I've been trying to come up with an easier way to quickly add a snippet so I started looking at the source code. I discovered "snip" was a query trigger, but I had no idea that was how it worked. I had always just searched for a snippet by name, it came up, and I selected it to get it into the clipboard.
While writing this issue, I just took a closer look at the query tab and realized it was getting updated after plugins are activated. Can't believe I didn't realize that was there sooner. :o/
So, "snip +" will let me add a new one snippet. The source of the plugin makes me think I should be able to choose to edit one too, but I can't seem to find the way to trigger that alternative action if it exists.
But the bigger issue then is discoverability. I wonder how many cool features are hidden in Albert and its ecosystem but no one uses them b/c there its no easy to learn about them.
Two other plugins: "PATH" and "Kill Process" have no explanation on how to use them. I can move over to the query tab after activating them and see if a new query is available. But what about any extra functionality?
Or the Documentation plugin. I just tried it and installed the Python docs. But "docs pathlib" doesn't return anything about the pathlib module, so I don't know what to do with it next.
Maybe each plugin could have the option to include a readme.md that would be shown in the Albert settings UI? Maybe some things that are programmatically available, like the query or alternate actions, could be automatically shown as part of the built-in docs for the plugin which would be displayed with any readme content?
Just some ideas. :) Love Albert. Thanks for all the effort you've put into it!