Python

Using MKDocs

As you can tell, this site is no longer based on Publii CMS (which is still a very good CMS). After spending a few hours with MkDocs, I’ve been tempted to use that instead, as I can do pretty much everything using Vim. I’m still migrating the content, so this site is a work in progress. Using a static site generator might initially seem like a long-assed way of getting a basic site up, but once MkDocs is installed and running, and the site’s customised, we only need to worry about a single configuration file and where to place the content.

Things to do with .ipynb files

Although Jupyter Notebook is designed primarily for data analysts, I think there are other use cases in which it can be an effective method of distributing Python code and associated documentation in a single .ipynb file. There are other editors we can use to handle .ipynb files: JupyterLab, Deepnote and Visual Studio Code (with the right extensions) are just a few I’ve tried. Jupyter Notebook is essentially a markdown editor with an embedded Python interpreter that executes whatever code is included in a document.