Platforms - is it widely available on a broad range of platforms?.
#Simplenote publish with markdown full
In other words, if a product has a feature that is only available when you purchase the software or an account, it will receive full marks for that feature. While these could never be completely unbiased, I hope that the simple trinary scoring alleviates much of this concern.Īdditionally, a product will never be judged for charging its customers. That's a valid choice on the part of the tool. For example, the tool might prefer rich text over markdown and thus receive a -1 on markdown. 1: the feature does not exist, or exists in such a manner that it is unusable.Ġ: the feature exists, but is sub-par, difficult to use, or lacks a critical componentġ: the feature exists and is sufficient for typical use casesĪ -1 on a feature is not necessarily a bad thing - it might simply not fit in the grand scheme of that tool. I'm scoring each entry on the list based on criteria that are important to me, or that I feel would be important to others when deciding between them. So when they look back and question why we, the Franklins of our generation, chose the komputer over the trusty quill and papyrus, they'll catch a glimpse into this milestone of humanity. Thus I am writing this document for the sake of posterity, in an effort to lend an unbiased opinion to future generations. The agony of decision making is nigh on unbearable. We are faced with more choices than ever for our venerable note taking medium, which is both a curse and a blessing. Yet I'm becoming the hipster I swore I would never be and falling for this new medium called a komputor. I have some 30 notebooks in my closet, begging me to fill them up. When Benjamin Franklin sat down to write in his diary what would eventually become the Gettysburg Address, he agonized over his choice of medium - stick with the tried and true stone tablet with hammer and chisel, or lend credence to this new fangled paper and pen? Here I am, 972 years later, faced with a similar decision. The overall journey won’t necessarily end next week but, rather, I’ll let you know how much further I plan to go.A Comparison & Review of Note Taking Applications Next week I’ll wrap up my journey to Markdown by summarizing my results. I can write much more efficiently and effectively with Markdown as part of my routine than I’ve been able to before. I haven’t added any additional steps that cause more lag than save time, and Markdown is a much quicker syntax to work with than HTML. I can say without a doubt that by adding Markdown to my language set that my workflow has sped up considerably.
And with Siri now at my command, I don’t know if I ever will need to. This is especially helpful if I have some ideas for a post and want to keep tabs on those for a later date. If I feel that the post isn’t ready for WordPress yet, I’ll send the post to OmniFocus (which Writing Kit has so kindly added support for) so that I can keep it out of mind but on my radar nonetheless. Now, I write up my posts on the iPad in Markdown using Writing Kit, copy them to the newly-improved WordPress app and either publish or save the draft right from my iPad.
Then Writing Kit came along and made the iPad a viable option for online writing again. So much so that I eventually stopped using my iPad for writing for a spell. But then it started crashing, so I was back to my original workflow – which was very tedious. The WordPress app on the iPad was terrible for a long time, so I never bothered to use it.īlogPress was an improvement for a while, allowing me to actually write entirely for the online audience on my iPad.
#Simplenote publish with markdown mac
With that app, I’d write in plain text and then wouldn’t do much more with it until I got on my Mac at home so I could bring it into WordPress. Only when absolutely necessary do I add images to my posts, and still do it in WordPress once I’ve put the article in there from Byword.įor the longest time I didn’t do any online writing on my iPad. I’ve prtty much incorporated all of the basic Markdown syntax into my articles, and actually avoid embedding images in my posts altogether because of my lack of proficiency (or foresight) in embedding images in Markdown.
Now I am able to write the piece on my Mac in Markdown using Byword, copy the HTML that Byword transcribes from a Markdown export into the WordPress back end and then fine-tune it from there.
What I did before was either write the article in nvALT or in Scrivener in plain text and then send it to my WordPress back end for the “HTMLifying” process. I’m writing this piece in Byword, which has become my application of choice when it comes to writing for the online platform. In this, the penultimate post in my Journey to Markdown series, I’m going to get into how Markdown integrated with my writing workflow, and how I use the apps I’ve mentioned as part of my writing workflow now that Markdown is a part of it.
0 kommentar(er)
