From bb2c44639c63d93bd8f4cb3cc2b37c756c52747f Mon Sep 17 00:00:00 2001
From: Romain Asnar <romain.asnar@gmail.com>
Date: Fri, 18 May 2018 03:22:34 +0800
Subject: [PATCH 1/3] Add table of contents and titles in README file.

---
 README.md | 50 ++++++++++++++++++++++++++++++++++++++++++++++++--
 1 file changed, 48 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index a5d925c..2859ae6 100644
--- a/README.md
+++ b/README.md
@@ -1,2 +1,48 @@
-# medium-guidelines
-Guidelines and good practices for Medium publications
+# Medium Guidelines
+
+This guidelines are made for people who love writing amazing stories on Medium. As developers, we often miss the opportunity to get benefits from sharing our experiences, knowledge and thinking. 
+
+This document intend to be clear, consistent and brief.
+
+## Table Of Contents
+
+* [Content](#content)
+  * [Headlines](#headlines)
+  * [Images](#images)
+  * [Call to action](#call-to-action)
+  * [What I learned](#what-i-learned)
+* [Cooperation](#cooperation)
+* [Duration](#duration)
+* [Frequency](#frequency)
+* [Schedules](#schedules)
+* [Social Media](#social-media)
+* [Tags](#tags)
+* [References](#references)
+
+## Content
+
+### Headlines
+
+### Images
+
+### Call to action
+
+### What I Learned
+
+## Cooperation
+
+## Duration
+
+## Assets
+
+## Frequency
+
+## Schedules
+
+## Social Media
+
+## Tags
+
+## References
+
+- [How to write Medium stories people will actually read - by Quincy Larson](https://medium.freecodecamp.org/how-to-write-medium-stories-people-will-actually-read-92e58a27c8d8)

From 6750cd0a7f4a7ae1273c7c51c152dca6818fa7ff Mon Sep 17 00:00:00 2001
From: Romain Asnar <romain.asnar@gmail.com>
Date: Fri, 18 May 2018 15:24:44 +0800
Subject: [PATCH 2/3] Fix typos.

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 2859ae6..0adaa60 100644
--- a/README.md
+++ b/README.md
@@ -1,8 +1,8 @@
 # Medium Guidelines
 
-This guidelines are made for people who love writing amazing stories on Medium. As developers, we often miss the opportunity to get benefits from sharing our experiences, knowledge and thinking. 
+These guidelines are made for people who love writing amazing stories on Medium. As developers, we often miss the opportunity to get benefits from sharing our experiences, knowledge and thinking. 
 
-This document intend to be clear, consistent and brief.
+This document intends to be clear, consistent and brief.
 
 ## Table Of Contents
 

From 06c568a6e0102c878a1a12c23075fe4108667326 Mon Sep 17 00:00:00 2001
From: Damien Fraud <damien.fraud@gmail.com>
Date: Fri, 18 May 2018 17:23:46 +0200
Subject: [PATCH 3/3] Update introduction for more context about the WHY

---
 README.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 0adaa60..3a9d09e 100644
--- a/README.md
+++ b/README.md
@@ -1,8 +1,10 @@
 # Medium Guidelines
 
-These guidelines are made for people who love writing amazing stories on Medium. As developers, we often miss the opportunity to get benefits from sharing our experiences, knowledge and thinking. 
+These guidelines are made for people who love writing amazing stories on Medium. As developers, we often miss the opportunity to get benefits from sharing our experiences, knowledge and thinking. We created this space to share best practices based on our own experiences to help everyone to be able to get the most out of Medium.
 
-This document intends to be clear, consistent and brief.
+We value experience over information.
+
+This document intends to be clear, consistent and brief. Consider it as our own cheatsheet of Medium.
 
 ## Table Of Contents