processing / processing/p5.js-web-editor

Enhancement: Bulk Asset Management (Pagination + Multi-Select Delete)

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

Nobody has claimed this yet.

Enhancement Help Wanted
Dominant language
JavaScript
Stars
1.7k
Forks
1.7k
Avg merge
3d 4h
Merged PRs (30d)
8

Description

Increasing Access

Currently, the Assets tab lists all uploaded assets in a single, continuous list with no pagination or bulk actions.

This creates multiple issues:

  • Users have a hard storage limit (250 MB) and must manually clean up assets.
  • Assets can only be deleted one at a time, which becomes tedious as the list grows.
  • No way to efficiently manage or clean up old/unused assets.
  • Performance and usability may degrade for users with many assets.

Current Behaviour
Assets are displayed in a long list.
Each asset has an individual dropdown with a “Delete” action.
No pagination, no multi-select, no bulk actions.

Image
Feature enhancement details
1. Pagination or Infinite Scroll
  • Introduce pagination (e.g., 20–30 assets per page), or
  • Use infinite scrolling with lazy loading.
  • Improves performance and readability for large asset collections.
2. Multi-Select with Checkboxes
  • Add a checkbox for each asset row.
  • Add a “Select All” checkbox in the table header.
  • Allow selecting multiple assets at once.
3. Bulk Actions
  • Enable Bulk Delete for selected assets.

  • Optional future enhancements:

    • Bulk download
    • Bulk detach from sketches (if applicable)
4. Confirmation & Feedback
  • Show confirmation modal before bulk deletion.

  • Clear messaging like:

    “You are about to delete 12 assets. This action cannot be undone.”

  • Show success/error feedback after action completion.

💡 Why This Matters
  • Helps users stay within storage limits more easily.
  • Greatly improves usability for power users and educators.
  • Reduces repetitive actions and frustration.
  • Aligns with common UX patterns in asset/file managers.

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating the Assets tab implementation and its existing per-asset Delete action. Define the pagination or infinite-scroll approach, checkbox selection, bulk-delete confirmation, and success/error feedback; done means users can manage many assets and delete selected assets safely.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
frontend
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.