> Preaching to the choir! I'd be surprised to find anyone on HN with an argument against writing your blog/book in markdown with vim. Time. Wordpress for the m

> Preaching to the choir! I'd be surprised to find anyone on HN with an argument against writing your blog/book in markdown with vim. Time. Wordpress for the most part is WYSIWYG. With any of these static site generators I have to learn the conventions, work out how to install and edit themes and generally there is a lot of faffing. > Now what I'd be interested in seeing is an argument for traditional publishers or WordPress users to switch to this sort of stack. There isn't one. It doesn't scale. There is a reason why companies typically use some sort of CMS system. It isn't just ease of editing. You can control when, where and who can publish content to the site. You can localise content. You can version control content. You can have stakeholders review content before it is made public. Doing that with vim, git and a static site generator and some bash scripts is a faff and will frustrate non-techie people that just wanna copy and paste content from Word.