-
Notifications
You must be signed in to change notification settings - Fork 281
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
card collections/dashboard #1319
Conversation
Nice! :) Some design feedback:
|
Hi, we would love this collections/dashboard feature to go live for productive use. I don't quite get when we can expect that to happen. Would you be so kind as to give me any kind of estimation? We are using Deck 0.7.0 on Nextcloud 17 (stable). Thanks in advance! |
@ardarandir |
In addition to the comments by @jancborchardt I think we should try to keep the main content view stay in a similar card based layout as the regular board view has. I don't see a good use case for an all cards view, as this would basically be just a long endless list without any proper filtering. We should aim to provide lists that give users a good overview or help them to find the relevant cards more easily. Due date viewThe assigned to me list could also be grouped by duedates, as this is most likely what the priorization is done by. In addition we could allow users to apply custom filters on those lists with #414 cc @nextcloud/designers |
9e4415d
to
f5eae04
Compare
Rebased and changed base branch to master |
Signed-off-by: Jakob <[email protected]>
Signed-off-by: Julius Härtl <[email protected]>
f5eae04
to
ecc9b5c
Compare
Signed-off-by: Julius Härtl <[email protected]>
Not sure how you resolve conflicting feedback around here? Or is the only thing missing now the "Review required"? Thanks. |
No, we definitely should address the mentioned points before merging. 😉 |
Let's see if @jancborchardt and @nextcloud/designers have any comments on my additions. |
Agree with everything said by @juliushaertl in #1319 (comment) :) Only thing is that I’m not sure the list layout should use the card style, as that’s too many containers for a single-row layout. I tend towards doing it like @jakobroehrl above or as in the Tasks app. cc @raimund-schluessler as this now gets very close into the same territory as Tasks and we should coordinate how best to move forward together. :) As @jakobroehrl mentioned, the other tools all go in the direction of just having views for the "to dos", instead of different apps: See Microsoft Tasks in Teams, Asana, Ticktick, Todoist, Ora, Zenkit, … |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
Back to the original topic of the pull request, I would suggest we go for a card based approach as well for now, as once boards are exposed as calendars with #1545 we could redirect the user to the tasks app showing the cards in a list as a first starting point. |
This comment has been minimized.
This comment has been minimized.
There are a lot of the same functionality in Deck and Tasks eg:
I think it's easier to interate a list/table view in Deck than duplicate and maintain the hole functionality in two apps. |
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
This comment has been minimized.
So what will happen to this pull request? Merge or decline (if thats the right word)? Path1 Path2 Which path will we continue? (I am never sure how decisions are made here...) |
Well, the discussion drove a bit into details that are actually part of #15 but are of course related to the lists. My comment from #1319 (comment) still stands. So with that and the plan we came up with in #15 I think reusing the tasks app for any list view would make the most sense here.
We usually try to find a solution that is somehow common sense in the end. Let me quote our code of conduct here:
|
I think we drifted away from what this pull request was actually about - the dashboard to give quick access to important cards. Let me summarize what I think the consent was:
Open questions:Assigned to me
I was not arguing for a single row layout but to still provide some sort of grouping for the dashboard overview, like this:
|
Continued in #1934 |
Signed-off-by: Jakob [email protected]
Added some collections, and it's working so far :)
Could you give me your feedback @juliushaertl ?
Thanks a lot! :)
I think I would use this view in #1315, too.