Update content: Remove preface from trip report and expand colophon

src/content/notes/2024-eastern-sierra-trip.mdx

@@ -18,19 +18,6 @@ import DSCF1605 from '@assets/2024-eastern-sierra-trip/DSCF1605.jpg'
 import DSCF1631 from '@assets/2024-eastern-sierra-trip/DSCF1631.jpg'
 import DSCF1634 from '@assets/2024-eastern-sierra-trip/DSCF1634.jpg'
 
-
-## A preface about motivation
-
-Which I will eventually move somewhere else.  The idea for creating photo journals, and the entire website redesign, started a few months ago.  Earlier this year, I had the opportunity to do a photography mentorship with [Jakob Lilja-Ruiz](https://www.jakoblr.com/) (aka [portra papi](https://www.instagram.com/portra_papi)).  One of those weeks was dedicated to curating your work, a skill he felt was among the most underrated in photography.
-
-Curation is something I've never put much thought to.  I cull the bad photos, but hadn't considered how to arrange the good.  I've tried to develop the practice over the past 6 months as I curated series to post on Instagram, but I struggled with it.  I wasn't finding imaginative choices, and was mostly coming up with collections of similar things like silhouettes or certain landscapes.  And the required regularity of posting that social media encourages made it feel like a chore.  I found myself wanting a different format in which to think about curation.
-
-Many of the highlights of my year, both experientially and photographically, are the roadtrips I take exploring the Western US and documenting those travels has already been the focus of my photography for several years.  Taking inspiration from [Bound for Nowhere](https://www.boundfornowhere.com/) and [Adventure Taco](https://adventuretaco.com/), I realized the curation I was most interested in was documenting those travels in both prose and visual.  I imagine that being a thread I can pull on to spend more time with my collection and think about curation, starting with travel chronologies and expanding to other forms in time.
-
-And so I set about doing so in my standard fashion.  Rather than start a photo site using any of the high quality options that exist, I completely rebuilt my website from scratch.  I wanted control over how I combined text and image and am building the pieces that allow me to do so.  This is the first attempt at doing so.  It's not quite where I'd like it to be, but it's good enough to start.
-
-## The trip
-
 This was a short trip with modest ambitions.  I was in need of a few nights camping and a general change of scenery.  No strong itinerary or route to keep to this time.  I wanted to get a least one good hike in.  I had rented the Fujifilm 55-140 telephoto lens and wanted to dedicate time to photography sessions and understand where I could use that in the pictures I want to make.  
 
 The Eastern Sierra is my favorite part of California, and I try to visit it at least once a year.  I had missed last year's visit and it was time for a catch up.  So I packed and gassed up the truck and headed east.  

src/content/notes/colophon.mdx

@@ -7,17 +7,31 @@ modifiedAt: 2024-11-10
 ---
 import Sidenote from "@components/Sidenote.astro";
 
-The publishing term *colophon* is a statement in book a containing information about the publication of the book.  In the early days of personal webpages, most sites were custom built or assembled from the parts bin, the term was adopted for the "how I made this" section of someone's site.  And so that tradition continues here.  
+The publishing term *colophon* is a statement in a book containing information about the publication of the book.  In the early days of personal webpages, when most sites were custom built or assembled from the parts bin, the term was adopted for the "how I made this" section of someone's site.  And so that tradition continues here.  
 
-### Build
+## Content
 
-The site is built using the [Astro](https://astro.build/) framework.  I'm not really qualified to weight its pros and cons.  My go-to guy for everything frontend, [Sam Breed](https://sambreed.dev/), uses it for his site and that's good enough reason for me.  While I'm not versed in frontend frameworks, it does seem sensibly put together and packages a number of ideas I'm vaguely aware of being good things.
+The motivations for the latest version of this site were twofold.  1) I wanted a public notebook 2) I wanted a medium to present my photography.
 
-Astro [components](https://docs.astro.build/en/basics/astro-components/) have allowed be to build the site out of self-contained chunks that serve one purpose, and reuse them across both the HTML and Markdown portions of the site.  And Astro's separation of site content from the framework is another huge selling point.  The majority of the site content is Markdown files, which frees me from having to create them in my coding editor.  
+I've been an appreciator of a personal digital notebook for the better part of a decade, doing most of my work in folders of Markdown files.  Tools like [Obsidian](https://obsidian.md/) and [Roam Research](https://roamresearch.com/)  reinforced and expanded that working pattern.  At this point I do the majority of my personal digital work within Obsidian.
 
-The end result is I'm able to write page this in [Obsidian](https://obsidian.md/), which is much more amenable to writing prose than VS Code, while at the same time being able to easily introduce fairly complex modifications to the layout/style when I want to.
+I wanted to have a public notebook as well, sharing in-progress work and growing it over time, which I see the [notes section](/notes) of this site growing into.  Inspiration for this came from many places, with [Andy Matuschak's notes](https://notes.andymatuschak.org/) and [Maggie Appleton’s digital garden](https://maggieappleton.com/garden) being some of the biggest influences.
 
-### Styling
+The idea for presenting photography started a few months ago.  Earlier this year, I had the opportunity to do a photography mentorship with [Jakob Lilja-Ruiz](https://www.jakoblr.com/) (aka [portra papi](https://www.instagram.com/portra_papi)).  One of those weeks was dedicated to curating your work, a skill he felt was among the most underrated in photography.
+
+Curation is something I've never put much thought to.  I cull the bad photos, but hadn't considered how to arrange the good.  I tried to develop the practice over 2024 as I curated series to post on Instagram, but I struggled with it.  I wasn't finding imaginative choices, and was mostly coming up with collections of similar things like silhouettes or certain landscapes.  I found myself wanting a different format in which to think about curation.
+
+Many of the highlights of my year, both experientially and photographically, are the roadtrips I take exploring the Western US. Documenting these travels has been the focus of my photography for several years. Taking inspiration from [Bound for Nowhere](https://www.boundfornowhere.com/) and [Adventure Taco](https://adventuretaco.com/), I realized the curation I was most interested in was documenting those travels in both prose and visual.  This could be a thread to explore my photo collection more deeply. My hope is over time the travel chronologies serve as an entry point to other forms of curation.
+
+## Build
+
+The site is built using the [Astro](https://astro.build/) framework.  I'm not really qualified to weigh its pros and cons.  My go-to guy for everything frontend, [Sam Breed](https://sambreed.dev/), uses it for his site and that's good enough reason for me.  While I'm not versed in frontend frameworks, it does seem sensibly put together and packages a number of ideas I'm vaguely aware of being good things.
+
+Astro [components](https://docs.astro.build/en/basics/astro-components/) have allowed me to build the site out of self-contained chunks that serve one purpose, and reuse them across both the HTML and Markdown portions of the site.  And Astro's separation of site content from the framework is another huge selling point.  The majority of the site content is Markdown files, which free me from having to create them in my coding editor.  
+
+The end result is I'm able to write this page in Obsidian, which is much more amenable to writing prose than VS Code, while at the same time being able to easily introduce fairly complex modifications to the layout/style when I want to.
+
+## Styling
 
 The site style is borrowed from [tufte-css](https://edwardtufte.github.io/tufte-css/).  I've been a fan of the layout and typography of his books since I first encountered them.  The aesthetic feels like modernization of classic academic texts like *Principia Mathematica* and *On the Origin of Species*, and having a style that more closely resembles a printed page than a chromed website appeals to me.