Tips: An Alfred Workflow for Launching .scriv Files in Marked and Scrivener Simultaneously

(UPDATE Jan. 2017: A kind visitor recently let me know that the original workflow I created years ago, had stopped functioning properly. I’ve since fixed it and wrote a follow up post here).

A heads up: As the title implies, this post assumes (or, in a way, suggests) that you have purchased Scrivener, Marked and the Powerpack option in Alfred 2.

One of Scrivener’s shortcomings (yes, they do exist) as far as Markdown support is concerned, is its inability to give an HTML preview of your Markdown syntax while you write in it. There is no workflow for accomplishing this other than exporting your MD or MMD, opening it in another editor that reads MD (or the converted html) and checking it there before cutting and pasting the code into your blog’s editor.

In all fairness, that’s not what Scrivener was created to do and just because I’ve found some slightly unconventional uses for it, I can’t expect the good folks at Literature and Latte to change their software to accommodate lil ole me. We all know Scrivener is much, much bigger than blogging and writing in MD and MMD.

The good news is that even though Scrivener doesn’t have an in-app html preview function for your markdown, there is one program that you can use in tandem with it that can.

That Program is Marked.

You can read about Brett Terpstra’s “Marked” in a slew of different places (including its recommendation in the comments on this site ) so I won’t write a review of it here (maybe another time). In a nutshell though, Marked is a realtime markdown converter that works with any text editor you throw at it. Open a text file in its respective editor, open Marked, then drag the same file into Marked and go back to the text editor to continue writing/editing. As you save your markdown document, you’ll see it update in Marked, displaying the converted HTML instantly.

Cool right? It’s also a game-changer.

Marked and Scrivener

Integrating Marked has made my blogging workflow in Scrivener much more streamlined because of Marked’s handling of MD/MMD as well as its plethora of options and amazing tools for authors. But, that all said, getting a file into each application is clunky at best and almost immediately after doing that a couple of times, I wanted/needed to automate that initial step so that it was smoother.

Enter Alfred

Alfred is another popular tool out there whose sole function is to streamline everyday tasks like launching multiple apps at once, finding files quickly on your computer, searching the web, quitting apps, shutting down or restarting your computer… you get the idea. It does all of this from your keyboard and once you get used to its commands, you’ll get addicted to not touching a mouse or track pad. In truth, it’s one of the first apps I install when I get a new computer.

But aside from these baked-in options that you get for free, you can also pay for the Powerpack option and unlock a slew of very powerful tools that give you immense control over your Mac. One of these tools is the ability to easily create custom workflows. Once I encountered the dilemma above, I dove in and immediately came up with a solution.

Now, one caveat. I am not much of a programmer, so I made my workflow out of the built-in modules that Alfred gives you out of the box. I am sure that with some custom scripting this workflow could be made even nicer (if you have suggestions for improvements leave them in the comments below please). That all said, I was really happy with how this workflow came out. To save you (and I) some time I’ve included a link to the workflow below, so that you can download it and add it to your own personal workflows in Alfred. Just download it, double-click and add it to Alfred. Easy.

The way the workflow works is you bring up your Alfred prompt. Type in the keyword, which in my case is “scrivmarked”, that then allows you to browse your “Documents” directory right in Alfred. Once you find the .scriv file you want to open, arrow down to highlight it and hit the right arrow key where you’ll find a file action to open the file in both Scrivener and Marked, arrow down to that action and hit enter.

AlfredFileAction

Make it Your Own

One of the best things about workflows In Alfred is that you can tweak them to suit your needs relatively easily. Hate my keyword? Choose a different one. Have your Scrivener project files in a different location outside of the Documents directory in OS X? No problem, tweak the search scope. These, and many other aspects of workflows, can be tweaked easily in Alfred without knowing a single line of code.

But, again, if you do know a way to make this better, I’d love it if you posted your modifications in the comments below! I am sure there are many ways to make this workflow even more useful to us all!

Useful links:

Writing: My Writing System Revisited

If you’ve been coming to this site for a while, you may have noticed one of my earlier posts about a writing system I was using at the time. Well, two years have gone by and after years of faithful use, one of the main ingredients of that system, a Dropbox editor by the name of Elements, has finally been sunset.

Change is good.

