Page History

...

There is also universal storage, part of angular universal that has some overlap
Not enough people have experience with redux, js data or universal storage.
We will research this by the next meeting, in order to come to an informed decision.

UI Style Guide

Should we create a document that describes how the UI should work, what it's components are, how they should be designed, what is customizable in the theme, etc.
Do we create one single theme, or a version that is a blank slate, and an opinionated version that showcases what can be achieved
Do we make (part of) this before development can start?

In order to achieve a cohesive design it's important to start formalizing these things early on
We need a first draft during the initial stages of development, and adjust it later on if necessary
We should focus on a "blank slate" theme first, as it will be easier to create an opinionated version started from that as the other way around
Afterwards create the opinionated theme

Are we going to require that code be documented using TypeDoc as in the prototype?
Will we use a code style guide?
How do we decide and communicate about the use of a new 3d party library or component?
Do we put resources on the Duraspace or github wiki?
We could remove the concept of communities from the UI, and use the term collection for everything, even if nothing changes to the backend. Is dat something we want to do?
- it would bring DSpace in line with PCDM

We'll ask everybody to use TypeDoc
We'll use the standard angular code style guide as a starting point, deviations from it can be added later on.
If you want to introduce a new 3d party dependency you should bring it up in these meetings
We'll put everything on the Duraspace wiki, but will add a summary to the README.md file on github
We'll remove the concept of communities from the UI. However we should take care not to introduce too many changes in DSpace 7 to keep the workload under control.