Hi there, a few months ago I decided, I would want to go to a form of webspace where I dont have to spend money. Although it’s only a few bucks, I thought it would be time to move on…​ this is basically a tutorial to move over to github pages…​

Edit from 20-04-2025: Previously I had a Makefile-based approach, but this was not the ideal way, so now I changed it to utilize github actions instead

Today, I want to show you how you can modify your Odoo frontend, I wont go to deep into owl and instead just show the basic steps for implementing modifications and changes via HTML5, CSS und javascript.

Lets dive in and wet the toes.

We begin by writing a short cut-through css file to change and modify the view (in my example case here removing carets on the provisioning reports) but feel free to change any other element (or attribute) you want

When you fire up your browser to visit a website, you most probably did not noticed a very important mechanism underlying the browser and working in the background. Caching. Caches are used everywhere to optimize and improve access times and such in consequence the overall performance (of a site). Caching in the browser for example means, that ideally only the portions of the website that changed are loaded from the www. All else was already loaded before and did not change, thus needs no reload. Portions that are no longer up-to-date become invalidated (also known as cache-invalidation) and are loaded anew from the source. There are two types of very different caches in the computer

This is a small, incomplete list of topics I’d like to write about in the mid- to far future.

Today I want to introduce a solution for a usability-problem I had in Odoo recently. In Odoo 12 there is a lock button next to the edit / save button, and you have to click both to (1) unlock the page and (2) make it editable. This should be done in one step, effectively removing the locking mechanism used in the Delivery Orders (class StockPicking) and Manufacturing Orders (class MrpProduction). The solution requires an xml and a javascript-file as well as a dedicated web-controller. The soliution is presented below.

As the blog grow bigger and after the move to hugo, I noticed a gap in the workflow,since a blog and its content itself are different entities, I wanted to handle them as such, that led me to a cleanup of the original source code for blog, where I moved the content folder into a different repo, called hugo_content, the former repo I called hugo_blog. ---

In my case, this means you have to clone the repo hugo_blog first go inside the new directory (cd hugo ), checkout its branch 'hugo' and then do a clone of the repo hugo_content.

Since one week my blog is build on the static-site-generator Hugo. I wanted to move to Hugo far earlier, due to the wide variety of themes. However this required the move from Asciidoc to Asciidoctor, and I experienced a few problems with the integration of Asciidoctor into my existing workflow. As the approach of rendering the latex-equations in the asciidoc-documents no longer worked, I decided to move on to client-based rendering of formulas, like done in KaTex and Mathjax.

I picked up Nikola some months ago as I was searching for a simple static-site-generator to setup a blog with minimal effort.

To make things a bit more interesting and at the same time easier we will use Nikola in a Docker container. So I require an almost basic understanding for Docker here.

First create a directory on our host system, where you want the files stored, e.g. 'blog' in your home directory.