Skip to content

[Feature]: Local image attachments on tasks + optional subtle card cover from first image #11

Description

@rosspeili

One-line summary

Attach images via local paths; optionally wash the first image as a very subtle background on task cards.

Problem / motivation

Tasks often need a sketch, screenshot, or photo. Cloud uploads are out of scope; local references keep HPPM offline. Optionally, cards with attachments can show a very subtle first-image wash behind content.

Proposed solution

Drawer field

  • List of local images; prefer copying into a project-managed folder (e.g. .hppm/attachments/<issueId>/).
  • Store paths in .hppm/store.json (not base64 blobs).
  • File picker add/remove; thumbnails; open with OS viewer or simple lightbox.

Cards (optional)

  • Kanban/Fruits (at least Kanban for v1): first image as very low-opacity wash behind card content; text stays readable.
  • Preference toggle if noisy (cardImageWash).

Implementer notes: Spike path strategy first; sanitize paths (stay under project root); gitignore guidance for attachment folders; image types png/jpg/webp/gif; design pass per light/dark themes. Out of scope: video/PDF; cloud sync; AI tagging.

Alternatives considered

  • Markdown image links only in notes (weaker UX, no card wash).
  • Base64 in store (rejected — bloat).

Primary surface

Task drawer

Constraints you accept

  • Must stay local-first (no required cloud account)
  • Should not break existing tracker *.md readability

Mock / sketch / reference (optional)

Drawer “Attachments” row with thumbs; Kanban card with soft faded photo behind title/tags at ~5–15% opacity.

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:drawerTask drawer — fields, edit, delete, notesarea:store.hppm store, fingerprints, preferences, registryarea:viewsOverview, Table, Kanban, Timeline, Neural, FruitsenhancementNew feature or improvement requestneeds designNeeds UX / visual decision before implementation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions