TODO Update this, @BP!

Architecture¶

The tate-wagtail project is a monolithic application, combining code that used to be managed and hosted in separate projects.

Add more details here, and diagrams.

Site codebases¶

One of the Key Performance Indicators for the project is the number of separate site codebases that need to be maintained. With the change in architecture to a monolithic Wagtail site, we expect this number to decrease greatly.

Legacy (7)¶

The code needed for the website lives across 7 repositories, 3 of which needing updates as part of regular product development tasks (CMS, frontend, UI).

* https://github.com/tatemedia/ui
* https://github.com/TateMedia/frontend
* https://github.com/TateIS/Tate-Base-Files
* https://github.com/TateMedia/api-client
* https://github.com/TateMedia/api
* https://github.com/TateMedia/cis2json
* https://github.com/TateIS/Ansible

Code freeze (4)¶

As of the code freeze, developers should only need to work in a single repository, with the API repository still in active use by the new monolithic application.

-* https://github.com/tatemedia/ui
-* https://github.com/TateMedia/frontend
-* https://github.com/TateIS/Tate-Base-Files
-* https://github.com/TateMedia/api-client
+* https://github.com/TateMedia/tate-wagtail
* https://github.com/TateMedia/api
* https://github.com/TateMedia/cis2json
* https://github.com/TateIS/Ansible

MVP launch (3)¶

Due to the early code freeze, the number of application codebases relevant at launch will remain largely unchanged.

* https://github.com/TateMedia/tate-wagtail
-* https://github.com/TateMedia/api
* https://github.com/TateMedia/cis2json
* https://github.com/TateIS/Ansible

Visee site launch (2)¶

With the Visee site launch, all code and infrastructure needed for the IaaS site with Drupal is no longer relevant (and could be fully removed). This includes previously-deprecated repositories that had been merged into tate-wagtail, and Ansible configuration for IaaS deployments.

* https://github.com/TateMedia/tate-wagtail
* https://github.com/TateMedia/cis2json
-* https://github.com/TateIS/Ansible

Future state: direct background sync Wagtail <-> CIS (1)¶

Once the CIS data integration can be driven entirely by Django, there will be no need to maintain the separate Java cis2json scripts.

* https://github.com/TateMedia/tate-wagtail
-* https://github.com/TateMedia/cis2json