My github blogs have proliferated over the years and many of my strategies were poorly thought out. Cleanup is in order after a few weeks of work with Hugo. The goal for the next week or so will be guided by the following strategy.
Blog post or README text?
Convert posts from various blog branches to this blog.
- https://tomrake.github.io/test-blog - delete soon.
- https://tomrake.github.io/my-blog - convert posts to my legacy portion.
- Code Project blogs I have several code projects with related blogs, this information needs to be divided between the project README and a related blog post. Configuration and API details of a component should be in the README, along with a link to longer explanation posts and use case posts. When explaining a problem to be solved, it should be in a blog post.
The Code projects
Updating my site with org-mode
I have updated blogging procedure
This is of a technical interest on how I actually produce my blog. I have always written by blog pages in emacs and historically have authored in Markdown syntax and the Beautiful Jekyll theme on GitHub. I now author my pages in org mode and use org-publish to render them to the Jekyll repository. Next I ensure that the blog posts are in the _posts/ folder and commit those changes to the git image of my site. Finally, I upload and push my local site to GitHub.
[Read More]