[busterarm]

I was a professional web developer and occasionally moonlight as one. If you have non-savvy people entering content, WordPress is, in most cases, the only sensible choice.

I can turn a better site around that suits most peoples' needs in Jekyll these days in less time. I took the best of both worlds here and developed a workflow of: 1) private WordPress for content editing categorized content in Kramdown using only the ACF Pro and s3 uploader plugins 2) a process that builds and deploys a jekyll site to an HAproxy load-balanced NGINX cluster whenever anyone clicks Publish.

It pulls the content directly from the wordpress database at build time and the site uses webpack and whatever javascript niceties you'd expect from a site developed in 2018.