nextcloud / nextcloud/deck

Usabilty enhancements consistent with Nextcloud: Set start page and unsubscribe

Open
#4,017 0 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement feature: upcoming cards
Dominant language
JavaScript
Stars
1.4k
Forks
354
Avg merge
1d 10h
Merged PRs (30d)
43

Description

DECK basically is great but in multiuser environments it can become overcrowded if the number of assigned decks becomes huge with some inconvenient consequences.

Some enhancements could resolve that:

  1. Whenever one opens deck 'Upcoming cards' is shown. Depending on usage this may become nasty. There shoud be an option to set 'Upcoming cards', 'All board' or an individual board as startup page.

  2. Unlike in calender it is not possible to hide shared decks. If there are many users with many boards and they all share with you as team leader things will get messed up. It would help a lot if there was not only a group 'All boards' and 'Shared with you' but also 'My boards'. 'My boards' might be an additional group or replace 'All boards'.

  3. The option to 'Show boards in calender/tasks' should be individual for single boards. Having dozends or hundreds of shared boards in calendar/tasks is not really useful.

  4. Also one should have the possibility to unsubscribe from shared boards as is in file-sharing to prevent being spammed from cloud users who think thier boards are important for you while you don't ...

Thanks and best
Nikolaus

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 tracing the Deck UI entry points for the startup page, board grouping, calendar/tasks visibility, and shared-board membership. Clarify the desired settings and behavior for each of the four requests, then verify that preferences and unsubscribe actions work consistently across the affected views.

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
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.