Media library of the admin: grid and list, folders, search, upload by drop and paste
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 35/100
Research direction
Start with docs/planning/admin-technical-spec.md, sections 4.14, 5.2 and 10.4, and the existing media routes and admin menu. Implementing this page spans browsing, uploads, folders, accessibility, and several kinds of tests; first check the dependency on A-19 and the related issues. Done means meeting the listed acceptance checks, including route contract tests against the OpenAPI document.
Written by the indexing model from the issue text.
Description
Problem
Row 3.15 asks for a media library, row 5.2 for upload by drag-and-drop and paste, and row 5.4 for folders. The media routes exist and the admin has no page over them: an asset is uploaded with the CLI or a direct call.
Proposal
The page /media of FluentCMS.Plugins.Media.Admin, with its menu item in the media section:
- A browse component, which the picker of A-20 reuses: grid and list views of a folder, the folder tree, search, filters by type and tag, and paging (
GET /media,GET /media/folders). The view, the folder and the filters are in the query string. - Upload by button, by dropping files on the page and by pasting. Each file shows its state (waiting, uploading, done, refused) and its refusal (
FCMS1581toFCMS1584) by name; a refused file does not stop the others. The state is per file and not per byte: the browser's fetch reports no upload progress, and the access token stays in C#. Drop and paste take a small script module of the half, which joins the allow-list of 3.1. - Folders: create, rename, move, and delete an empty one.
- Selecting an asset opens the detail panel of A-50; until it lands the panel shows the title, the type and the size.
Acceptance
- An editor browses folders, switches between grid and list, searches, filters by type and tag, and pages
- Ten files dropped at once upload with a state per file, and one of a refused type is named with its reason while the nine others finish
- An image pasted from the clipboard uploads into the open folder
- A folder is created, renamed, moved and deleted; deleting one with assets says why it is refused
- The page is usable by keyboard alone and passes the axe-core check in both themes and in the right-to-left pseudo-culture
- Component tests cover the browse component and the upload states; contract tests check the routes against the OpenAPI document (#3104); an end-to-end case uploads by drop and moves an asset's folder
Design: docs/planning/admin-technical-spec.md, sections 4.14, 5.2 and 10.4 (A-21). Rows 3.15, 5.2, 5.4. Needs A-19; #3100, #3103 and #3104 are merged. Size: M.
- Dominant language
- C#
- Stars
- 569
- Forks
- 107
- Avg merge
- 2h 49m
- Merged PRs (30d)
- 397
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the 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 fluentcms/FluentCMS
-
area:host area:operations type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:build security type:chore
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:sdk security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
-
area:content security type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
Maintainers usually reply within 1 day
-
area:build type:bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day
All issues in fluentcms/FluentCMS
Similar issues
-
bug needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
microsoft/microsoft-ui-reactor#1567 ·
Maintainers usually reply within 1 day
-
clawsweeper:fix-shape-clear clawsweeper:queueable-fix clawsweeper:source-repro impact:ux-friction issue-rating: 🦞 diamond lobster no-stale P2
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
openclaw/openclaw-windows-node#2287 · 2 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
kind:ux needs-triage
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
elsa-workflows/elsa-foundation#4742 ·
Maintainers usually reply within 1 day
-
priority:P2
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
enhancement good first issue help wanted new-language
Difficulty 2/5 1-3 hours Newbie friendliness 82/100