A case for Markdown and the WP 5.0 Editing Experience

I love markdown written as I

(Note to my loyal readers, yes this is not my normal format, but I wanted a platform to say this out loud, so here it is.)

I am pretty darn excited about the possibilities of the WordPress 5.0 editing experience. You might still be calling it Gutenberg and that is OK, but when WP 5.0 drops it will just be ‘the editor’. The idea of manipulating my content with drag and drop and no more messy handwritten shortcodes is broadly appealing. I have a few awesome personal anecdotes about why this is so awesome but the more I talk to agencies the more I see that one of the serious concerns is giving the content editor too much control. If you can insert columns or other strange blocks ‘where they don’t belong’ on a landing page, all hell is going to break loose with brand standards.

Enter the Markdown…

What if instead of freaking out about how to retrain our clients, we seize the opportunity to help them embrace a much cleaner path that would require almost no change in their tool chain and less than 30 minutes to master (with a cheat sheet handy of course).
Markdown was specifically created as “an easy-to-read, easy-to-write plain text format, and optionally convert it to structurally valid XHTML (or HTML)”
Do you want to something in italics? word
Do you want to bold something? word
The notation is very stable and can be written in Word, Google Docs, notepad or (insert your favorite text editor here). Hundreds of resources are available online to help you learn it and there are so many reference materials, that might be the most overwhelming part.

And what does this have to do with the WordPress 5.0 editing experience?

You can cut and paste or WP-CLI post create from a text file into Gutenberg and it will correctly transform it into beautiful HTML. Once there, you hit one (1) button from a dropdown called ‘Convert to blocks’ and then you have every line break as it’s own block. And the kicker here, is if you just paste in a URL to some media asset it can recognize, like a tweet or a youtube video, it will just auto form a proper block around it.

This is literally random, from wikipedia

Once the ‘base content’ is there in blocks, well, the art of setting this image here and that image there and such is actually quite fun. In fact this post was made exactly this way and yes, there are random pictures from wikipedia throughout it to prove a point. I did not type those on my original post with you can see over on my Github, here: https://github.com/mcdwayne/PublicDocs/blob/master/A-Case-For-Markdown.txt

Why not just use the 5.0 editor to write your content?

For me personally, this comes down to workflow and tool choice. I have burned myself way too many times asking my browser not to crash, refresh or otherwise forget what I am currently doing in that window while typing. Auto save points like Google Docs can make that better, but you know what never forgets? Sublime text. You know what works on airplanes? Sublime text. I do however accept that I am in, what was once descried to me as, the 0.2% of content creators who think this way currently.

But what if, instead of giving your content creators a new window and a lot of shiny new toys that you might be able to lock down but would raise so many more questions than answers, what if instead you showed them a way to be consistent with their brand content and made formatting and publishing this content a very simple, well understood process that would let you then better explain the entire editor slowly to their trusted team members. Let every intern and new person write all the Google Docs in the world, but only the trusted get to use the WP Editor.

What world does that workflow exist in?

Don’t copy the URL, just Copy Image and paste that, 5.0 Editor 

That is a data point I don’t have. I will admit I am not doing a lot of client work where content creation is something I am involved with and have no idea if there is an audience for this beyond getting devs to turn in content faster, but I wanted to say my peace about it somewhere. Let me know on Twitter or in the comments what you think.

Thanks for listening. Next post should go back to my normal format.

2 thoughts on “A case for Markdown and the WP 5.0 Editing Experience”

Leave a Reply

Your email address will not be published.