Somehow, I'm doing that thing again where I want to make something simple, and end up making a whole infrastructure... Blog-o-Matic manages your blog content so you can serve your content with a static file server. Blog-o-Matic is made to solve these problems:
*.mdfiles with any tool With Blog-o-Matic-optimized content, you should be able to view and edit this content in something like Byword, or your favorite text editor. You should have the ability to sync the input directory over something like iCloud, Google Drive, or Dropbox to make edits, then publish changes on your computer.
Process content into a standard format for consumption Should minify images into multiple sizes for responsive design, transform
md => html | react components, etc.
Should have its own preview editor Should have a simple static server for use during the development process. This will serve the built files that Blog-o-Matic deploys to the static file server, so you can preview it in the form of a website.
Should publish static files Blog-o-Matic should be able to build and publish any combination of md, html, and minified resources to a static file server. Should keep track of file creation, and have some basic presets for publishing (scp, AWS, export to file, etc)
More detailed example usage is found in each individual package: