Short documentation about how I created this blog site
Setting up this blog
General thoughts and considerations
Since my portfolio site Built by talented wrnr is optimized for image and video content and doesn’t really focus on text, I wanted to create a dedicated blog, mainly for my own documentation purposes (like a lot of people I tend to completely forget about how I solved something once it’s been solved), but also to share some of my findings and processes. Lastly, there have been countless instances where obscure blogs or videos helped me solve a (usually self-inflicted) technical problem at work or at home, so my goal is this one achieving the same for someone else.
What software is this blog using
Since the whole process of creating the blog should not take too long while at the same time offering enough features to work with and extend a Markdown based workflow, I decided on Hugo as a framework and HugoTex as a theme.
I used Notion as a personal Wiki for quite some time and have since switched to Obsidian, which is where the posts on this site are written.
To deploy the site, I’m currently using Vercel which is installed to my blog repo on GitHub, though this might later change to something more robust like Coolify.
As a general guide for this kind of blog setup, you can also refer to this post by creator NetworkChuck.
What will be posted here
Since I work in CG and VFX, most of the problems I have to solve are work related. For my projects I mainly use Houdini and Nuke, so definitely expect some posts to focus on that topic.
Because these software packages can require a somewhat larger infrastructure to make more complex projects happen without surprises, I started using Deadline to manage renders, and work with a NAS for storage. This is mainly what got me interested in adjacent networking and self-hosting workflows. I’m still relatively new to all the tools available and want to learn much more, but expect some posts to be about using my third-hand ThinkCentre as a Proxmox node to host my render manager among other services.
Generally, I want to share whatever fits the broad category of “technical setups I build that could benefit from a structured documentation”. I hope some of it helps.