Markdown vs. CoffeeScript vs. Hack

All documentation and blog posts are written in Markdown

We use Markdown primarily for documentation and other forms of writing.

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.

Users can format their contributions with Markdown. Great way to post tutorials with code.

Authoring of content

News articles consumed in markdown and injected into React components using Showdown with an XSS filter.

Define the project pages.

By now, almost all my text content is created in (some dialect of) markdown. It's easy to process and extend in javascript.

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.

For when you need to write.

Project documentation.

Documentation and tutorials about the app

Markdown is how I format all my posts. Uses the "smart" and "footnotes" options.

Update with Parsedown

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.

We use this internally, but there is also Markdown CMS plugn-in for Agile Toolkit.

We use NimbusKit/markdown as a convenience wrapper around NSAttributedString

저는 markdown 덕후입니다

Almost everywhere except Python documentation.

wiki notes, internal how-to guides, technical docs, change-logs, release notes

All specifications

Writing README.md's is very important to us. Also a lot of our content is maintained in Markdown (using contentful.com). We are also cool with org-mode.

We use Markdown to write posts for our blog, and also document our processes.

Huge fan of markdown

Mainly for github Readme files, and occasionally for other documentation as desired.

간략한 문법을 통해 깔끔한 문서가 나오는것에 매료되어있습니다.

Write Blog Post @ Github Pages, Documentation like API Blueprint

Use it on a daily basis to create beautifully formatted documents / pdfs.

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.)

Code documentation.

Markdown is awesome and becoming more well-known. It is also easier than using some proprietary markup language.

Yes, we have a README

Standard for editing readme markdown files.

For notes and documentation

For READMEs in code respository

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

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.

I use a lot to coding JS.

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

This is my language-of-choice for coding.

All frontend code written in coffeescript

See NodeJS once again.

CoffeeScript is good to write some utilities at front-end.

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.

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)