Home page of the admin with plugin dashboard widgets

オープン
#3,292 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
4/5
見積もり時間
3〜5日
初心者へのやさしさ
49/100
issue の種類
機能追加
明瞭さ
おおむね明確
活発さ
活発
技術スタック
csharp

調査の方向性

Read docs/planning/admin-technical-spec.md sections 5.1 and 10.4 (A-22), then trace the admin home page and the media plugin manifest for dashboard widget entry points. The issue also depends on A-19; #3096 is merged. Done means the widget grid, permission and plugin gating, error tile, responsive and right-to-left behavior, accessibility check, and component and end-to-end coverage meet the listed acceptance criteria.

索引モデルが issue の本文から書いたものです。

説明

area:admin type:feature

Problem

Row 8.9 asks that a plugin adds widgets to the dashboard, each visible by permission or role. The home page of the admin is a placeholder, and nothing renders a [DashboardWidget].

Proposal

  • The home page lays out the widgets of the manifests in a grid by their size hint (small, medium, wide), in a stable order: by plugin name, then by the order of the manifest.
  • A widget is shown only while its plugin is enabled in the site and the caller holds its permission or role (#3096); its half is loaded when the home page shows it, and a widget that is not visible loads nothing.
  • A widget that fails to load or throws shows an error state in its own tile, and the others render.
  • Core's own tiles: the content types the caller may read, as links to their lists. With no widget and no type the page says so.
  • The media half declares one small widget, the latest uploads, so that the page is proven on a real half.

Acceptance

  • With the media plugin enabled the home page shows its widget; in a site where it is disabled the widget is absent and the half is not fetched
  • A caller without the widget's permission does not see it
  • A widget that throws leaves the rest of the page working
  • The grid reflows on the tablet layout, follows the right-to-left pseudo-culture, and passes the axe-core check in both themes
  • Component tests cover the order, the gating and the error tile; an end-to-end case covers the enabled and the disabled site

Design: docs/planning/admin-technical-spec.md, sections 5.1 and 10.4 (A-22). Row 8.9. Needs A-19; #3096 is merged. Size: S.

主要言語
C#
スター
569
フォーク
107
平均マージ
2時間 49分
マージ済み PR(30日)
397

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

fluentcms/FluentCMS のほかの issue

fluentcms/FluentCMS の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。