@@ -186,9 +186,31 @@ The CRM service is built with two distinct servers:
*`test-api.donate.torproject.org`: test site to rename the API
middleware (see [issue 40123](https://gitlab.torproject.org/tpo/tpa/team/-/issues/40123))
There is also <https://donate.torproject.org> which is a static
website built with Lektor. That site talks with the donation API
middleware through Javascript.
#### Access
The CRM doesn't talk to the outside internet and can be accessed only via http authentication.
Users that need to access the CRM need both to be added on Civi and on the apache on `crm-ext-01.tpo`.
#### Components
The Civi CRM instance is used for:
- Mass emailing via the Newsletter
- Donation campaigns
The monthly newsletter is configured on Civi and an archive is created on <https://newsletter.torproject.org>.
Donation campaigns are setup both on Civi and the donate website ([donate.torproject.org](https://donate.torproject.org)).
<https://donate.torproject.org> is a static website built with Lektor like all the other tpo [websites](https://gitlab.torproject.org/tpo/web/).
<https://donate.torproject.org> doesn't talk to Civi. The `donate-api` php app is the component that allows communications via the `donate.torproject.org` site and Civi.
The donate.tpo site talks with the donation API middleware through Javascript - a react component was written for this and is part of the [donate-static repository](https://gitlab.torproject.org/tpo/web/donate-static).
Civi, the php application and the JS component on donate-static are all maintained by the Civi CRM contractors.
The donate.tpo website are maintained by TPO (communication and donations teams), except for the JS component and any major modification that involves also some Civi development, which is done by the Civi contractors.
