So I mentioned that Byword was not the only app I’m using in my Markdown endeavor. The other one I’m using is Marked by Brett Terpstra.

While I can preview a post right here in Byword (Command+Option+P), Marked does some other things that make it a nice addition to my workflow.

Aside from the built-in features of the app, its a great learning tool. As I’m writing, I’ve been keeping Byword open on one side of the screen, and the same document open in Marked on the other half of the screen. Using this setup, I can instantly see what the final post will look like.

One of my favorite features has been the validate external links feature. By using this tool, Marked verifies links I’ve inserted into the post. This is useful for me as 1) it ensures I’ve got the correct links and 2) ensures I’m using the correct Markdown syntax as I write.

This is just a quick example of how I’m using these two apps to learn and use Markdown. There are many other features of both apps. I’ve found using the two together helps me concentrate on writing, learn Markdown in general, and see what the final product will look like.

In my post about learning Markdown, I mentioned one of the benefits of reading David Sparks’ Field Guide was the app suggestions throughout the book. I found the arguements for using a dedicated app compelling, and after looking through the many options, I decided to give Byword a try.

When reviewing apps, design is often highest on my list of criteria. This isn’t always good, as sometimes apps that look pretty simply don’t work very well. Luckily, Byword isn’t one of these apps. The interface is very simple and clean. The focus of the app is writing, so there aren’t a lot of other features getting in your way. It just works.

Regarding Markdown capabilities, there are two features that I found most beneficial:

*As you’re writing in Markdown, you can quickly preview what it will look like on the web. This is either done through the menu, or through a quick keyboard shortcut. Since I’m new to Markdown, I used this feature often so I could see if I was using the correct syntax as I wrote.

*Another great feature is the ability to export the HTML for your work to your clipboard. After writing, I’d copy the HTML, then paste it to my blog. Because I’d already previewed what it would look like in Byword, pasting the article to my blog’s composition window is the last step.

One other nice touch with Byword, is if you visit the app’s site, you’ll find a Byword guide should you need a Markdown refresher.

Overall, Byword is a beautiful app that works well. But, its not the only one I’m using for learning Markdown. More on that in the next post.

As I continue my usage of Markdown, two things jump out at me

1. It is very easy to use. More specifically, the syntax is easy to remember because there’s not a lot of it. When I do forget what I need to use, I refer to a 1-page cheat sheet I created.
2. I know enough HTML to be dangerous, but wouldn’t consider myself proficient. I’m writing these posts in a third party app, converting the text to HTML, then copying/pasting the HTML to my site. As I do this, I’m learning small amounts of HTML along the way.

So the benefits of learning this seem to be more than just finding a better, more efficient way to post to the web.

In my next post, I hope to talk about the apps I’m using.

In Day 1 of Markdown, I mentioned I’d discuss the resource I used to begin the task of learning Markdown. After reading the initial post, some readers actually guessed what the resource was.

I actually had no intention of learning Markdown, but in a recent Mac Power Users podcast, Lex Friedman and David Sparks initiated a debate about writing in Markdown or HTML.

I knew that David had just released a book about Markdown (Markdown: A MacSparky Field Guide), so I picked up a copy and went for it.

Having no experience using the tool, I can’t comment on whether or not this is the best Markdown book ever. What I can say, however, is that it is working for me, and in the end that’s what’s most important.

The book is not very long, which to me is a major victory. I was able to read most of it inside of a day, and found the topics enjoyable. It includes a history of Markdown, and various use cases for using it.

Where the book shines for a newcomer is in how it teaches you the syntax. There is a chapter devoted specifically to syntax, from formatting, to outlining, to inserting links and pictures in to your text.

The text is great in that it is simple and straightforward, but one additional feature I continually found myself using was the accompanying videos. Created in iBooks Author, paired up with each new topic was a related screencast that presented the lesson in live action. I found this to be a better way to learn.

Another chapter of the book I really liked was around suggested Markdown apps, and why you may or may not want to use them. Being brand new to the topic, I welcome any suggestions that will help me get going that much faster.

So for the second post in a row, I’m using Markdown and plan to continue doing so. In my next post, I hope to comment more on my newfound experience with Markdown.

Today, I took a stab at learning Markdown, the increasingly popular text-to-HTML tool for writing on the web. I’ve heard a lot about Markdown, but never looked beyond some initial discovery in determining what it was.

After reading about it and watching a few short videos, so far, it seems to be pretty straightforward. With its simple structure and ease of use, its easy to see why those who write on the web favor it.

Depending on the app one chooses for writing, it can completely eliminate the need for any HTML knowledge. I’m writing this post in Markdown, and plan to continue to do so going forward barring any unforeseen hurdles.

In my next post, I plan to talk about the resource I used to learn Markdown.

Dan Frakes’ recent Macworld article regarding the iOS app Drafts, sparked enough of my curiosity to give it a shot.

As Dan points out, the options the app provides are seemingly endless. I’m writing this post in the app, and will have emailed it to my blog. Many apps can do this, but not many can do as many other things as Drafts can. I’m happy I made the purchase so far.

App.net is offering a unique trial method for people wishing to try before they buy…

Link

I’ve read a lot about the new iPad mini, and most reviews seem to be positive.  People favor the physical size of the device, and its weight, allowing you to hold it comfortably for long periods of time.  They talk about the vast number of apps available, and how they were were actually optimized for the iPad mini, making it a better experience.  And they debate about whether or not this was the perfect size all along.  

Then the conversation shifts to the screen, and how the mini doesn’t feature a retina display.  Debaters discuss whether or not the non-retina display will cause people to pause before buying.  Then they talk about how much more beautiful the full size iPad’s screen is.  

All of these comments made me curious.  I was interested in the iPad mini when it was just a rumor, and became more so when it became a reality.  I have a first generation iPad, and I was looking to upgrade at some point.  

Then a friend of mine mentioned that his wife had bought him one.  My friend is a user experience designer, and one who’s opinion I value when talking technology.  So, he stopped by and showed me the mini.  Naturally, I focused on two things: the physical size of the device, and its screen.

As far as the size, I agree, I think the physical size of the iPad mini is perfect.  The physical aspects simply make it nice to hold, and for long periods of time.  It makes for a nice experience.

Then there’s the screen.  The non-retina screen.  The horror.

When I first saw the screen, I couldn’t believe how good it was.  The articles I had read had me prepared for blurry text, and an experience that was just un-Apple like.  But then actually seeing it in person, I was blown away by how far off I thought opinions were.

Then it occurred to me.  When review articles are written, it is the job of the author to give an honest opinion about the new device, and how it compares to what is out on the market.  Reviewers have seen or even use the latest and greatest technologies.  So, these devices are what they base their opinions on.  Which is fine.  That’s their job.

But, most of us don’t have the latest and greatest technologies.  Like I said, i was looking to upgrade from a first generation iPad.  So, to me, the iPad mini’s display looked great, possibly because I didn’t even have an iPad 2 for comparison, let alone one featuring a retina display.  

Factor in those people who don’t know, or even care, what a retina display is, and I think most people will find the iPad mini to be a great device.  I liked it so much, that I went out and bought one for myself, and so far, I absolutely love it.  But, that’s my opinion based on how I use the iPad, and the technology I personally have.