Use case or problem
The new Community Plugins site is nice to browse, but all you can really do when viewing a plugin as a user is install it immediately.
I’m not always able to immediately install a plugin, and don’t always have the time to devote to reading about a plugin to decide if I even want to install it. So, when I see a plugin that sounds interesting at a glance, it’s useful to save it for later when I can take a proper look at it and actually install it.
That isn’t currently possible without using external tools, which limits the usefulness of the site.
Proposed solution
The basic version: implement a “Favourites” system for plugins/themes, so that a logged-in user can click on the Favourite button to save that plugin or theme to their favourites list. A user can then view their favourites list in the browser to quickly re-discover plugins they’ve saved for later.
Other terms are available, e.g. “Bookmark” or “Save” or “Star 
” or “Heart 
”, etc.
A slightly more involved system could also include:
- Multiple user-defined “lists” for users to save their favourites into (eg. creating a list for “must-have plugins” that they might want to install in multiple vaults, a list for “writing plugins” for a writing-focused vault, and a list for “dev plugins“ for ) — like GitHub’s lists for starred repos.
- Integration with the Obsidian app itself: if a user has connected their account to the app, these favourites (and lists) could be exposed within the in-app plugin browser.
Current workarounds
- Manually bookmarking plugin pages in the browser (which won’t help if your browser doesn’t sync, or if you use different browsers on different devices).
- Manually visiting plugins on GitHub to star them and use GitHub’s lists feature to categorise plugin repositories (losing access to the info available on the plugins site, like screenshots and scorecards - also, clunky).
- Even more clunky methods like emailing or DMing yourself a link to something so that you can look at it again later.
Related feature requests
I couldn’t find any requests for something like this, or communication regarding future plans for the Community Plugins site (so if something similar is already planned, I’d appreciate a point in the direction of where to find information about planned features).