So a quick thing which I've started doing recently: "Everything Is Markdown." Have retooled most of writing processes to start there. 1/X
-
-
Replying to @patio11
Previously, I had a confusing mismash of WordPress, various email systems, drafts in various formats, 3 templating systems in repos, etc.
1 reply 1 retweet 0 likes -
Replying to @patio11
Markdown everywhere: I get to use a fairly consistent writing environment (text editor) and separate content and delivery mechanisms.
2 replies 1 retweet 2 likes -
Replying to @patio11
This lets me upgrade delivery mechanisms (and/or change them) without having to crack open previously published content to update it.
1 reply 1 retweet 3 likes -
Replying to @patio11
That wasn't that painful the first time I did e.g. a blog migration, but now that my back catalog is millions of words, yep, not happening.
1 reply 0 retweets 0 likes -
Replying to @patio11
I've also found that I'm basically useless for doing meaningful writing in an IDE or WordPress -- I spend too much time on HTML not writing.
2 replies 0 retweets 0 likes -
Replying to @patio11
Markdown gives me the 95% case virtually for free, and in those rare circumstances where I really, really HTML, it's possible to drop it in.
2 replies 0 retweets 1 like -
Replying to @patio11
I have never really repurposed writing between blog/podcast/etc before. Won't do it often, but optionality is good and process was smooth.
2 replies 0 retweets 3 likes
MDing blog posts, podcast transcripts, emails, and (courtesy of http://remarq.io ) the read-only collateral that businesses throw off.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.