Update docs so that docs reflect the intentions of how the system is designed in v2.
Remove use case docs, which mostly focused on push/pull. Not applicable now that NetworkDeployment is used.
Do you have any concerns with this PR?
I couldn't be 100% certain of the UI docs. These will evolve along with v2 issues in the web-client repo. Most error reporting will now be through fetching and displaying NetworkDeployment records, instead of as alerts on the top of the screen, but the UI isn't implemented yet so I couldn't give specific instructions.
How can the reviewer verify this PR?
View
Any background context you want to provide?
The use case docs were mostly an exercise that I did for better understanding the system. They don't provide much value, and had become out-dated, so I just removed them.
Screenshots or logs (if appropriate)
Questions:
Have you connected this PR to the issue it resolves? #365
Does the documentation need an update? Included
Does this add new dependencies? No
Have you added unit or functional tests for this PR? No
What does this PR do?
Do you have any concerns with this PR?
I couldn't be 100% certain of the UI docs. These will evolve along with v2 issues in the web-client repo. Most error reporting will now be through fetching and displaying NetworkDeployment records, instead of as alerts on the top of the screen, but the UI isn't implemented yet so I couldn't give specific instructions.
How can the reviewer verify this PR?
View
Any background context you want to provide?
The use case docs were mostly an exercise that I did for better understanding the system. They don't provide much value, and had become out-dated, so I just removed them.
Screenshots or logs (if appropriate)
Questions: