What this section is
Notes on the programs used to do the work, such as the editor, the package manager and the site generator, and how they’re set up.
Most tools are easy to install. Setting them up well is where the decisions are: which settings to change, why, and what breaks if you get it wrong. A tool gets a note here once its setup involved real decisions worth remembering, not just for being installed.
This isn’t a course to read in order. Each set of notes stands alone; open the one for the tool you’re using.
What’s here
- Quartz: the program that turns this vault’s notes into a website. 6 notes on how it works, configuring it, styling, layout, the graph view, and publishing. Based on this site’s actual setup.
- npm: not how to use npm (JavaScript’s package manager), but the settings underneath it: where packages are downloaded from, the
.npmrcsettings file, and logging in to private package sources, which often works on your laptop and fails in automated builds. 2 notes. - Agent skills: the
SKILL.mdfile format that teaches AI coding assistants a task, and why a skill can silently fail to load. 1 note. - OpenClaw study partner: setting up a local AI study partner that runs on this laptop without the internet, can read the vault but not change it, and quizzes you instead of giving answers.
- Neovim setup: configuring the Neovim text editor.
Related
- Git: the most-used tool of all, with its own full course.
- Linux: the system these tools run on.
- The home page: the map of every subject.
About this section
- Not covered yet: the shell itself (zsh settings, prompt and history; scripting is in Bash Scripting), tmux, and Docker as a tool for local development rather than for deploying.
Jump to a subject
Software engineering
Infrastructure & security
Computer science
Hardware & engineering