New pygments styles.

See #38.

README.md

@@ -1,4 +1,4 @@
-# Flex [![Build Status](https://travis-ci.org/alexandrevicenzi/Flex.svg?branch=master)](https://travis-ci.org/alexandrevicenzi/Flex)
+# Flex [![Build Status](https://travis-ci.org/alexandrevicenzi/Flex.svg?branch=master)](https://travis-ci.org/alexandrevicenzi/Flex) [![Dependency Status](https://david-dm.org/alexandrevicenzi/Flex.svg)](https://david-dm.org/alexandrevicenzi/Flex)
 
 A minimalist [Pelican](http://blog.getpelican.com/) theme.
 
@@ -10,6 +10,7 @@ A minimalist [Pelican](http://blog.getpelican.com/) theme.
 - SEO Best Practices
 - Open Graph
 - Rich Snippets (JSON-LD)
+- [Multiple Code Highlight Styles](https://github.com/alexandrevicenzi/Flex/wiki/Code-Highlight)
 
 ## Integrations
 
@@ -21,10 +22,22 @@ A minimalist [Pelican](http://blog.getpelican.com/) theme.
 - [Piwik](http://piwik.org/)
 - [StatusCake](https://www.statuscake.com/)
 
+## Install
+
+The recommend way to install is over [pelican-themes](https://github.com/getpelican/pelican-themes).
+
+The `master` branch is the development branch. If you're happy with fresh new things and maybe sometimes (~most of time~) broken things you can clone the `master`, but I would recommend to you to clone a tag branch.
+
 ## Docs
 
 [Go to Wiki](https://github.com/alexandrevicenzi/Flex/wiki)
 
+## Contributing
+
+Always open an issue before sending a PR. Talk about the problem/feature that you want to fix. If it's really a good thing you can submit your PR. If you send an PR without talking about before what it is, you may work for nothing.
+
+As always, if you want something that only make sense to you, just fork Flex and start a new theme.
+
 ## Live example
 
 You can see how things looks like [here](https://blog.alexandrevicenzi.com/flex-pelican-theme.html).