Problem Statement
There are a number of useful stats and figures that Camille and content editors would find useful to prioritise content editing tasks.
Sanity offers a "Dashboard" tool that we have already set up within the Studio as a "POC" (proof of concept).
The Dashboard embeds self-contained "widgets" to arrange and present custom content which seems like an ideal solution to this problem.
This issue is to create and embed several widgets in the Dashboard.
Acceptance Criteria
A bunch of widgets embedded in the Dashboard including:
[x] #101
Total number of resources (internet resource document types + website + crisis)
sub-totals breakdown by document type
[x] #102
How many documents are published
How many documents are unpublished
How many documents have changes awaiting review
breakdowns by document type (internet resource types + website + crisis)
[ ] #103
How many resources are present in each category
As there are a ton of categories consider how best to present it without it feeling cluttered; for example show Top 10 (no. 1 having most resources) with an expandable accordion-like section of user wants to drill down? Or maybe a category tree with a counter next to each?
Considerations
UI requirements are flexible and design and layout is left to the implementer - however we should stick to Sanity UI where possible (already added as a dependency)
Problem Statement There are a number of useful stats and figures that Camille and content editors would find useful to prioritise content editing tasks.
Sanity offers a "Dashboard" tool that we have already set up within the Studio as a "POC" (proof of concept).
The Dashboard embeds self-contained "widgets" to arrange and present custom content which seems like an ideal solution to this problem.
This issue is to create and embed several widgets in the Dashboard.
Acceptance Criteria A bunch of widgets embedded in the Dashboard including:
[x] #101
[x] #102
[ ] #103
Considerations
UI requirements are flexible and design and layout is left to the implementer - however we should stick to Sanity UI where possible (already added as a dependency)
Relevant docs: https://www.sanity.io/docs/dashboard
https://www.sanity.io/docs/creating-your-own-widget
Sanity UI:
https://www.sanity.io/ui