joshlong / joshlong.github.io-content

this repository contains the content that, when changed, triggers a CI build resulting in the automation required to generate the new site and then push the change to the relevant Git repository.

Content for the JoshLong.com blog

This blog uses jbake to process the Markdown, Asciidoctor and HTML files and turn them into content that people can read on the blog.

Make a change (such as editing an existing file or adding a new one to, for example, content/jl/blogPost/*) and then git commit and git push the change and you'll trigger a CI build. The CI build runs jbake on the content, then git clones the Github pages site for the actual blog itself, adds the updated site to that build and then git add and git commits everything to the repository. The changes then usually appear live on the blog. The whole process takes a minute or so. Just keep refreshing and your change will land, eventually.

joshlong.github.io-content's Issues

make the site ingest all the content from the profile-processor

https://github.com/joshlong/advocacy-profile-processor/issues/1

the problem is that there's an unnatural coupling here.