Feature Request: Official plugin manifest / browser for discovery, explanation and one-click install

未關閉
#1,908 0 則留言 1 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 4 天內回覆

還沒有人認領這個 Issue。

評估

難度
5/5
預估耗時
一週以上
新手友好度
30/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
冷清
技術堆疊
csharp
領域
tooling

研究方向

Issue 中沒有確定實作檔案、測試或進入點。首先確定第一個交付物是 plugins.json 清單、瀏覽器頁面還是 API,然後就中繼資料欄位和外掛程式狀態規則達成共識;當一個官方結構化目錄可供探索及未來工具使用時,即表示完成。

由索引模型根據 Issue 內容生成。

描述

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.

主要語言
C#
星號
25.8k
分支
1.4k
平均合併
3 天 19 小時
30 天內合併 PR
3

環境準備

  • 沒有 Dockerfile 或 Docker Compose 檔案
  • 有 Pull Request 範本
  • 沒有貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

QL-Win/QuickLook 的其他 Issue

查看 QL-Win/QuickLook 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。