Decide the tech stack and design ideas
pbiology opened this issue · comments
Description
The tool needs to have an established and agreed upon tech stack and design ideas so we all can think about how to implement functionality.
Suggested solution
Have lead developers suggest and decide upon a tech stack
This can be closed when
- A tech stack and design ideas exist for this project
- Documented somewhere in this repo
Blocked by
We have decided to go with a split frontend/backend and to use a mongoDB solution for keeping data in the backend.
Endpoints needed will be built using FastAPI or equivalent.
As for frontend this is yet to be fully decided due to not having any frontend resources at the moment.
At some point it would be nice to have the design/architecture documented, but this will be created at a later stage