So with that sad fact come and gone, I’ve been faced with task of finding a new Dropbox editor to fill the iOS void that was wonderfully filled beforehand. If you haven’t read the post that I linked to above in the first paragraph, I invite you to do so. Much of that writing system still exists today and if you write on the go like I do, you may find it useful. Also, I don’t plan on rehashing it here so if you are looking for context, definitely give it a quick spin, it’s not too long.

Back? Excellent!

So after some research I’ve found two beautifully developed and highly capable Dropbox editors that have been out for a good bit, so I guarantee that you’ve heard of them. That old adage “Change is good” definitely has its place in this tale and, truth be told, the ending of Elements might’ve been the best thing that’s happened to my workflow in a good bit.

Bridging the Gap.

The fun thing about workflows is that no matter how much you love a process, it can always be tweaked into something lighter and more efficient. Even though I loved how versatile my last writing workflow was, there were places where it was quite clunky process-wise or hampered by the limitations of iOS at the time. I dealt with it all because those things were mere quibbles and they didn’t slow me down that much. But with Elements out of the picture, it was an invitation to see if I could refine everything a bit, maybe get rid of a few things and, hopefully, add functionality that could make writing anywhere that much more efficient and enjoyable.

So without further ado, here are the editors I settled on.

Writer Pro by the development firm Information Architects Inc and Editorial by the one-man shop OMZ Software headed by Ole Zorn. Both of these text editors fulfilled all of the current needs I had and then some. Without a doubt, the three main stipulations I had were:

  • Markdown support
  • Instant sync across platforms, or robust export options
  • The ability to save my flat text files to Dropbox

Of course there were others on the list, but these were the main ones.

One thing to note, these two apps are still somewhat new and are constantly being developed to accommodate much-requested user features. If you don’t see something in this post that you like, I highly recommend that you go out to their respective sites and have a look a the complete list of features, as well as look at what’s in the pipeline for the future.

None of these editors are perfect, arguably they never will be, but they are a joy to use and are well on the way to being even more feature-rich with the raw talent behind them. I mention this because writers are a finicky bunch. We like our writing experiences to be just so.

So I write this post knowing full well that these editors won’t be for everyone, but maybe for a few. Let’s hit Writer Pro first and then Editorial.

Writer Pro for iPad and iPhone icon

Writer Pro.

Writer Pro was a bit of a tough sell for me. I already owned its older sibling iA Writer (which is still just as awesome now as it was then) and was curious how they were building off of the stark minimalism that they’d strived and gotten so many accolades for in the past. Would it now be cluttered? Not as easy to use? Or worse, would the extra UI/UX come off as unnecessary?

Luckily, the answer to these and all of my concerns were “no”. I can say this, if you are an iA Writer fan and can’t think of a single thing that it could do better, stay put. There is no reason to jump ship to Writer Pro. But, if you’ve loved the experience of writing in iA Writer but wished it had a more robust feature set above Writer’s wonderfully implemented “just open it and write” aesthetic, than Writer Pro is more than likely your answer.

Here’s my short-list of Writer Pro’s strengths and weakness.

Strengths:

  1. Fully supports MD (with inline preview support).
  2. Dropbox sync. I can already hear it now. “Well hold up Tad, I just went to the site and Writer Pro doesn’t sync with Dropbox at all!!” Calm down. You’re right. Writer Pro does not sync with DropBox… yet. But it will. Soon.
  3. A built in workflow that is natural and develops habits conducive to good writing. Admittedly, I didn’t like it at first, but having written a few pieces in it, it is a nice systematic flow that makes sense to me. You can completely ignore it too, but I recommend giving it a spin a few times. You may warm up to it.
  4. Syncs via iCloud to your Mac and your iOS device instantly. Truly. I know there is a lot info out there about how much of a pain in the ass creating adequate sync can be on iCloud, but iA nailed with Writer Pro. There is barely any lag at all. Write on your iPhone, and it immediately shows up on your iPad or Mac.
  5. iA Writer’s spartan layout is here in spades. Not cluttered at all and easily read. Even the sidebar they added on the right is minimalist and can easily be hidden if it bothers you.
    1. Incredible syntax filtering to keep you in check with exactly what you are writing. It’s hard to describe just how useful this is, or how amazing it is to watch it in action. I highly recommend checking it out. It’s truly a game changer for me and the general clean up I do while editing.
  6. Saves as flat .md but exports to pdf, clean html, .docx, or .rtf. More than enough for my mobile writing needs (but some may want more).
  7. Full markdown html preview. Command-R and a pop up comes up instantly, showing you your Markdown, rendered in clean html.
  8. Night mode theme. If you write at night as I often do, this will save your poor eyes from a lot of undue strain. It’s a small thing but I really appreciated it.
  9. Feature parity across platforms. I’m used to losing features when I move to my iPhone or iPad. So it’s an incredible development feat to see a writing experience expressed so completely across my laptop and iOS devices. Nothing (that I can see) has been lost when I move between environments and form factors. Everything you need is there and easy to find.
  10. Has a very talented development house behind it. iA has some big plans ahead for Writer Pro. If there is something missing now, chances are it’ll be added in moving forward. They are meticulous folks, almost to a fault.

