Deck [design review call]
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 1.4k
- Forks
- 354
- Avg merge
- 1d 10h
- Merged PRs (30d)
- 43
Description
Important: ensure that when it applies, changes are also reflected on the mobile apps
First load and dummy data
- First load of the app: load personal view instead of upcoming cards
- Dummy data: come up with more relevant cards
- Tutorial tasks as one idea like other tools do it
Search and filtering
- Search should go to the top of the navigation
- We can filter the navigation
- Then we don't need the headings anymore
- We could have quick filters that apply to the list
- We should search for boards and cards like talk does
- Remove the global serach in the bottom content area
- Epic: Search and filtering needs some bigger design discussion
- Smaller things filter menu
- Label filter button in the top right if space is available
- Headings are a bit too big
- Tag list might be better to switch to a multiselect or have a filter -> bigger discussion as ewll
Settings
-
Settings
- Move to a settings dialog
- Keyboard shortcuts already has a dialog
-
Add board input. can stay for now
-
Skipped discussing modal due to https://github.com/nextcloud/deck/issues/2702
-
Big button to the right of the last list to create new one (still keep an )
-
[ ]Button to create new card: same behaviour as trello, screenshots below
✅ Done
Before starting a new design review, move all completed items into this bucket
Placeholder
🗓️ Reviews done:
2024/12/17cc @juliusknorr
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the checklist and the linked search-and-filtering issue, #5990, then clarify which navigation, search, filtering, settings, and card/list creation items are in scope. No source files or tests are named; done means implementing the agreed design-review changes, reflecting applicable changes in the mobile apps, and moving completed items into the Done section.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- design, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100