Skip to content
alkemist

Logs

Short working notes: observations, decisions, and questions still in motion.

  1. Start with one concrete slice

    A working page is a better test of an authoring model than a menu of proposed capabilities.

    For a new publishing feature, begin with one reader journey. Here it is: choose a section, open a short entry, and return to the section index without losing the distinction between a note and an article.

    That slice checks the things readers actually encounter: the content schema, generated path, header navigation, readable text width, and the route back to the collection. More fields only become justified once a real entry needs them.

    The same discipline applies to scientific components. A chart, model, or theorem block should earn its public API by carrying one real piece of work all the way from source to a reader’s browser.

  2. Let the route explain the kind of work

    A quick note on keeping developed writing, experiments, reference, and a guided path legible.

    A publishing site collects several different tempos of work. A design decision may need a fully argued article. A running observation may only need three paragraphs. An interactive model needs room to be used, while installation details need stable reference pages.

    Alkemist keeps those jobs visible in the URL. Blog is for developed writing; Logs is for short working notes; Labs is for things to operate; Docs is reference; and Book is a path where one chapter prepares the next.

    The separation is modest, but it prevents a useful note from pretending to be an essay and prevents a tutorial from becoming an unfindable stream of posts. A site can choose which section labels appear in its navigation through src/lib/sections.ts.