Speaking of faults! Here are Writer Pro’s weaknesses:

  1. No Dropbox support currently. Like I said though, it is on the way. iA has already mentioned explicitly that it will be in the next update.
  2. As much as I appreciate the current export options, I wish there were more. I’d love to write a message to someone and export the html straight into an email app for instance. Currently to do that I have to highlight all text, copy, open mail, start a new message, and then paste. It’s clunky and it doesn’t need to be. Adding more options would make Writer Pro a bit more versatile. Though I somehow doubt that’s what they are aiming for.
  3. The structure of the workflow may be a bit rigid for some. Note, Write, Edit, Read is fine for my needs but it may not work at all for others. Want to edit it or add another stage to the process? You’re out of luck.
  4. It’s definitely (and admittedly) a work in progress. The good news is that iA is definitely listening to its user-base. So if you need anything, go on and ask for it. If enough do, they’ll listen.
  5. Not many options to tweak the writing experience. By design, just like iA Writer before it, Writer Pro is a very stark and flat experience. What you see is what you get. Want a different font or just change the font size? Too bad. If this tact isn’t your cup of tea, then chances are you should keep looking elsewhere.
  6. Cost. Getting the iOS and Mac versions will set you back just shy of forty dollars. In a five dollar app world, this may be a tough sell. To me it was worth it though.

mzl.kavtkfpa

Editorial.

Editorial made major waves when it dropped and it’s been years since I saw such a rabid fan-base grow around an iOS text editor. Having used it a good bit now I definitely see what all of the fuss is about. I also see that I have only just barely scratched the surface of what this incredibly powerful editor can do! If you are looking for a humongous deep-dive on everything Editorial click this link right now,  and read Federico Viticci’s review on macstories.net. It’s so long he created a damn e-book out of it. Don’t let that deter you though, it’s brilliant and well worth your time.

If it sounds like Editorial is a sledgehammer to use against a tack nail, well, it can be. In truth, it’s the biggest reason why I didn’t download it initially. I just couldn’t bring myself to use an editor that necessitated another learning curve. Turns out I was absolutely wrong on that count and developer, Ole Zorn, created a text editor that is yours to use however you’d like. Everything you can do (and there’s a lot that you can do) waits patiently, out-of-the-way, allowing you to just get in there and write.

That all said, like Writer Pro it has its strengths and weaknesses too. Here they are.

