That's great news since Markdown will really help those of us who use WordPress get posts formatted that much more quickly. I hate using the formatting buttons that come with WordPress, and Markdown beats hand-coding HTML any day.
(Note: This is an Ode blog, and it uses Markdown.)
Now all we need is Markdown in self-hosted WordPress.org. Then we'll be cooking with gas. The thread that announced Markdown for .com sites says it will be eventually be part of Jetpack for .org installations.
Until then, WordPress people remind that there are many Markdown plugins available.
He acknowledges that most people seem to be moving it the other way (from WordPress to Octopress), but he cites a few things that he couldn't get past in the Ruby-on-one-side, static-HTML-on-the-other world of Octopress:
Acknowledging that something isn't working for you and seeking something that does? Nothing wrong with that. And a whole lot right.
By the way, I love Markdown. And you can get it in WordPress
Click, the blog I write under the auspices of my employer, has moved from Movable Type to WordPress.
The move was prompted by the company's decision to phase out Movable Type, which they've been using since the MT 3 days.
I can't say I'm surprised. While there's a certain flexibility in what you can do in Movable Type (like setting up any number of feeds and kinds of HTML output without regard to themes), the multiblog capability is integrated in a way that WordPress isn't anywhere near, and every damn thing is a static HTML file (if you want it that way), the platform is getting creaky, there's not much of a community, especially compared to WordPress, and the whole WP ecosystem of plugins and themes is pretty much nonexistent.
That said, I got to know Movable Type pretty well, I will miss it, I have to figure out how to build a whole lot of stuff that is easy (and already built in MT).
But there are so many things that WordPress brings to the proverbial table, things I'm learning about as I go, that it's going to be an equally proverbial adventure.
So how do I do this in WordPress? I'm looking into child themes (I confess that I've -- horror of horrors -- modified the main theme in a WordPress blog), but I need EXTRA theming. What I need is the ability to tap the blog database for custom HTML output that includes only the elements I want with accompanying HTML so I can display that output on other sites.
It's so easy to do this in Ode and Movable Type. Why is it so hard (or seemingly so) in WordPress?
The recent BoingBoing post about the busy/huge web site's changes focuses on the move to Disqus comments, but the bigger news is that it's dumping Movable Type for WordPress. Even Matt Mullenweg of Auttomatic fame mentioned it.
A few years ago, BoingBoing, which does something like 1 million views per day, made the move to Movable Type from whatever it is they used until that point. The reason behind the move to MT, as I remember it, anyway, was the high availability of a statically built Movable Type site and its ability to handle the kind of traffic BoingBoing was drawing.
Well fast-forward to now, and BoingBoing's Movable Type days are over. It's still plenty popular but is now running on WordPress. I guess this means that WP is more than able to function in extremely high-traffic environments like that of BoingBoing.