Home page of the admin with plugin dashboard widgets

Open
#3,292 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
49/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Active
Tech stack
csharp

Research direction

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.

Written by the indexing model from the issue text.

Description

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.

Dominant language
C#
Stars
569
Forks
107
Avg merge
2h 49m
Merged PRs (30d)
397

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from fluentcms/FluentCMS

All issues in fluentcms/FluentCMS

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.