Merge pull request #28 from citricsquid/metalsmith

Version 2

.gitignore

@@ -0,0 +1,4 @@
+.vagrant
+node_modules
+bower_components
+build

LICENSE

@@ -1,18 +1,21 @@
-Copyright (C) 2012 - 2013 Samuel Ryan (citricsquid)
+The MIT License (MIT)
 
-Permission is hereby granted, free of charge, to any person obtaining a copy of 
-this software and associated documentation files (the "Software"), to deal in 
-the Software without restriction, including without limitation the rights to use, 
-copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the 
-Software, and to permit persons to whom the Software is furnished to do so, 
-subject to the following conditions:
+Copyright (c) 2015 Samuel Ryan <sam@samryan.co.uk>
 
-The above copyright notice and this permission notice shall be included in all 
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
 copies or substantial portions of the Software.
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR 
-IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, 
-FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE 
-AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, 
-WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN 
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

README.md

@@ -0,0 +1,32 @@
+# [httpstatus.es](http://httpstatus.es)
+
+[httpstatus.es](http://httpstatus.es) is an easy to reference database of HTTP Status Codes
+with their definitions and helpful code references.
+
+## Contributing
+
+All contributions are welcome! If you have an idea to improve the website please
+submit a pull request or [create an issue][1], or provide your thoughts on any
+[open issues][1].
+
+Each status code lives in a Markdown file at [contents/codes](contents/codes),
+the easiest way to submit changes is via the GitHub editor. When contributing
+changes to the status codes please be mindful of the following:
+
+* Soft line length of 80 for Markdown
+* Markdown links should be used as [references instead of inline][2]
+* If an RFC or external document is referenced, make the reference a link
+* Source information on a status code from the most recent standards available
+    (Status Code standards directory is available on [iana.org][3])
+* The opening paragraph of a status code should describe the meaning, following
+    paragraphs can describe implementation
+* Don't edit the meaning of descriptions, but formatting and structural
+    changes are a-okay
+* [Don't double-space after a period][4], and remove any examples of it
+* If the description references a section in the current RFC, always add the RFC
+    identifier. For example "Section 6.6" should become "RFC1234 Section 6.6"
+
+[1]: <https://github.com/citricsquid/httpstatus.es/issues>
+[2]: <https://daringfireball.net/projects/markdown/syntax#link>
+[3]: <http://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml>
+[4]: <http://www.slate.com/articles/technology/technology/2011/01/space_invaders.html>