Strengths:

  1. Super clean layout. The first thing you’ll notice is just how inviting Editorial is when you open it. It’s even more incredible once you start discovering what it’s capable of.
  2. Inline preview support for .md and .mmd. Writer Pro does this as well but I like Editorial’s presentation better. It’s not as stark and it is more readable.
  3. Full markdown HTML preview. A quick swipe left immediately displays how your markdown will render on the web.
  4. Dropbox support front and center. Out of the box, you can assign to a folder in your Dropbox account. I plan to link this to a synced Scrivener project folder at some point, but I haven’t gotten around to it yet.
  5. Utilizes Dropbox versioning. Need something from a previous version? Deleted something you need back? No worries. Editorial has you covered. Super easy to use and some nice piece of mind.
  6. In-app browser for research. This seemed a little kitschy at first until I used it. Now I dearly wish all of my editors had a fully functional browser built-in. Not having to leave my editor in iOS to look up a link or research a topic gets addictive fast.
  7. A huge amount of options to tweak your writing experience. Head on into the settings after you get comfortable. If there is anything you’d like to change about writing in Editorial? Chances are it’s in there. Fonts, sizes, line-height, font-spacing, whew… the list goes on.
  8. Support for text snippets baked in. Got chunks of text or maybe a markdown page layout that you reuse over and over again? Create a text snippet and watch it immediately fill your document with a few taps. Very handy.
  9. Contains a custom workflow framework that allows you to perform a myriad of automated tasks. With these tasks you can do just about anything – like post your text into your blog on WordPress for instance – I’ve only just begun to play with these, but it’s mind-blowing what you can accomplish. Don’t have an interest in creating workflows? No problem. You don’t have to.
  10. Export Options. Because of the workflows above, export options in Editorial are almost limitless.
  11. Has full console-based Python support. Not a Python developer at all but if you are? You’re in for a big treat!
  12. Has a night mode theme. Like Writer Pro, if you write at night, your eyes will thank you.
  13. Custom top keyboard row in iOS. A beautiful custom keyboard row at the top awaits you! Streamlining workflows, snippets, as well as a very novel approach to moving your cursor around your document with swipes – it’s all about one thing, empowering your writing in iOS and saving you time.
  14. Has very talented developer behind it. Like iA, only with one guy behind the curtain. It’s incredible to me what he accomplished in Editorial. The app been called a “game-changer” by many a seasoned iOS veteran and it’s absolutely deserved.
  15. Cost. At $4.99, this app is a steal for all that it does.

That all said, it does have a few weaknesses. Some of them big ones. Here they are.

Weaknesses:

  1. Editorial can do so much that it is truly overwhelming at times. If you are curious like I am, you can easily (and often involuntarily) start geeking out on creating workflows when you originally came there to write. Luckily, as I mentioned above, most of it stays out of the way. But it is there. All those possibilities…
  2. On the flip-side, using it to its fullest potential does necessitate a learning curve. That may turn people off.
  3. iPad only. No Mac or iPhone version. This is a huge point to be aware of. If you don’t write in iOS on an iPad, Editorial is useless to you. On the one hand this is infuriating. On the other, I can’t imagine this app working well on an iPhone. On the Mac though? Definitely. Until then, you’ll have to snag your flat text files from Dropbox and open them in whatever OS X editor you love.

The choice is yours.

So that’s how I filled the recent gap in my workflow. It is not perfect, but I have confidence that it will get close to that quickly. Writer Pro will continue to be my bridge for when I need to sync my words across platforms and Editorial will more than fill my writing needs for when I am just carrying around my iPad. Two apps, loaded with functionality, fully mobile, facilitating my writing from wherever I may be, at any time.

It’s a beautiful thing.

Helpful Links:

Writer Pro: OS X download | iOS (universal) download
Editorial: iOS download (iPad only)

Writing and the Web: The Editorially Review

Editorially.com logo

UPDATE 02/13/14: I am absolutely bummed to hear that these super-talented developers are closing the doors on this exceptional project on May 30th, 2014. Read more about why here.


Here’s my original review:

I spend a good amount of time on this site reviewing native text editor apps and I do so for good reason; generally, they simply work better, are often more stable, and they allow you to save/edit your work in a more convenient fashion via key commands (command S is way quicker than hunting and clicking a save button on a web page’s UI, for instance).

That’s not to say there isn’t a place in my workflow for web apps. I do occasionally use the web-based counterparts to the native apps I have at my disposal, but that usually is only if I am not at my personal computer. In short, if given the choice between Evernote on the web or Evernote on the Mac/PC, or iWork’s Pages on iCloud.com versus Pages locally, I’ll always go the local/native install route.

Don’t get me wrong. I love the idea of web apps becoming the norm in the (probably very near) future, but up until this year, there really hasn’t been anything I’d have taken a chance with writing a post or short story in. I don’t think I’d ever trust long-form writing to a cloud-based service, but short form? Definitely, if something captured my fancy.

And it just so happened that an online editor did.

Enter Editorially.com

PC Layout

Editorially.com accomplishes so many things well that I am starting to wonder if they jacked into my brain specifically.

