Finally loading content into the site's repo

If you had watched my site's repo today, you would have seen that I added seven new posts to the site. These have been sitting on my computer already written, but I've been too embarrassed to commit them to version control until they were proofread. I've got four more written that need to be proofread.

Thinking of new blog features

Yesterday I created a drafts folder for the site, and today I added a database column that tracks if a post is in draft or if it's published. Draft posts are ignored by Git.

I'm still enjoying that all of my content is in version control, but there are parts of editing the content that are downright painful (literally: my wrist hurts).

Here's the current flow:

1. I make a change in a markdown file.
2. I jump to terminal and rerun the import script.
3. I switch back to my Chrome window.
4. I hit ctrl + r to reload the page.
5. I select the text and have my computer read it to me.

After I proofread my remaining content and I've launched this site, the first feature I'd like to add is a watcher that automatically re-runs the imports when the content changes. I'm chasing that great Hugo DX, but with Rails for some reason.

After that, I'd like some way to configure dates in the UI.

That's all for tonight: my wrist really hurts.

EDIT: It's still May 18th and I haven't gone to bed yet. I just went on a walk and thought how cool it would be to build text-to-voice into the front-end of the site when it's in development mode. It turns out there's a simple browser API for text-to-speech. It also sounds a lot better than the hacky Linux selected text to speech that I built. And here I was thinking that I'd need to build some kind of back-end service that streamed audio to the client.