Summing it up, StackEdit mitigates a lot of the weaknesses associated with the editorial workflow for Jekyll when you are a lonely blogger without an complete tech team and infrastructure for backing you up. For you that uses websites on public repositories, maybe this is what you’ve been searching all along!
In fact, this post is actually an working test of using it as an CMS.
For this to work, there are a number of steps:
The last step depends a lot on your Jekyll configuration. For example, on my gitlab website I use this template for creating posts on my blog or documents sections:
--- layout: page } --- Publish now Update current file publications. }
The yamlProperties on this template is given by the parameters on File properties for each StackEdit document, which for this post are:
title: 'An unusual and practical CMS for Jekyll: StackEdit' author: Danilo Lessa Bernardineli tags: 'jekyll, cms, markdown, stackedit, bloggin' categories: blog date: '2019-06-09'
Afterwards, publish it on your Jekyll repository and into the correct filepath, and you’re done! StackEdit will automatically publish newer editions when you edit it, and you can visualize your output while you’re editing your document. Awesome