I hired some writers to create content for my business and they know and understand how to use markdown and html. Further, we all use Grammarly to remove spelling and grammatical mistakes, along with helping us with writing better content.
However, posting on Jekyll is a challenge. Usually, our posts have at least one image (a featured/cover image), and sometimes other tables and figures. I do not want my content writers to worry using Jekyll + GitHub Pages + Git + creating images + linking to said images. They are great writers and not technical and just want to write as if they are in a basic word processor (similar to writing content in Wordpress).
This made me wonder if there are any front-end tools for writing Jekyll articles that will allow you to write the post, with images, and then have it automatically post the code to the GitHub repo and commit those changes.
Does such a tool exist and or are there ways to cobble such a solution together?
I think what you want is to hook up your Jekyll repo to a CMS. There are several open source flavors out there and services with generous free tiers. Most can get you close to the Wordpress editor experience so your content folks don’t have to worry about writing Markdown, HTML, or dealing with git.
This thread has some links to a few of them… there are many out there.
Okay, thank you. It looks like a headless CMS is closest to what I am looking for. Unfortunately, all these services seem to want to help you manage your site and put their custom technology in front of it. I was hoping there was just an easy way to write the markdown in a website and then have it post to GitHub pages, along with any images or other media.
Thanks for your help. I am playing with Forestry now and it seems to do a pretty good job. The documentation of how these services work leave a lot to be desired. I got the impression they will import your site and the GitHub pages are obsolete, but it looks like, at least with Forestry, it allows you to post directly to GitHub. I will be trying that for awhile and see how it goes.
It helps to think of these services as a more visual way of editing your site’s content. They don’t import your site, they’re mostly accessing your git repo, reading the data, then pushing commits back to it as you edit pages/posts/etc.
When it pushes those changes back, GitHub Pages and the like rebuild your site. Same thing would happen if you were editing the files directly on GH or pushing from a local development setup.