You may wonder why we don’t allow you to really publish from Ulysses, as in “publish a story, not just a draft”. For one, Medium’s API has just been released, and we wanted to stay on the safe side. We don’t want you to accidentially publish something you didn’t intend to, or in a state you didn’t mean to make available to the public. Plus, some of Medium’s advanced options, such as pull quotes and fancy header images, are not available yet, so we figured you might love to tinker around a bit, before you really commit your piece.
Lastly… we all make mistakes, and right now there’s no way for us to allow updating your stories from within Ulysses. So again, we figured it would be best to do drafts, since you can have as many drafts as you like, mistakes and all. Plus, this will only get better in the future, so there’s room for anticipation and excitement at your end, too.
I’ve been keeping an eye on Medium, and though it’s not for me, they’ve managed to reignite interest in the idea of a blogging platform – and any respectable blogging platform needs an API. While I won’t move MacStories away from WordPress, it’s good to know that I have another solid option if I should ever decide to use another platform for another website. To me, Medium looks like a cool company that’s trying something new. And I think that’s more important than ever to empower as many potential writers as possible.
On that note, don’t miss Daniel Jalkut’s first look at the Medium API. Daniel has been developing MarsEdit for several years, and he’s the voice I trust when it comes to blogging APIs and native clients.