Editorially is a web-based text editor app for writing on and for the web (or offline too as it turns out, more on that below). Aside from a pleasing and intuitive UI, it’s feature set is what ultimately bowled me over. Here’s the laundry list of things that you get when you sign up for an account:

  • Baked in support for Markdown syntax (it’s supported beautifully and inline). If you’ve visited here before, you’ll know I’ve got a soft spot for MD and MMD and if you do too, you’ll quickly discover just how much Editorially was literally made with it in mind. Be sure to check out their Help page, it’s all kinds of useful.
  • Autosave. It autosaves constantly without lag and pretty much in real-time. I can’t stress how important (and impressive) this actually is. And if you lose your connection during an autosave? It’ll save a copy of your draft in your browser’s cache (modern browsers only). I mean, how cool is that?
  • Collaboration. Got a piece of writing that you want someone to edit or proofread? Editorially has you more than covered with inline comments, track changes with check-in-check-out editing. It’s quite simple for you to invite people to comment, discuss or even take control and edit your files! Give a person a control of your document and they get preoccupied and leave it locked? Not a problem! Ask for control back and if the document has been idle for over 60 seconds, it’s back in your hands.
  • Versioning. You can’t have collaboration without versioning. Editorially knocks this out of the park with a version created with each autosave. You can also diff and compare versions as well as add notes to specific versions to reference in the future. Cool in a browser? Yes. Helpful in making your forget you are writing in a browser? Definitely!
  • Activity Feed. Wondering if your editor/s checked and edited the document you invited them to view? Look no further than the handy built-in Activity Feed. It’ll tell you who edited what and when, as well as provide timestamps for when your document auto-saved.
  • Different Publishing/Export Options. A recent update gave folks the ability to post their markdown to WordPress (.com and self-hosted with Jetpack enabled) or to archive a copy of your work to a folder on Dropbox. I used both for the very post you are reading right now. Both export options worked flawlessly.
  • Other import and export options. But wait! There’s more! Currently you can start a new document by importing a plain text file (.txt, .md, or.markdown) and it’s even more robust in the export category allowing you to export to many file formats including .html, LaTeX (.tex), Rich Text (.rtf), Word (.docx) and even ePub (!?!). I do wish there was a PDF option but, frankly, I’m shocked a web app can do all of this already. That all said, the developers at Editorially are cooking up even more export options in the future and I can always export locally and print to .pdf easily enough.
  • Responsive Design. Somehow the folks at Editorially.com made their site and all of its functionality fully responsive. This means it’s thoroughly usable on a pc, tablet and yes, even a damn smart phone. As web developer and a writer, I seriously can’t believe they pulled it all off. It’s a joy to use and a sight to behold. Even if you don’t end up using their services, you owe it to yourself to check this site out on every screen you can find. If only to see the future of the web/web apps and how high the bar’s been set.

Changing hearts and minds…

As amazing as the above list of functionality is for me to recount, what caused me to pause and smile the most whilst using Editorially was it’s ability to make me pine for the functionality and usability found in a web app, to be in my native apps. If you write in Markdown, Editorially is a no-brainer. Hell, if you simply write for the web (or simply write), there is no reason why this couldn’t (and shouldn’t) be your go-to editor. My wife and colleagues and I use this to collaborate and edit each others work.  Furthermore, I am not ashamed to say that I use it sometimes just because it’s a joy to use. It represents a paradigm shift in my eyes. I really do think it’s the future in many ways.  In fact it wouldn’t surprise me at all if local installs of Office suites are extinct in a couple of years after using Editorially for a few months.

I wouldn’t have thought that a year ago, but I do now.

Obviously I’m a fan…

Clearly I’m smitten with Editorially and all they’ve accomplished. But don’t take my word for it. Go and sign up and give it a spin. At the very least I think it will change your stance on what web apps are capable of today, you sure can’t beat the price (spoiler alert: it’s free) and at best, it’ll give you a very capable alternative to mix things up in your writing workflow. I love it and I am willing to bet that you will too.

Software: My Favorite OS X Text Editors to Date

For years now I’ve been… well… collecting text editors. The reasoning behind this “hobby” can be boiled down to the fact that I am a writer and I like different tools for different tasks. Also, having a web development background, I have a huge appreciation for good UI/UX. I love the idea that something as seemingly mundane as software can make similar tasks (like typing text) a joy or, at the very least, elevate them to something else entirely.

There are a ton of options to choose from out there. It’d be impossible to write about all of them. So in this post I’d like to tackle typically encountered writing tasks and my favorite text editors to date that I use to accomplish them.

