Working Notes: a commonplace notebook for recording & exploring ideas.
Home. Site Map. Subscribe. More at expLog.

About

Just for posterity, here's an older version of the about page that described the slipbox I'd originally published on explog.

The current site is much simpler, though I've maintained some old habits:

• showing indicators about the length and age of a note
• as minimal as possible for simplicity: it's the writing that matters
• I've switched from org to markdown; there are still artifacts of org mode strewn throughout the site I'd like to fix up

The main page of knlb.dev explains why this website exists.

The current version of this site is generated by a 500 line python file (with inline html and CSS for all the formatting) relying on uv for execution with the prefix:

#!/usr/bin/env -S uv run --script
# -*- mode: python -*-
#
# /// script
# requires-python = ">=3.12"
# dependencies = [
#    "pyyaml", "flask", "markdown-it-py",
#    "linkify-it-py", "mdit-py-plugins"
# ]
# ///

The corresponding github action to publish it is:

name: Build and Deploy Notebook

on:
  push:
	branches: [ main ]
  workflow_dispatch:

permissions:
  contents: read
  pages: write
  id-token: write

concurrency:
  group: "pages"
  cancel-in-progress: false

jobs:
  build:
	runs-on: ubuntu-latest
	steps:
	  - name: Checkout
		uses: actions/checkout@v4
		with:
		  fetch-depth: 0

	  - name: Install uv
		uses: astral-sh/setup-uv@v4

	  - name: Set up Python
		run: uv python install

	  - name: Build site
		run: ./bind -p ./pages -o ./build

	  - name: Upload artifact
		uses: actions/upload-pages-artifact@v3
		with:
		  path: ./build

  deploy:
	environment:
	  name: github-pages
	  url: ${{ steps.deployment.outputs.page_url }}
	runs-on: ubuntu-latest
	needs: build
	steps:
	  - name: Deploy to GitHub Pages
		id: deployment
		uses: actions/deploy-pages@v4

Previously

• This is a collection of ad-hoc notes from reading, thinking and exploring: written for myself as I learn. Having them publicly available gives me an easier way to access them when I want, and to occasionally link to when I need to share information.
• More carefully considered notes are published on ExpLog. These days, I'm most likely to respond on Twitter if you have any comments.
• I edit these notes using LogSeq, which you should check out if you haven't; they're then automatically published every couple of hours using a Github Action. I use Org Mode to write -- and then rely on running Emacs in batch mode to export to HTML; the configuration is an adapted version of the one used to publish expLog.
• Visualizations
  • The light vertical line on the right shows the full commit history: ticks to the right mark days, ticks to the left identify commits.
  • The dark border on top of links in the index indicates the file size, to quickly distinguish between detailed and superficial notes.

— Kunal