xamplez-admin · December 19, 2015 17:48 · Jul 21, 2013 · Jul 21, 2013 · Jul 21, 2013 · Jul 21, 2013
diff --git a/CODE b/CODE
@@ -1 +1 @@
-<put your code here>
+<put your code here and change extension to your language>
diff --git a/_README.md b/_README.md
@@ -8,9 +8,9 @@ How to use
 1. Fork this Root Gist to create a new snippet.
 2. Modify your gist according to following rules:
   1. **You MUST put a gist description** which summarizes your snippet as precisely as possible:
-     * Words with a dash `#tag` are indexed as tags.
-     * URL will be highlighted
-     * words beginning with `@john` are highlighted as Twitter links but you can precise also `@twitter:john` and `@github:john`
+     * Words starting with `#` like `#tag` are indexed as hashtags.
+     * Words starting with `@` like `@john` are highlighted as Twitter links (You can also precise `@twitter:john` or `@github:john`
+     * URL will be highlighted in the description
   2. You can add as many files as you want in your gist
   3. File extensions are used to identify the language (e.g. `code.scala` -> scala)
   4. A code snippet shouldn't be too big (a few lines if possible) so don't hesitate to cut in several files

diff --git a/_README.md b/_README.md
@@ -8,9 +8,9 @@ How to use
 1. Fork this Root Gist to create a new snippet.
 2. Modify your gist according to following rules:
   1. **You MUST put a gist description** which summarizes your snippet as precisely as possible:
-    * Words with a dash `#tag` are indexed as tags.
-    * URL will be highlighted
-    * words beginning with `@john` are highlighted as Twitter links but you can precise also `@twitter:john` and `@github:john`
+     * Words with a dash `#tag` are indexed as tags.
+     * URL will be highlighted
+     * words beginning with `@john` are highlighted as Twitter links but you can precise also `@twitter:john` and `@github:john`
   2. You can add as many files as you want in your gist
   3. File extensions are used to identify the language (e.g. `code.scala` -> scala)
   4. A code snippet shouldn't be too big (a few lines if possible) so don't hesitate to cut in several files

diff --git a/_README.md b/_README.md
@@ -7,12 +7,14 @@ How to use
 
 1. Fork this Root Gist to create a new snippet.
 2. Modify your gist according to following rules:
-  1. **You MUST put a gist description** which summarizes your snippet as precisely as possible.
-  2. All words starting in the description with a dash `#tag` are indexed as tags.
-  3. You can add as many files as you want in your gist
-  4. File extensions are used to identify the language (e.g. `code.scala` -> scala)
-  5. A code snippet shouldn't be too big (a few lines if possible) so don't hesitate to cut in several files
-  6. If you want to explain precisely your code or provide usage examples, please use a Markdown file (e.g. `README.md`)
-  7. You can put a License in case your code need to be protected in anyway
+  1. **You MUST put a gist description** which summarizes your snippet as precisely as possible:
+    * Words with a dash `#tag` are indexed as tags.
+    * URL will be highlighted
+    * words beginning with `@john` are highlighted as Twitter links but you can precise also `@twitter:john` and `@github:john`
+  2. You can add as many files as you want in your gist
+  3. File extensions are used to identify the language (e.g. `code.scala` -> scala)
+  4. A code snippet shouldn't be too big (a few lines if possible) so don't hesitate to cut in several files
+  5. If you want to explain precisely your code or provide usage examples, please use a Markdown file (e.g. `README.md`)
+  6. You can put a License in case your code need to be protected in anyway
 3. Save it & wait for [&lt;Put Xamplez Instance URL Here&gt;](http://blablabla.blabla) to index it.
 
diff --git a/README.md → _README.md b/README.md → _README.md
diff --git a/_LICENSE.txt → __LICENSE.txt b/_LICENSE.txt → __LICENSE.txt
diff --git a/README.md b/README.md
@@ -6,16 +6,13 @@ How to use
 ----------
 
 1. Fork this Root Gist to create a new snippet.
-2. Modify your gist according to Rules.
-3. Save it and wait for [&lt;Put Xamplez Instance URL Here&gt;](http://blablabla.blabla) to index it.
+2. Modify your gist according to following rules:
+  1. **You MUST put a gist description** which summarizes your snippet as precisely as possible.
+  2. All words starting in the description with a dash `#tag` are indexed as tags.
+  3. You can add as many files as you want in your gist
+  4. File extensions are used to identify the language (e.g. `code.scala` -> scala)
+  5. A code snippet shouldn't be too big (a few lines if possible) so don't hesitate to cut in several files
+  6. If you want to explain precisely your code or provide usage examples, please use a Markdown file (e.g. `README.md`)
+  7. You can put a License in case your code need to be protected in anyway
+3. Save it & wait for [&lt;Put Xamplez Instance URL Here&gt;](http://blablabla.blabla) to index it.
 
-Rules
------
-
-1. **You MUST put a gist description** which summarizes your snippet as precisely as possible.
-2. All words starting in the description with a dash `#tag` are indexed as tags.
-3. You can add as many files as you want in your gist
-4. File extensions are used to identify the language (e.g. `code.scala` -> scala)
-5. A code snippet shouldn't be too big (a few lines if possible) so don't hesitate to cut in several files
-6. If you want to explain precisely your code or provide usage examples, please use a Markdown file (e.g. `README.md`)
-7. You can put a License in case your code need to be protected in anyway
diff --git a/README.md b/README.md
@@ -7,7 +7,7 @@ How to use
 
 1. Fork this Root Gist to create a new snippet.
 2. Modify your gist according to Rules.
-3. Save it and wait for [<Put Xamplez Instance URL Here>](http://blablabla.blabla) to index it.
+3. Save it and wait for [&lt;Put Xamplez Instance URL Here&gt;](http://blablabla.blabla) to index it.
 
 Rules
 -----

diff --git a/README.md b/README.md
@@ -1,13 +1,13 @@
 # Xamplez's Root Gist
 
-This is the Root Gist for `PUT YOUR TOPIC HERE` Xamplez's instance
+This is the Root Gist for `<PUT YOUR TOPIC HERE>` Xamplez's instance
 
 How to use
 ----------
 
 1. Fork this Root Gist to create a new snippet.
 2. Modify your gist according to Rules.
-3. Save it and wait for [Put Xamplez Instance URL Here>](http://blablabla.blabla) to index it.
+3. Save it and wait for [<Put Xamplez Instance URL Here>](http://blablabla.blabla) to index it.
 
 Rules
 -----

diff --git a/README.md b/README.md
@@ -1,13 +1,13 @@
 # Xamplez's Root Gist
 
-This is the Root Gist for <PUT YOUR TOPIC HERE> Xamplez's instance
+This is the Root Gist for `PUT YOUR TOPIC HERE` Xamplez's instance
 
 How to use
 ----------
 
 1. Fork this Root Gist to create a new snippet.
 2. Modify your gist according to Rules.
-3. Save it and wait for [<Put Xamplez Instance URL Here>]() to index it.
+3. Save it and wait for [Put Xamplez Instance URL Here>](http://blablabla.blabla) to index it.
 
 Rules
 -----

diff --git a/README.md b/README.md
@@ -1,17 +1,11 @@
-# Xamplez's Root Gist of the Root Gists
+# Xamplez's Root Gist
 
-## Instructions for Xamplez administrators
-When you create a new instance of Xamplez, you must first fork your configuration from the [Lord of the Gists]().
-Then, you create your Root Gist(s) by forking this Root Gist of the Root Gists.
-It just gives a default template that you can modify. 
-Finally, make the configuration gist point to this/these Root Gist.
-
-## Instructions for Xamplez code snippet creators
+This is the Root Gist for <PUT YOUR TOPIC HERE> Xamplez's instance
 
 How to use
 ----------
 
-1. Fork the Root Gist to create a new snippet.
+1. Fork this Root Gist to create a new snippet.
 2. Modify your gist according to Rules.
 3. Save it and wait for [<Put Xamplez Instance URL Here>]() to index it.
 

diff --git a/CODE b/CODE
@@ -0,0 +1 @@
+<put your code here>
diff --git a/README.md b/README.md
@@ -0,0 +1,27 @@
+# Xamplez's Root Gist of the Root Gists
+
+## Instructions for Xamplez administrators
+When you create a new instance of Xamplez, you must first fork your configuration from the [Lord of the Gists]().
+Then, you create your Root Gist(s) by forking this Root Gist of the Root Gists.
+It just gives a default template that you can modify. 
+Finally, make the configuration gist point to this/these Root Gist.
+
+## Instructions for Xamplez code snippet creators
+
+How to use
+----------
+
+1. Fork the Root Gist to create a new snippet.
+2. Modify your gist according to Rules.
+3. Save it and wait for [<Put Xamplez Instance URL Here>]() to index it.
+
+Rules
+-----
+
+1. **You MUST put a gist description** which summarizes your snippet as precisely as possible.
+2. All words starting in the description with a dash `#tag` are indexed as tags.
+3. You can add as many files as you want in your gist
+4. File extensions are used to identify the language (e.g. `code.scala` -> scala)
+5. A code snippet shouldn't be too big (a few lines if possible) so don't hesitate to cut in several files
+6. If you want to explain precisely your code or provide usage examples, please use a Markdown file (e.g. `README.md`)
+7. You can put a License in case your code need to be protected in anyway
diff --git a/_LICENSE.txt b/_LICENSE.txt
@@ -0,0 +1,13 @@
+            DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
+                    Version 2, December 2004
+
+ Copyright (C) 2013 YOUR_NAME_HERE <YOUR_URL_HERE>
+
+ Everyone is permitted to copy and distribute verbatim or modified
+ copies of this license document, and changing it is allowed as long
+ as the name is changed.
+
+            DO WHAT THE FUCK YOU WANT TO PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. You just DO WHAT THE FUCK YOU WANT TO.
Original file line number	Diff line number	Diff line change
		@@ -1 +1 @@
		<put your code here>
		<put your code here and change extension to your language>