This app was initially split into a front end Vue app and back end Firebase app, then Django app.
Also this was originally built with a different organisation in mind with slighty different goals.
As such, we have a number of models and libraries in weird places - if you started this project tomorrow you wouldn't lay them the way they they are laid out now.
This issue is for a refactor, so that if possible, we'd have a core that can be used across future installations and then separate from that, stuff that's really specific to CAT. For example, the CAT specific importers would ideally live in their own django app or module, whereas the 'cl8' module would have the core functionality (i.e. search, listing, integrating with slack, or other services, viewing and editing profiles, etc ).
In the long run, you'd ideally have these separately usable, so future installations are essentially the 'cl8' module, plus some configuration at well defined points, and the CAT code as an extension.
This app was initially split into a front end Vue app and back end Firebase app, then Django app.
Also this was originally built with a different organisation in mind with slighty different goals.
As such, we have a number of models and libraries in weird places - if you started this project tomorrow you wouldn't lay them the way they they are laid out now.
This issue is for a refactor, so that if possible, we'd have a core that can be used across future installations and then separate from that, stuff that's really specific to CAT. For example, the CAT specific importers would ideally live in their own django app or module, whereas the 'cl8' module would have the core functionality (i.e. search, listing, integrating with slack, or other services, viewing and editing profiles, etc ).
In the long run, you'd ideally have these separately usable, so future installations are essentially the 'cl8' module, plus some configuration at well defined points, and the CAT code as an extension.