add another possible architecture diagram (tpo/web/donate-neo#79) authored by anarcat's avatar anarcat
/cc @stephen
......@@ -505,6 +505,20 @@ sequenceDiagram
donate.tpo->>user: redirects to donation thank you page
```
Another possible implementation was this:
```mermaid
graph TD
A(user visits donate.tpo)
A --> B(django backend serves the donation form, with the all the active perks)
B --> C(user submits form)
C --> D(django frontend creates payment contract with paypal/stripe)
D --> E(django backend validates form)
E --> F(django backend passes donation info to civi)
F --> G(django backend redirects to donation thank you page)
F --> H(civi gets the donation info from the django backend, and adds it to the civi database without trying to validate the donation amount or perks/swag)
```
As of this writing (August 2024), it's unclear whether the actual
design follows this, see [tpo/web/donate-neo#79](https://gitlab.torproject.org/tpo/web/donate-neo/-/issues/79) for the task of
clarifying those docs.
......
......