Jekyll Rest provide an API end point to write new posts for sites using Jekyll and Github.
It's primary use case is to enable automating content creation. It is probably not for everyone. However, if you are trying to write more outside of walled gardens like Twitter, you may find it useful.
Today, it has a single end point,
create_post. The create_post end point does its best to take whatever content is handed to it and create a corresponding file on your git repo.
If there is no body and title, no post will be created on Github.
application/jsona JSON document may be submitted
You should be able to set it up by clicking the following Heroku button.
The following environment variables are available:
I use Zapier to manage all of this. You can set up an email at Zapier to receive an incoming email and then send a webhook to this project. You can do the same for SMS. Setup Twilio (or your favorite service) to send a web hook to Zapier. In turn, have Zapier send a webhook back here.
Ultimately, this whole thing works much better if you are using Netlify, Github Page, or something else that will trigger a rebuild/publish of your site when a Git push is completed.
bundle exec rspec
Right now there is no support for assets. I would love to see this added in the future. As I understand it, you can only submit one file at a time to the Github API which was one of the reasons I did not tackle this from the start.