Using Markdown

(This is a post to help me remember common Markdown syntax.)

To be sure, if I really wanted to preserve my content indefinitely, Markdown in a text file is better than Markdown in a database field.

Markdown Makes Sense, Even in an Email

I dislike Rich-text or HTML email. If it’s done right, it’s not bad. It’s usually not done right.

Markdown is Easier to Fix

Code like <span style="font-weight: bold; font-family: Georgia; color: red;"> litter old pages, and I always feel compelled to take a minute (more like 15) to strip them all out. To be sure, Markdown doesn’t stop you from using the above.

Writing Code

<head<?php print $rdf->profile; ?>>
  <?php print $head; ?>
  <title><?php print $head_title; ?></title>
  <!--googleoff: all-->
  <?php print $styles; ?>
  <?php print $web_area_feed; ?>
  <?php print $shiv; ?>
  <?php print $scripts; ?>
</head>
  1. Markdown can be transported more easily
  2. Markdown encourages structured data, something that I’ve been pushing for a long time at work
    • Need a hero image? Use a field
    • New an ad inserted? Use a field
    • Need a slideshow? Use a field
    • None of the above should be part of the main body content
  3. Fewer inline styles that required fixing before you can update the look and feel

This post inspired by Chris Coyier.