Bit of a caveat – All of these will be for Apple’s OS X, though some of them are available for different platforms.

As I’ve mentioned several times on posts here on this site, I am not against the other operating systems out there. They all have their strengths. I just prefer OS X for my computing needs and have been using it for so long now, that I don’t even know much about any other platform anymore. I used to, but there is only so many hours in the day :). I’ll make a deal with you though, I promise to mention other platform versions when it applies.

That said, please know that I have zero experience with that particular version of the software.

Ok, enough jibber jabber, let’s get to it!

Writing Letters

Periodically I drop everything to write a long letter to someone and when I do, I don’t use a Mail app. I’m utterly convinced that the Mail apps around today were built only for quick responses back to people – the distraction of additional emails coming in, the clutter, it’s multi-column UI… it’s pretty much become a long-form chat client.

When I write a letter to someone I want the experience to be spartan, distraction free, with clean easy-to-read fonts, a full screen mode and little-to-no editor tools. Luckily, there are more than enough options out there! What I’ve been using is a combo of iA Writer and Ommwriter. I like to use iA for correspondences that need my attention but not an overly emotionally-infused response. For the latter, I use Ommwriter.

If you’re an Apple device owner, than iA is a dream come true, as there are versions of the app for your Mac, iPhone and iPad. All three sync with each other seamlessly, have a UI that is almost nonexistent, are light weight, support markdown syntax and save to a flat text format that is easy to export into an email (or CMS interface).

Ommwriter is a bit of different animal all together in that it offers its own distinct and custom UI/UX when you fire it up and use it. Undulating backgrounds, full screen mode, individual keystroke sounds, soothing music – it may not be for everyone, but it’s definitely for me. When I write to loved ones I almost always use Ommwriter to complete this task. It does very, very little other than offer a unique writing space. But for letters that deserve your undivided attention? It’s perfect. I am not sure where development is on this one, but it’s currently available on iPad, Mac and Windows PC.

Writing for the Web

While I’ve written a good bit on this site about the virtues of Scrivener as a blogging platform I still am a huge fan of Mou which is a markdown editor I’ve also written about here. I do know there are a lot of excellent options out there for this exact task, but I’ve really grown accustomed to Mou’s aesthetics and it’s lightening quick preview pane that displays your markdown in fully rendered html as you type, with very little lag.

Mou App at mouapp.com (image linked to that very site).

It’s still in beta (and thus, free) but it’s genuinely polished enough so that you don’t ever notice that fact. The developer is really passionate about this editor too, which gives me high hopes for the future. If you write in markdown (and you should if you are writing for the web) and are a Mac user, than you can’t go wrong with Mou. It’s a joy to use and does what it does (process markdown syntax) exceptionally well. Feel free to read my previous review if you are interested and want to learn more about it.

Long-form writing

highres-scrivener-logo

To date, I do all of my long-form writing in Scrivener. It simply handles lots of text in the easiest and best way that caters to how my brain works. Watching all of those small chunks of text pile up into a project that exports beautifully as a whole into any file format you could need, is a beautiful thing to behold. I am unabashedly smitten with it and haven’t witnessed any other editor even come close to what Scrivener does. It’s my one-stop shop for about anything I write.

So if you can only afford one new text editor, Scrivener is what you should get. Not long ago I finished an entire 508 page novel in it, you can read about it here if you want.

Scrivener is available for Mac, Windows and Linux

Note taking

OS X's very own Reminders App

I am never picky when it comes to taking quick notes. That’s why I often use OS X’s Reminders or Notes apps. They are dead simple to use, quick to open and they seamlessly sync with my iOS devices which is key, since 99.9% of the notes I take I will more than likely need as I am walking around during the day.

Mind Mapping

highres-scapple-logo

Here’s another niche that has a lot of options out there (good ones too). I personally love the ease of use that Scapple provides. It super simple and intuitive to ease into and with an export to PDF option it’s easy enough to share with others. Add in its compatibility with Scrivener, and it’s a no-brainer for my workflow.

What’s great too, is that I know for a fact I am not even coming close to using Scapple to its fullest potential. But knowing that it caters to my needs quickly and easily makes it a perfect addition to my writing tool kit.

You can snag Scapple for both Mac and PC and there’s also a free trial for you to try it out if you are on the fence.

Using what works best for you

