Media field editor, list cell and media picker of the admin

Open
#3,289 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
48/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Active
Tech stack
csharp, openapi, tailwindcss

Research direction

Read docs/planning/admin-technical-spec.md sections 5.2 and 10.4, then inspect the media admin components and FieldEditorBase; the issue names no implementation files or test paths. Check the merged prerequisites A-19, A-21, #3100, #3103 and #3104 before starting. Done means the picker, media field editor and list cell meet the acceptance checks, including keyboard access, route contract tests and the Article.Hero end-to-end case.

Written by the indexing model from the issue text.

Description

area:admin type:feature

Problem

Row 3.10 asks for a media picker and row 1.4 for media fields. A media field of a form shows its JSON read-only, a list shows the same in its cell, and an editor cannot set the image of Article.Hero.

Proposal

In FluentCMS.Plugins.Media.Admin:

  • IMediaPicker: a dialog over the library with the folder tree, search, upload inline and single or multiple selection, limited to the types the field allows. It reuses the browse component of A-21. Declared with [AdminService], so asking for it loads the half.
  • The field editor of media: a thumbnail with pick, upload, remove, and reorder for a field with several assets; alt text and focal point editable in place with the components of A-50 (PATCH /media/{id}). Read-only, errors, locale and direction as FieldEditorBase gives them.
  • The list cell of media: a thumbnail, with a count for several.
  • Thumbnails from the urls of the Management reads (#3100); labels of the assets of a list are read with one call, not one per row (2.7).
  • The field and the cell fall back to the read-only JSON when the plugin is disabled in the site.

Acceptance

  • On the Blog sample an editor picks an image for Article.Hero from the library, uploads another from the picker, removes it, saves, and the list shows the thumbnail
  • A field that allows images only refuses a PDF in the picker and in the upload
  • Alt text and focal point changed from the field are saved on the asset
  • The picker and the field are usable by keyboard alone, and pass the axe-core check in both themes
  • The built-in Editor and Author pick and upload (#3103)
  • Component tests cover the editor, the cell and the picker; contract tests check the media routes it calls against the OpenAPI document (#3104); an end-to-end case sets the image of Article.Hero

Design: docs/planning/admin-technical-spec.md, sections 5.2 and 10.4 (A-20). Rows 3.10, 1.4, 5.7. Needs A-19 and A-21; #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

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.