How my personal website is architected and built.
All of the content files are written in Obsidian flavored Markdown. They're copied from the Obsidian vault directory on my local machine into my
The content is stored in version control simply to reduce storing and fetching it from somewhere else.
content/notes/<DIRECTORY PATH>/<FILENAME>and served as
content/posts/<FILENAME>and served as
When the site builds, the paths are flattened out.
As an example, the file for the content you're currently reading lives in the vault path
40 - Projects/curiouslychase.com. When the content is served, it will be served at
Serving content at the
notes root makes the URL path durable. I can move it into a different directory and the URL path will persist at the same location it did before.
I use a few scripts to stitch everything together:
status: publishedinto my git repo's
I was originally using Obsidian Publish and serving the site Using Fly.io and NGINX for Proxying Obsidian Publish but found the solution wasn't meeting my needs.
dv.table(["Note", "Description"], dv.pages().filter((p) => p.status === "published").map(p => [p.file.link, p.description]))
dv.list(dv.pages().filter((p) => p.status === "published" && !p.description).map(p => p.file.link))
Subscribe to my Newsletter
Every other week I publish the Curiously Crafted newsletter.
In it, I explore the intersection of curiosity and craft: the people who make stuff, what they make and the way they pursue the craft of making.
On The Web
See all of the places I have a presence on the web.