We’re using Markdown parsers for Reviews, Blog Posts, and Stack Description (the text you’re reading right now). We’re using Bootstrap Markdown for content input (except for reviews) and RedCarpet for rendering in certain places.

Markdown represents a highly portable and lightweight text formatting. I had converted all of my Wordpress posts to Markdown prior to migrating over to Jekyll and eventually to Hugo. The fact that many generators support Markdown means that my content remains portable regardless of the platform/engine I use.

What you see is not what you get, never it is.

Documentation is better in Markdown format. You don’t need anything special to read it.

It is compact, portable, comparable.

Markdown is my text file format of choice.

Because it is almost an effortless markup language without ever having to write an HTML tag. Of course, you'll want to use it in environments that make it look pretty (GitHub, etc.)

Using StackEdit to edit markdown files for blog roll and about sections. MD files are stored in Google Drive and pushed to GH pages through StackEdit.

All of our Javascript code is first written in CoffeeScript for ease of reading / writing. It is compiled to Javascript before being minified and served to the client.

All front-end / back-end is driven by Coffeescript. For the main ReactJS functionality JSX is embedded with coffee in .cjsx files / handled by Browserify.

We like CoffeeScript because it's more readable, we use it because we have a lot of libraries and functions already (plays nicely with Rails, too)

All our code is CoffeeScript, blending seemlessly in our JS stack

Javascript is a hell. We use coffeescript for its readability.