Architecture: Cross-cutting Concepts

[lwjohnst86]

Section Cross-cutting Concepts (design/cross-cutting-concepts.qmd). We've already done a few of these, and many would be basically a paragraph max. We can split the sections up.

@rqding Maybe you could do the security and dissemination (how will people install Seedcase) subsections? And @K-Beicher you could do the Privacy/legal subsection?

• [x] Subsection: Security (backend authentication)
• [x] Subsection: Privacy, legal
• [x] Subsection: Logging, monitoring
• [x] Subsection: Storage, analysis locations
• [x] Subsection: Multiple domain-specific standards (? Like data variable naming)
• [ ] Subsection: Multi-language support
• [ ] Subsection: UX, UI
• [x] Subsection: Dissemination (Where to install from, ?)
• [ ] Subsection: Guiding principles (expand from intro, or move from intro?)
• [x] Subsection: Permission levels (#91)

[lwjohnst86]

@K-Beicher if you are looking for stuff to do, you could do the Logging and monitoring section

[lwjohnst86]

@rqding could you write about the installation/dissemination? How will we get the users to install the software? I know we'll start with Docker, but it would be good to eventually make it more formal (e.g. .exe, .deb, and .dmg/.pkg), to reduce the number of steps users take to install Seedcase.

[lwjohnst86]

Not necessary to use this issue anymore