What I love so much about this golden age of apps is their ease of use, availability in app stores to download and the amazing variety of text editors that are there to choose from.

With so many developers out there clamoring to fulfill our individual needs (and our hard-earned cash), there is bound to be something out there for everyone. When it comes to writing, we are definitely all unique. What I use works for me, but may not work at all for you. I just sometimes find it helpful to read about what others are using and how they are accomplishing the writing goals/tasks in front of them.

If you have some suggestions, list them below in the comments. Let’s a get a complete and quality list here! Marked and Byword come to mind. Are there any others? Let everyone know!

Tips: Setting up Scrivener to Compile MultiMarkdown

Back in August I wrote a post about using Literature and Latte’sScrivener as a complete Blogging System“. What I wasn’t expecting was how that post drummed up a lot conversation about MultiMarkdown and writing in Markdown in general. After going back and forth with you all (a genuine pleasure), I realized that I hadn’t really covered the process of exporting your MMD documents from Scrivener into clean, valid html for whatever web-based platform you were using.

I thought I’d take care of that now and write a companion piece on both setting up Scrivener to use Fletcher Penney’s MultiMarkDown and, once installed, how to easily compile your documents and export them as clean html that you can then copy and paste into the WYSWYG of your preferred blogging platform.

First, let’s get MultiMarkdown installed (if you don’t have it installed already)…

Markdown Export

One thing I failed to mention in that original post was that you actually may not have MultiMarkdown installed on your computer. I say this, because I didn’t. The easiest way to tell (without using the command line)? Open Scrivener, click the Compile button and hit the drop down at the bottom. If you see just “MultiMarkdown” as an option and nothing else, you don’t have everything you need to compile your MMD document into html.

Here’s what you need to do (don’t worry, it’s easy I promise):

  1. Go to Fletcher Penney’s MultiMarkdown downloads page and grab the install that matches the OS you are using on the computer in front of you. I usually download to my desktop to find it easier.
  2. Unzip the file that downloads and double-click the installer within.
  3. Follow the onscreen directions to complete the install.

That’s it! Told you it was easy.

What now?

If you had Scrivener open prior to the download, save your project and quit. Now re-open Scrivener and you should now see a whole new host of MultiMarkdown options under the drop down at the bottom of the “Compile” menu!

mmdoptionsinscrivener

For most of you, the “MultiMarkdown -> Web Page (.html)” option is all you need. Click that and then click the “Compile” button. Again, I like to save the exported .html doc to my desktop to find it easily, but feel free save the document wherever you like and open it in a text editor. To do this, right-click your new .html file and choose an editor like Textmate, Coda or even good old Notepad. Once open, you’ll see that all of your MultiMarkdown has now changed from this:

mmdcode

To this:

ScrivMMDExport

The code you are interested in (unless your working with a static HTML-based site) is within the opening and closing body tags (<body></body>). Copy that code and post it into your site’s editor. When you do this, make sure you are in HTML mode in your site’s editor (in WordPress it’s under the “Text” tab), otherwise you’ll end up with a post contains all of your text as well as all of the html tags. Trust me, it looks funny and broken when you do it.

Hey, this is great! Thanks! But what’s the point to all of this?

Well, put simply, WYSIWYG editors have come a long way over the years, but they are still far from perfect.

If you’ve ever written a post, pasted it into the editor of your site and spent the next hour cleaning up code the editor thought you wanted, you probably wouldn’t want to write on your web site again for a while. On the flip side though, these same web site editors will just about always take clean and valid html code and render it correctly – displaying everything just as you’d expect. Still, trying to write in html (not to mention valid html) is a pain in the butt too – we shouldn’t have to frankly – and, luckily, with Markdown we don’t have to.

That’s why it’s so damn convenient that Scrivener supports it!

What this post didn’t cover. (aka: I smell a series comin’ on!)

I didn’t go over actually writing in Markdown.

I am assuming if you read this far, you already know how to write in Markdown (which lends easily into MultiMarkdown) and that wasn’t really the point of the this post anyways.

If there is interest, I’d be happy to write another post on how I write in, and rely intrinsically on, Markdown for all of my web publishing. If you’d like to hear more, leave any specifics in the comments below (even if it’s just a “Yes please!”) and I will do my best to accommodate them in a future post.

Hope you found this useful! Now get back to blogging in Scrivener!