I too use Mou and it's a great editor. I've contacted the developer a few times (http://chenluois.com/ - bugs and feature requests) and s/he's been very responsive and usually emailed back in a few hours.
Markdown Pro (www.markdownpro.com - 6 dollars) is another great markdown editor for mac that has more features.
In any conversation about Markdown, I think it's appropriate to mention Textile [1] as well. Textile is fairly similar, intended to fulfill the same niche of markup with slightly different syntax. Personally, I prefer textile because I think it's a bit more expressive, though I'd rather be writing LaTeX...
Textile is a different beast. Unprocessed Markdown is meant to be human consumable, not just human readable. Specifically, you should be able to send a raw Markdown file to someone who doesn't know what Markdown is, and it should still be pleasant to read for that person.
Textile uses easy to read syntax, but line prefixes like 'h1.' leak the HTML intentions to the reader. That's not to say textile doesn't have it's uses though. Textile solves problems that Markdown doesn't even address, even in its extended forms. For example, Textile allows you to apply span tags (with class name) using Textile syntax. Markdown requires you to write actual HTML.
Top reason for me: separation of presentation and content
Which, when actually practiced, is the biggest advantage raw HTML offers over anything WYSIWYG. Except with Markdown I don't even have to write out the HTML, and that practice of only caring about content (and addressing presentation later using styling rules) is naturally enforced by the beautifully limited syntax Markdown offers.
True. But just because I am capable of using HTML doesn't preclude me from being a Markdown user too. A different kind of user, but a user nonetheless.
I think markdown could be the lingua franca of publishers. HTML would be the best, but it's a bit to specialized. Where as markdown walks the line of being specialized yet easy enough to learn that it won't scare away brand new users. I mean markdown can interpret plain text into something useful. If enough non-technical sites adopted markdown, front and center, it could spread widely.
Edit your code block over at the left margin as you would normally edit any code. Then do a block insert of 4 spaces down the left side of your code block. That's how I do it.
line of code
line of code
indented line of code
line of code
In vim, after editing your code like you usually would:
Go to the front of the top line,
Ctrl-V to enter visual block mode (Ctrl-Q on windows),
jjj to the bottom line,
I (capital I) to insert at the front,
space space space space,
escape.
I did exactly that to create the above two blocks.
in vim, you can also use ">>" command which indents a line. if you use python, your vim is probably already set up to indent four spaces, so the above can be done with "4>>" (=indent next four lines)
That's GitHub flavor. You can also use back ticks and specify syntax highlighting, e.g:
```python
from functools import partial
def foo(a,b,i):
if i >= a and i <= b:
return i**2
else:
return 0
print reduce(lambda x,y: x+y,map(partial(foo,3,7),xrange(1,10)))
```
I just discovered "Nocs"[1] for the iPad/iPhone, very nice markdown editor with drop box support. It's free and seems to work better than some of the stuff I've paid for.
For the love of {whatever}, please stop using markdown or any other text to html markup. When you use it a lot yourself, you think it's no big deal. And you begin to think your users will understand it easily.
37signals used to do this with Basecamp. I would bet $100 that if they asked their customers, their customers would overwhelmingly say that they prefer the WYSIWYG editor that is now in Basecamp instead of the old way.
I'm going to have to disagree. Markdown is used on StackOverflow, GitHub, Reddit.
While StackOverflow and GitHub users may be tech-savvy, Reddit has a lot of casual users. Markdown is not difficult to pick up, it merely codifies how people type anyway.
Other advantages of using Markdown locally is to separate data from content, legibility, and standard support. Using Pandoc, you can convert Markdown files into HTML, PDF, manpages, etc.
Just because a few tech sites use it doesn't make it user friendly.
This is a tech community so almost everyone here is likely comfortable with learning new things. The rest of the world isn't like that.
Most people don't like learning new things, particularly if it's not going to really make a difference in their lives in a dramatic way. They are familiar with Word or Gmail.
Think of it this way: let's say bought a new car tomorrow. With this new car, instead just sticking in the gas nossel and filling gas, you had to say a few magic words, stick the nossel in, fill gas and then say a few magic words.
The magic words might be simple and even make sense. Like "adding gas" and "done adding gas". But they are just extra steps. Moving parts. Things that could go wrong. Easily.
I'm saying this primarily because I've used markdown in the past and almost always without fail, I get emails and phone calls about how something isn't working the way it should be and invariably it's one character off from what they intended.
In the short term I suppose you might not want to use markdown. But, in the log run markdown would be better then most wyswigs, and if you have a population of users who are sufficiently technical, or need to do something more intricate then a couple paragraphs markdown really is the way to go.
Basecamp uses textile, not markdown. I don't know of an option to switch it. I would be thrilled if it in fact used markdown -- I find it much quicker to write.
For this particular customer, maybe the WYSwhatever is a little easier, but not substantially - I personally prefer the old Basecamp overall.
If you are looking for a Markdown editor for the Mac, check out Mou.
Disclaimer - I am in no way affiliated with the tool or it's developer. Just a happy user :)