For exercise I put blog.solvaholic.org on Amazon Web Services S3 with a CloudFront front-end. I used Hexo to build the content, and pushed it up with awscli. That works and was totally worth it, and now I’m ready to do away with that complicatedness.
Yes, it is that easy. The instructions I found, though, all work with assumptions that .. um .. are unaligned with the assumptions I made.
Here are some of the resources I used :
If you put Jekyll-flavored .md files in a GitHub Pages repo, GitHub Pages will render them for you just like Jekyll would have if you built the site locally and then published it.
When you use one of the Pages-supported Jekyll themes, Pages will render your site with the layouts, assets, and styles for that theme. These are available in https://github.com/pages-themes for each supported theme.
You may override those styles and layouts by placing your versions in your repo.
The Jekyll workflow I expected is like :
The GitHub Pages Jekyll workflow is like :
I’ll have to circle back around on this and fill in more details. Mostly :
index.md
, replace index.html
with :---
layout: post
type: home
---
{% if site.posts.size > 0 %}
<ul>
{% for post in site.posts %}
<li>
<strong><a href="{{ post.url }}"></a></strong> / <time datetime="{{ post.date | date_to_xmlschema }}">{{ post.date | date: '%b %-d, %Y' }}</time>
</li>
{% endfor %}
</ul>
{% else %}
<p>No posts yet!</p>
{% endif %}
/_posts
and add content to it with filenames like 2017-04-10-Post-Title.md
:---
layout: post
title: Post Title
---
Paragraphs of words and stuff.