Skip to content
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

Chapter progress overview #66

Open
dafrie opened this issue Jan 8, 2021 · 0 comments · May be fixed by #68
Open

Chapter progress overview #66

dafrie opened this issue Jan 8, 2021 · 0 comments · May be fixed by #68
Assignees
Labels
good first issue Good for newcomers

Comments

@dafrie
Copy link
Member

dafrie commented Jan 8, 2021

Goal

The chapter overview should obviously be more informative than the current status. It would be nice, if the card would show the user a quick overview on the current state of the chapter and ideally this overview is role dependent (see the mockup description on the right).

The idea would be to have multiple sections within each card, the first section would list for each root component type of this chapter the total number of occurrences in the chapter, ideally grouped by status as shown in the mockup.

In the second section the translation progress for each language could get rendered for example.

Mockups

https://drive.google.com/drive/u/0/folders/1WIyKWdV41zwW5ijMIv5brCX-dheqHQWw
image

Ideas for an approach

I guess it probably makes sense to make an encapsulated component for each section and then have a query for each card (even if this is not very efficient as we won't have that many chapters).

To get the list of component types per chapter with the associated counts, the api_componenttype type could be queried with its 1:n relation to api_component and filter by chapter (directly via GraphQL).

For the grouping by status, I think this a bit more tricky since the status needs to get calculated for the whole tree and
therefore I guess it makes sense to add a database view for this functionality. I would therefore suggest to ignore the grouping by status for now and just render the total count per component type....

@dafrie dafrie added the good first issue Good for newcomers label Jan 8, 2021
@kimbylr kimbylr self-assigned this Jan 10, 2021
@kimbylr kimbylr linked a pull request Jan 10, 2021 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
good first issue Good for newcomers
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants