vercel · mattpocock · Sep 20, 2022 · Sep 20, 2022 · Sep 20, 2022
@@ -2,10 +2,14 @@
 
 ## The problem
 
+![](../../../public/images/docs/why-turborepo-problem.png)
+
 Monorepos have many advantages - but **they struggle to scale**. Each workspace has its own test suite, its own linting and its own build process. A single monorepo might have **hundreds of tasks to execute**.
 
 ## The solution
 
+![](../../../public/images/docs/why-turborepo-solution.png)
+
 **Turborepo solves your monorepo's scaling problem**. Our remote cache stores the result of all your tasks, meaning that **your CI never needs to do the same work twice**.
 
 Task scheduling can be difficult in a monorepo. Imagine `yarn build` needs to run before `yarn test`, across all your workspaces. Turborepo **can schedule your tasks for maximum speed**, across all available cores.