diff --git a/0-Intro.md b/0-Intro.md
new file mode 100644
index 0000000000000000000000000000000000000000..068533052fdb2c8bb06515a66c94f4ec666c9a23
--- /dev/null
+++ b/0-Intro.md
@@ -0,0 +1,38 @@
+# Introduction to git - a powerful version control system
+
+## Why would you want to use a VCS?
+
+### Have you ever:
+
+- Made a change to code, realised it was a mistake and wanted to revert back?
+- Lost code or had a backup that was too old?
+- Had to maintain multiple versions of a product?
+- Wanted to see the difference between two (or more) versions of your code?
+- Wanted to prove that a particular change broke or fixed a piece of code?
+- Wanted to review the history of some code?
+- Wanted to submit a change to someone else's code?
+- Wanted to share your code, or let other people work on your code?
+- Wanted to see how much work is being done, and where, when and by whom?
+- Wanted to experiment with a new feature without interfering with working code?
+
+In these cases, and no doubt others, a version control system should make your life easier.
+
+To misquote a friend: A civilised tool for a civilised age.
+
+by si618 at [https://stackoverflow.com/a/1408464](https://stackoverflow.com/a/1408464)
+
+### Does this look familiar?
+Picture with many draft versions.
+
+Punchline: Not only for code.
+
+### A VCS gives you a history of your project:
+* dcad3f8 add table captions for fwb
+* 92531e7 figure captions for fwb
+* 5129bdd adapted figure to fig for fwb and minor
+* fff1924 minor: fix reference name
+* dda1e33 adapt abstract to numbered fwb summary
+* d2f46d3 compare real TCI and our TCI
+* 35787b1 some mean values we need to report
+* 6af0b79 denser conclusion
+
diff --git a/img/draft_mess.png b/img/draft_mess.png
new file mode 100644
index 0000000000000000000000000000000000000000..3158e2eb6c56a04cf6478963b76a1e60c55d7c86
Binary files /dev/null and b/img/draft_mess.png differ