chore(docs): No motion graphics explainer for now (#462)

electric-sql · Sep 20, 2023 · 58f54d6 · 58f54d6
1 parent 7ff970e
commit 58f54d6
Showing 1 changed file with 0 additions and 2 deletions.
diff --git a/docs/intro/real-world.md b/docs/intro/real-world.md
@@ -14,8 +14,6 @@ Bringing it all together and coming back to a high level, what kind of apps does
 
 ElectricSQL is designed to support relational applications which match a particular pattern. This pattern has a central, Postgres-based, backend application as a control plane or management system. You can then then expose multiple local-first apps and interfaces on top of this, much as you would with traditional API-based architectures.
 
-> XXX todo: motion graphic explainer here.
-
 In this architecture, ElectricSQL replaces traditional APIs and state transfer protocols, like REST and GraphQL. You still define your data model [using your existing web framework](../usage/data-modelling/migrations.md), like Prisma, Phoenix or Rails -- any framework that handles migrations and works with Postgres.
 
 You replace your server-side business logic with a local-first client app and background processing triggered by database events. And you codify your imperative authorization and validation logic into declarative security and sync rules.