Feature Request: Official plugin manifest / browser for discovery, explanation and one-click install
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 30/100
Research direction
No implementation files, tests, or entry points are identified in the issue. Start by defining whether the first deliverable is a plugins.json manifest, a browser page, or an API, then agree on the metadata fields and plugin status rules; done means an official structured catalog is available for discovery and future tooling.
Written by the indexing model from the issue text.
Description
Is your feature request related to a problem? Please describe.
Yes.
The current plugin discovery and installation flow is still too manual and fragmented. Users need to browse the plugin list page, open external release pages, compare plugins by themselves, and then download and install each plugin manually.
This causes several problems:
- It is inconvenient to discover available plugins in one place.
- Similar or overlapping plugins are hard to compare.
- It is not easy to understand what each plugin does before opening its page.
- Legacy, deprecated, or replacement plugins are not clearly structured for users.
- There is no simple way to automatically fetch plugin metadata for external tools or future in-app integration.
Describe the solution you'd like
I would like QuickLook to provide an official machine-readable plugin catalog, such as a plugins.json manifest, or an official plugin browser page/API.
Each plugin entry could include fields like:
- name
- repository
- description
- supported file types / extensions
- latest version
- release page
- direct download URL
- maintained / deprecated status
- replacement plugin (if any)
- compatibility notes
- short explanation of why a user might choose this plugin
With this, QuickLook could support:
- easier plugin listing and search
- clearer plugin explanations
- filtering by file type or category
- one-click download / install / update in the future
- easier support for third-party tooling and automation
Describe alternatives you've considered
One alternative is to keep using the current wiki page and manually open each plugin page when needed.
Another alternative is to build an external script or scraper that parses the plugin list page and extracts plugin information automatically. However, this is less reliable, harder to maintain, and depends on page structure instead of an official stable format.
Because of that, an official manifest or structured plugin catalog would be a much better long-term solution.
Additional context
This request is not only about convenience for manual users, but also about future extensibility.
If QuickLook provides an official structured plugin source, it would make it possible to build:
- better plugin discovery tools
- automatic plugin listing and explanation
- update checkers
- possible in-app plugin installation in the future
Even if full one-click installation is not implemented immediately, having an official structured catalog would already be a big improvement.
- Dominant language
- C#
- Stars
- 25.8k
- Forks
- 1.4k
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 3
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from QL-Win/QuickLook
-
遇到超大文件会卡住Open
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 4 days
-
[MarkdownViewer] Mermaid classDiagram with <<annotation>> fails with "Syntax error in text"Possibly taken @suhyun-nam claimed this 13 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
QL-Win/QuickLook#2028 · 3 comments ·
Maintainers usually reply within 4 days
-
[Bug] If the first character entered into the search box is a space, the preview window will close.Possibly taken @MORTEM3845 claimed this 27 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 4 days
-
[Crash] Fatal CLR error (80131506) previewing any SVG when WebView2 controller creation fails — initialization failure is silently ignoredPossibly taken @Henglie claimed this 14 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 48/100
QL-Win/QuickLook#2057 · 1 comment ·
Maintainers usually reply within 4 days
All issues in QL-Win/QuickLook
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Maintainers usually reply within 1 day
-
Bug IronPython Python 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyrevitlabs/pyRevit#4184 ·
Maintainers usually reply within 1 day
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
yusei36/KeePassPasskey#66 · 2 comments ·
Maintainers usually reply within 1 day
-
🐛 bug 🕒 low effort good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
guibranco/Sankhya-SDK-dotnet#654 ·
Maintainers usually reply within 1 day
-
巫女のセリフに声を付けるOpenassets claude-proposal
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
Fialuxe/MouthOfGod_System#358 ·
Maintainers usually reply within 1 day