What is Seed Hypermedia?

Seed Hypermedia is an augmented web for writing, publishing, and collaborating on documents in a peer-to-peer network. Instead of being locked into a single platform, documents in Seed have durable hm:// addresses, readable paths, version history, comments, citations, and built-in collaboration.

It combines some of the strengths of documents, websites, and shared knowledge bases: you can write structured content, organize it into spaces and subpages, link directly to sections, track changes over time, and discover how ideas connect across documents.

In practice, Seed Hypermedia is both a protocol and an app experience: a way to create portable knowledge that is easier to reference, discuss, and preserve beyond any one service or company.

What I do in Seed Hypermedia

I work on turning Seed Hypermedia’s ideas into product features and a reliable app experience. My role spans product implementation and platform quality, with work across interaction details like links and comments, interface development, release readiness, and overall reliability.

Areas I work on

My work spans several connected areas:

Product implementation: shaping ideas into concrete features and usable workflows

User experience details: improving interactions such as linking, commenting, and everyday document use

Interface development: building and refining the frontend experience

Reliability and quality: identifying issues, improving stability, and helping make the product dependable

Release and platform work: supporting the practical work required to ship and maintain the app across environments

Internal coordination: contributing to discussions, priorities, and the translation of ideas into execution

Current focus

My current focus is on improving the quality of the Seed experience through product implementation, interaction details, and reliability work. This includes helping refine how core features behave in practice, making the app easier to use, and contributing to the day-to-day work needed to move projects from concept to release.

How I work

I tend to contribute where product thinking and implementation meet. I like working on the details that make a tool feel clear, reliable, and ready for real use. This includes translating rough ideas into concrete behavior, refining workflows through iteration, and helping make sure the final result is both practical and coherent.

I also value documentation as part of the work itself: not only shipping features, but making the reasoning, process, and outcomes easier to understand and revisit.

Work and contributions

This section documents the projects, features, fixes, and ongoing areas of work I have contributed to at Seed Hypermedia. It can include short summaries, dates, my role in each effort, and links to related documents, discussions, or implementation notes

Embeds Design Proposal

Exploring alternative visual treatments for embedded content from other documents, replacing the current green left border approach.

Improving Editor Block Rendering

How we rethought the visual foundations of our document editor - fixing five interconnected rendering issues by committing to one alignment principle.

The Case Against electron-trpc: When Type Safety Becomes a Performance Tax

The danger of making critical decisions without data and prioritizing developer convenience over user experience.

Experiment: Forum view

What if documents can define a type and have "special views"?

Experiment: Improve performance in-site interactions

I want to improve the experience when we navigate inside a site. and here's the result: The whole project includes benchmarks on interactions, specially when try to comment. there are some good improvements made. You can see the PR here: https://github.com/seed-hypermedia/seed/pull/297

All Documents - directory

Idea to show the Directory in a full page. Imo if we have this we don't need the left hierarchical document navigator. However, we can have both. They are not incompatible! Inspirations Sketches Demo Mockup

Reliable document references

Keep child documents discoverable through reliable parent-reference updates across web and desktop. A shared actor system coordinates publishing, renaming, moving, and deletion, preserves unpublished draft edits, and provides bounded retries, explicit deletion confirmation, and persistent recovery history when updates fail.

Explore implementation plan

Private Document Hierarchy and Authorization

Keep Focused Comments Visible

Keep URL-focused comments visible after their parent thread renders in the main view and right panel.

Stable Document Heading Implementation Plan

File Browser Intent Prefetch

Stable Document Heading Layout

File Browser Intent Prefetch Implementation Plan

HT Conference

Hypertext ACM

Query Blocks and Databases

Agents 2

Importing

New Site Settings Section

Meta Schema System

Document Metadata Editor

Board Appview

Coming Soon

Deleted Document Parent Embed Cleanup

Tables Project Proposal

This is a proposal for implementing tables in HM editor

Query Block Filters

Fast Blob Propagation

Get a published blob to a connected peer in about a second by caching the server's reconciliation set in a monoid tree keyed by inbound demand, plus codec canonicalization on a new /0.9.3 protocol.