Reference Documents
Product Scope: Finances V2.0
Figma for Finances 2.0: https://www.figma.com/file/96NZ02oYe3jpet1roUp0s0/Mockups?type=design&node-id=1712%3A37203&mode=design&t=TZv4RspCOzxhLiVQ-1
Previous sprint technical documents:
Sprint 68: Manage custom expense types tasks
...
I suggest we use the package ExcelJS (https://github.com/exceljs/exceljs) to generate our xlxs document. It is a popular packages with close to 1 million weekly downloads (npm), has a readable API and the generated spreadsheet is fully styleable
The most popular alternative, SheetJS, has recently moved off of GitHub,
It is a large package, 1.1MB minified and 259.1kB minified and gzipped according to Bundlephobia
As a point of comparison, a single sheet xlsx file as we generate in certification export is 8-9kB. This suggests we should be creating the xlsx file on the server and sending via API to the frontend. However there are some other considerations we can keep in mind.
We don’t yet know the specifications of the file we will be generating (e.g. I believe they will be more highly styled than the certification documents) and they may end up larger
The client can cache the library code, making the difference in data sent to the client less noticeable as more documents are exported
This might be worth testing on different devices in terms of responsiveness
We don’t yet have the exact specification for this document (data content or visuals), but we can set up the framework (saga → controller → document generation → download) now with any data available in the current finances page
Dashboard Views
This rework is considerable but should happen entirely on the frontend (no full-stack tickets)Although this rework is visually substantial, for the most part all of the data is already present within the existing summary views
We are still waiting for some designs to be confirmed as final, so we will work on conservative parts of the design this sprint
...
...
M: must have N: nice to have
...
tasks
...
...
1
...
2
...
3
...
...
4
...
the most conservative
Note on the Figma Mockup: we are using the second panel of “Finances homescreen” as our current guide for the main dashboard, with the addition of the date filtering from the third panel
| tasks | notes | |
|---|---|---|---|
1 | Preliminary Dashboard Task | Convert the following class-based components into functional components:
| |
2 |   | Create reusable summary tile component | |
3 | |||
4 | |||
5 | |||
6 | |||
7 |
| ||
8 |
| ||
9 |
| ||
10 |
| ||
|
|
Questions & Answers
What’s the relationship between the old Labour view and the new Labour expense tile? Is there a migration covering this? For now is the old Labour summary view removed?
Is estimated revenue removed?
Does document export need to be recorded somewhere (e.g. in the database)?