Live since

Settlers Journal

A development journal for a Settlers of Catan web application, published as a searchable static site with Astro and Pagefind.

Settlers Journal on a phone
What it does

Building in the Open, One Session at a Time

Journal entry titled City Placement Validation, Double Resource Collection, and Robber Blocking, with its TLDR
01

One Entry per Session

Every work session on the Catan app ends with an entry: a TLDR, the main work, challenges, learnings, and screenshots or code.

Search page showing three results for robber, with the matching words highlighted
02

Search Every Entry

Pagefind indexes the built site, so full text search runs in the browser with no search server.

Tags page listing angular, architecture, astrojs, catan, java, postgres, react, svg, testing, and more
03

Browse by Topic

Tags group entries by subsystem and tool, from java and postgres to react and svg.

By the numbers

At a Glance

45journal entries
~11,500words of prose
2years, 2024 to 2026
0search servers
How it's built

From Work Session to Searchable Page

  1. EntryMarkdown Template
  2. Astro BuildAstroPaper Theme
  3. PagefindIndexes the Built Pages
  4. NGINXStatic Files over HTTPS

Built with

AstroAstroPaperTypeScriptTailwind CSSPagefindShikiSatori
Key takeaway

Writing an entry right after a session is easy. Reconstructing why a decision was made days later is not, so the fixed template matters more than any feature of the site.

Build Notes

Challenges, learnings, and what's next

Challenges

  • Maintaining consistent journal entries alongside active development requires discipline and time.
  • Pagefind requires a completed dist/ directory before it can index anything, so search does not work on the dev server.

Learnings

  • Pagefind integrates cleanly into an Astro site with no server-side infrastructure, and the default search UI requires no customization.
  • AstroPaper covers most of what a development journal needs out of the box: dark mode, RSS feed, tag filtering, OG image generation, and pagination.
  • Writing entries close to each development session is significantly easier than reconstructing decisions days later.

Next

  • Add a stats or summary page showing total entry count, most-used tags, and development activity over time.
  • Cross-reference related journal entries by linking between sessions that cover the same feature or subsystem.
  • Automate parts of the entry creation process, such as pre-populating the date and linking to relevant commits.
  • Explore RAG systems that could answer questions about previous design choices or jog my memory.
  • Review past journal entries and use them to improve the development workflow.
Keep exploring

More Apps