Log + Scribe

Log is Fisher’s home for the things he wants to share and keep: longer posts, short notes, photos and selected pieces of an older online history. Scribe is the editor behind it. Together they cover both sides of a personal publishing system: a stream worth browsing and an authoring experience practical enough to maintain from a phone.

The project started with wanting to blog again. Bringing back Tumblr and Instagram archives expanded that into a different question: which parts of an online identity should depend on someone else’s platform? Fisher’s description of the destination is simple: “my home base is my website.”

A stream for different kinds of content

A short note does not need the ceremony of a titled essay. Log gives posts and notes different treatments while keeping them in a shared timeline. Photos can be browsed in place; related bursts of notes fold together rather than consuming the whole page.

Tags provide another way through the archive, and search makes something findable after it has slipped down the timeline. The aim is a selected history and an ongoing place to publish, rather than a complete record of every online activity.

Writing from a phone

Scribe grew out of the practical side of that idea. Fisher initially expected to write Markdown in a text editor using a Pages CMS schema. As more of his work moved to his phone, he wanted an editor shaped around the content. His experience with timeouts and lost progress in the earlier online editing workflow made retaining work a priority.

A post gets a document editor, with formatting and image handling alongside the text. A short photo note gets a lighter workflow without requiring a title. Tags have their own management view. The same site schema remains underneath, but every field does not have to carry equal weight in the editing experience.

Keeping work between visits

Scribe saves editing progress to its backend and keeps a browser-local copy of edits. Returning to an unfinished piece is part of the normal workflow. GitHub synchronization connects that authoring work to the Markdown files that build the site.

Those safeguards reduce the risk of losing an edit; they are not a promise that every interrupted upload or publication can recover without intervention. Markdown remains the storage format, though saving through the editor can normalize formatting.

A static home

The stream, tag pages and search are built into a statically generated Astro site. Client-side interactions make the archive navigable without turning the whole site into an application server. Comments and subscriptions sit alongside that static foundation.

Log and Scribe are in personal use. Ramble sits earlier in the process, helping Fisher work through thoughts before the sustained editing that turns them into something to publish.

The demonstrations use invented posts, notes and photos in isolated local copies. No private archive or drafts are shown.