docs: bike workshop proposal

docs/intro/faq.md

@@ -39,6 +39,25 @@ We think our carefully chosen blend of technologies and our [social approach](/f
 Please read our [initial project announcement post](https://autonomic.zone/blog/co-op-cloud/) for more on this.
 Also see our [strategy page](../strategy/).
 
+## Should I use Co-op Cloud?
+
+We think we can recommend Co-op Cloud in the same way we can recommend a local
+DIY bike repair workshop instead of a professional bike repair shop.
+
+You go to fix your bike, they maybe have the tool you need, it's usually
+chaotically organised, they ask you basically to do the work yourself and
+*maybe* you manage to fix your bike!
+
+Some times you turn up and it's closed because nobody had energy to open up
+that night or they forgot to update their website with the new schedule.
+
+You generally meet really nice people while trying to figure out how the hell
+you get your new brakes fitted. You definitely feel empowered to improve your
+own bike fixing skills in the future and consider helping others with their
+bike.
+
+Co-op Cloud is basically like a digital DIY bike repair workshop 😛
+
 ## How do I make a recipe for (package) an app?
 
 Head on over to **Maintainers** section and see ["Package your first recipe"](/maintainers/tutorial/#package-your-first-recipe) for more.
@@ -183,7 +202,6 @@ It seems like this recommendation changed by the time Co-op Cloud was initiated:
 > Volumes are the preferred way to persist data in Docker containers and services.<br>
 > — [Docker "Storage" docs](https://docs.docker.com/engine/storage/#good-use-cases-for-volumes)
 
-
 > Volumes provide the best and most predictable performance for write-heavy workloads. This is because they bypass the storage driver and don't incur any of the potential overheads introduced by thin provisioning and copy-on-write. Volumes have other benefits, such as allowing you to share data among containers and persisting your data even if no running container is using them.<br>
 >  — [Docker OverlayFS docs](https://docs.docker.com/engine/storage/drivers/overlayfs-driver/#use-volumes-for-write-heavy-workloads)