Category description and image: build or drop #39

Closed
opened 2026-11-02 14:12:40 +01:00 by miko · 1 comment
Owner

Part of #1

Problem

Category.description (Editor.js JSON) and Category.image exist in the schema (#6) but no UI sets or shows them. #6 handed the description to #8 and the image to #11; neither was picked up, and #18 added cover images for guides only. Neither field is named in the PRD's v1 scope.

Acceptance criteria

  • Decide per field: in v1 or not
  • If in: admins edit it in the category form; the category page renders the description with the own renderer (ADR-0005); the image goes through the shared image module and /media with the category's effective visibility (ADR-0006)
  • If not: drop the column with a migration
Part of #1 ## Problem `Category.description` (Editor.js JSON) and `Category.image` exist in the schema (#6) but no UI sets or shows them. #6 handed the description to #8 and the image to #11; neither was picked up, and #18 added cover images for guides only. Neither field is named in the PRD's v1 scope. ## Acceptance criteria - [ ] Decide per field: in v1 or not - [ ] If in: admins edit it in the category form; the category page renders the description with the own renderer (ADR-0005); the image goes through the shared image module and `/media` with the category's effective visibility (ADR-0006) - [ ] If not: drop the column with a migration
Author
Owner

Decided: both fields are in v1. Description is edited in the category form (Editor.js) and rendered on the category page (ADR-0005); the image is a CategoryImage table like CoverImage, served through /media by the category's effective visibility (ADR-0006). Implemented in #41.

Decided: both fields are in v1. Description is edited in the category form (Editor.js) and rendered on the category page (ADR-0005); the image is a CategoryImage table like CoverImage, served through /media by the category's effective visibility (ADR-0006). Implemented in #41.
miko closed this issue 2026-11-02 18:50:06 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
MassiveDynamic/kataba#39
No description provided.