I released rookery 0.1.0 at the start of last week, and over the course of it I’ve iterated through a couple of versions to reach 0.4.0.
This fast release cycle is mostly a function of wanting to deploy updates quickly on this site and my main blog, both of which employ a deployment pipeline that pulls Rheo and its packages from published releases. In the future it will probably make sense to set up some sort of prerelease pipeline so that I can dogfood new functionality on my own sites first, but as rookery hasn’t actually been announced anywhere yet (besides these weeknotes), I figure that it doesn’t have any real users who would be impacted. 1
The features and default styling has changed fairly significantly since 0.1.0, so I again encourage the interested reader to check out rookery’s documentation for a more complete account. Highlights include a more thorough comparison between rookery and other similar tools and a tag system that complements the idea ecosystem. The tagging is conceptually and visually inspired by DEVONthink, and includes rudimentary integration with rookery-search, which you can see in action on the documentation site. An easter egg is that if you type the prefix tags: in the search modal followed directly without a space by some characters (i.e. tags:con), you can fuzzy search by tag names.
I also made my Math(s), Philosophy, History reading group site a rookery, sketching out the authors of texts we’ve read as their own ideas as a placeholder for how I intend to deepen the presentation of our group’s thinking there. The next phase of adopting rookery is to migrate my personal knowledge base to rookery, which is currently a flat folder of Orgmode files. These four projects—my weeknotes, my blog site, a reading group site, and my personal knowledge base—are a pretty good representation of projects that I feel the current version of rookery should be able to support.