nextcloud / nextcloud/deck

Relocate 'Delete Board' Button in Deck for Improved UX

Open
#5,332 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Summary

This issue requests a user experience (UX) enhancement in the Deck application. The current placement of the 'Delete Board' button poses a risk of accidental board deletions.

Description

In the current Deck layout, the 'Delete Board' button is located adjacent to the board's name, within the quick access area. This proximity increases the likelihood of unintentionally clicking the 'Delete Board' option, despite the presence of a verification dialog.

Suggested Solution

  • Relocate the 'Delete Board' Button: It is proposed to move the 'Delete Board' button to a more deliberate location, such as the right-hand side of the interface, away from frequently used controls.
  • Rationale: This change would minimize accidental clicks, thereby enhancing the overall user experience and reducing the risk of unintentional board deletions.

Expected Benefits

  • Reduces Accidental Deletions: By relocating the button, users are less likely to accidentally delete a board.
  • Enhances User Experience: A more intuitive layout increases user satisfaction and trust in the application.
  • Maintains Functionality: This change would not affect the core functionality of the Deck application.

Additional Context

This enhancement is in line with general UX design principles that recommend separating destructive actions (like deletion) from regular, frequently used controls.


I hope this format meets your requirements for submitting an issue to GitHub regarding the UX functionality in Deck.
Captura de pantalla 2023-11-27 a las 22 26 33

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

No files, tests, or entry points are mentioned. Start by locating the Deck board header and quick-access controls, then review how the Delete Board action is positioned and rendered. Done means the destructive control is moved away from the board name while remaining functional and accessible.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
design, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.