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

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.

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.

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