So it has been almost two months since I last wrote about my adventures in Markdown, and even that article was brief as I discovered that I wasn’t a fan of using my iPhone for writing – Markdown or otherwise. The journey contiues today with how I’ve integrated the use of Markdown into my online writing. And not just here…but everywhere.
Now I’m still a rookie in that I haven’t tried to use Markdown for images yet – or anything beyond the basics, for that matter. Still, I’m pretty happy with how I’ve managed to shift gears from HTML to Markdown so quickly.
Then again, Brett Kelly said I would do just that.
Basic Integration
First off, it’s official: I’m a Markdown guy now.
In fact, I can’t remember the last time I wrote a draft for something going online that wasn’t written in Markdown. Sure, I tweak my posts once they’re in WordPress using HTML (since that’s the only way I can tweak them based on my limited Markdown knowledge), but the nuts and bolts of my online writing is done using Markdown.
And I couldn’t be happier about that.
In terms of overall integration, I’ve found that I’ve been able to keep it up no matter what device I’m using, be it the iPad or my MacBook Air. I’ve got the tools in place to make it work easier for me on both fronts, but now that my mindset is Markdown-centric, I know I’d be able to use applications that don’t have as much of the Markdown syntax “baked in” as I do with my current ones of choice, Byword and Writing Kit.
Further Integration
Where I’m having issues is pushing forward with my Markdown prowess. I seem to be content – or perhaps stuck is a more appropriate word – with knowing what I know and leaving it at that. I’m able to pump out articles faster now, that’s for sure. But now I’m contemplating these questions at this stage of my Markdown experiment:
- Can I go faster with more Markdown syntax in my arsenal? Probably.
- Do I feel the need to add more Markdown syntax to my arsenal? Maybe.
- Should I pursue diving deeper into Markdown right now to acquire said arsenal? Again…maybe.
Honestly, I’m feeling pretty content with where I’m at with my Markdown integration. Considering I’m also spending a lot more time writing for offline purposes, muddying up the waters even more at this stage of the game doesn’t seem to make a whole lot of sense to me. This all leads to another question:
- Am I making too much of this? Once again – well…you get the picture.
Resistance is Futile
All this aside, I’m fully vested in Markdown now. When I sit down to write for the online platform or am curious about the latest writing app, Markdown is one of the first things that comes to mind.
On that note, a word to developers: If your writing app doesn’t support Markdown, then it’s highly unlikely I’ll be buying/using your app.1
That’s how far I’ve come on the journey. How I get what I’ve written in Markdown to my online portals (my workflow) is what I’ll be writing about new in the series. And it’ll be in less than six weeks’ time, folks.
1 I’m just sayin’.
